AI coding tools are arriving on IBM i. IBM Bob launched last month. Anthropic's Claude and ChatGPT have shown real capability with RPG. Early results are promising. However, as IBM i shops start evaluating these tools, a practical problem keeps coming up: the development foundation most shops are running wasn't built for this. Eradani is at COMMON POWERUp 2026 in New Orleans this week to talk about that problem, and what to do about it.
AI coding tools need source code on developer's local machine to work.
Traditional IBM i shops use PDM workflows and source physical files without local code access.
Many vendors push copies of RPG source to repositories but lack true Git functionality.
Eradani DevOps provides true Git branching, pull requests, merge workflows, and CI/CD pipelines.
Works with GitHub, GitLab, Azure DevOps, Bitbucket, Jira, ServiceNow, and SonarQube.
Eradani exhibiting at COMMON POWERUp 2026, Booth #305.
AI coding tools need source code on the developer's local machine to work. For shops running PDM-based workflows and traditional source physical files, that's not how things work today. Code lives on the IBM i. Getting it local, working with it, and getting it back safely is a manual process. Many shops are internally divided. Experienced developers want to continue using PDM, the RDi Remote System Explorer, and the Code for IBM i VS Code plugin. Younger developers new to IBM i want to work with the latest open-source tools and expect to use Git.
There is a real difference between having code in Git and actually using Git. Vendors have been pushing copies of RPG source to repositories for years and calling it Git support. You cannot take advantage of powerful parallel development support of Git; you cannot easily branch your code, stash it, trigger a pipeline from it, or run a code review against it. You cannot view changes at the branch or developer commit level, or easily roll back changes to a specific tag. You cannot make source changes locally on your PC and then use Git to sync them to your IBM i for compiles and execution. It is a backup dressed up as DevOps.
Eradani DevOps gives IBM i developers true, native Git. Real branching, pull requests, merge workflows, and CI/CD pipelines. It works with GitHub, GitLab, Azure DevOps, and Bitbucket. It connects to Jira, ServiceNow, and SonarQube. When developers work in real Git, they can have a local clone of their repository on their machine. Clone the repo, work locally, and push your changes. That local clone is what AI coding tools need. Eradani DevOps customers aren't blocked by the problem that's frustrating other shops right now. With Eradani DevOps, developers can choose to work locally or use traditional tools. Either way, they get a full Git workflow. An AI coding assistant is embedded, not an additional project.
Without a real pipeline, AI-generated code flows straight from the developer's screen to production. Manual checks worked when developers wrote 10-20 lines of code per hour. With AI tools generating thousands of lines in minutes, only automated pipelines can handle the load. With Eradani DevOps, AI-generated code goes through the same process as everything else. Committed to a branch, reviewed in a pull request, scanned by tools like SonarQube, and deployed through Eradani iDeploy with full traceability. Nothing reaches production without passing through the same gates as every other change.
As Dan Magid, CEO of Eradani, stated: "The AI tools are real, and they work. What we're telling customers at POWERUp is that the tools are only as good as the pipeline behind them. If you don't have a real DevOps foundation on IBM i, AI-generated code is just more risk sitting between your developer and your production system."
About Eradani
Founded in 2019, Eradani helps IBM i organizations connect their core systems to modern technology without ripping out what works. Eradani DevOps brings true Git-based development lifecycle management to IBM i. Eradani Connect provides secure, high-performance API and integration capabilities for IBM i environments.