watsonx on IBM i
IBM watsonx.ai, watsonx Assistant and watsonx Orchestrate explained for an IBM i or AS/400 shop: what the August 2026 Build with Bob preview connects, how an Orchestrate agent reaches Db2 for i through the IBM i MCP Server, and what each shop size should actually do about it.
watsonx is IBM's umbrella brand for enterprise AI, not a single product, and for most of its life none of it had an official connection to IBM i. That is no longer true. In August 2026 watsonx Orchestrate added a Build with Bob option to its Create an agent dialog, which launches IBM Bob, IBM's AI coding agent for IBM i, into a workspace wired to your Orchestrate tenant. It is the first official bridge between the IBM i coding agent and the watsonx platform.
Read that carefully, though, because it is a bridge between two build tools, not a connector to your data. Bob writes the agent. Orchestrate runs it. Neither one knows what a physical file is. Getting an agent to Db2 for i still runs through the IBM i MCP Server, and that piece is still yours to wire.
What an IBM i shop should use for AI coding assistance today
IBM Bob, with the Premium Package for i. Bob reached general availability 1.0 on March 24, 2026 and 2.0 on June 24, 2026, the same day IBM shipped the Bob Premium Package for i. The Premium Package is the IBM i layer, and it is the reason Bob is an IBM i product rather than a general coding agent that happens to have seen some RPG: about 40 skills and workflows and about 30 tools that read and write QSYS and the IFS, run CL commands and SQL, launch 5250 sessions, manage library lists and support a retrieval-augmented generation workflow, plus a Developer Mode covering RPG, COBOL, DDS, SQL and CL and a Database Mode built for Db2 for i SQL work.
Bob succeeded watsonx Code Assistant for i, which IBM previewed in November 2025 and never shipped as an independent product. Reported pricing runs from a $20 to $40 monthly add-on for the Premium Package up to $240 a month for Ultra with Premium included. Full detail is on the IBM Bob listing and the IBM Bob pricing page.
The general-purpose watsonx products that matter here
watsonx.ai
The foundation-model studio: build, tune, govern and deploy generative AI applications. Version 2.4 shipped in June 2026 as a governance and deployment release, with nothing in it aimed at IBM i. It is the layer underneath the rest of watsonx, and the one you would use to build a custom application against Db2 for i data through your own integration.
watsonx Orchestrate
The AI agent and workflow platform, and the only watsonx product with a live link to the IBM i toolchain. As of August 2026 it can launch Bob from the Create an agent dialog, AgentOps is generally available on IBM Cloud, and the one-knowledge-source-per-agent limit is gone. There is still no IBM i connector in the box.
watsonx Assistant
Conversational AI for chatbots and virtual assistants. Not IBM i-specific and not touched by the August release. Reaching Db2 for i data means custom integration, the same as any other backend.
How Bob and watsonx Orchestrate now connect
The Build with Bob option sits in the Create an agent dialog in watsonx Orchestrate. Choosing it opens a Bob workspace connected to your Orchestrate environment, where you describe the agent in plain language and Bob writes the agent definition, the tools it calls and the workflow that ties them together. It can refine agents that already exist, so it is not only a first-draft generator. Under the hood it configures two MCP servers, one for the Orchestrate Agent Development Kit documentation and one that drives the Orchestrate command line, which is exactly the wiring IBM developer advocates had been assembling by hand since January 2026. The August release turned that pattern into a button.
One caveat that matters if you are budgeting around it. IBM's release notes list Build with Bob as a preview in the Create an agent dialog, available on IBM Cloud and AWS deployments. The Orchestrate extension on the Bob side is generally available; the Launch Bob entry point is not. AgentOps GA on IBM Cloud and the multiple-knowledge-source change in the same release are GA. Treat Build with Bob as something to pilot this quarter, not something to write into a contract.
What it does not do is touch IBM i by itself. The chain an IBM i shop actually wants has three pieces, and we walk through it end to end in Bob, watsonx Orchestrate and the IBM i MCP Server.
How an Orchestrate agent reaches Db2 for i data
Through the IBM i MCP Server, or through integration code you write yourself. None of watsonx.ai, watsonx Assistant or watsonx Orchestrate ships a Db2 for i connector, and the August release did not add one.
The MCP Server is the shorter route. It is an open-source, IBM-published Model Context Protocol server, in beta since October 2025, that runs on IBM i, reaches Db2 for i through Mapepire, and exposes SQL tools defined in YAML plus IBM i services to any MCP-aware agent. watsonx Orchestrate agents call tools. The MCP Server is a tool provider. The two speak the same protocol, which is why the design works on paper. IBM has not published a tutorial assembling that exact combination, so treat it as a plausible design to pilot rather than a supported product, and start with a read-only query.
There is a second, quieter problem for anyone planning retrieval-augmented generation against IBM i documents or data. Db2 for i has no vector store. Db2 for Linux, UNIX and Windows 12.1 has a native VECTOR type and SQL embedding functions; Db2 for i does not, and IBM's stated direction as of May 2026 is OpenSearch running on Power as the vector and hybrid search layer, with the MCP Server as the agent's door into IBM i. Our RAG on IBM i explainer covers what that means for a design.
What this is realistically worth, by shop size
watsonx and IBM Bob on IBM i: a realistic recommendation by shop size
| Shop profile | What to do now | What to leave alone |
|---|---|---|
| One to three developers, no cloud footprint | Buy Bob with the Premium Package for i and use it on code explanation and documentation for the programs nobody understands any more. That is the whole return, and it is a real one. | Skip watsonx entirely for now. An Orchestrate subscription plus the integration work around it will cost more than the value an agent returns at this headcount. |
| Four to fifteen developers, IBM i plus one or two cloud applications | Bob with Premium for the whole team, then one narrow Orchestrate pilot: a single agent, one read-only Db2 for i query through the IBM i MCP Server, on data you already trust. | Do not build an agent that writes to production IBM i data in a first pilot, and do not assume Build with Bob is GA when planning the timeline. |
| Larger shop with a platform team and an existing IBM Cloud or AWS presence | Evaluate watsonx Orchestrate as the enterprise agent layer on its own merits, and scope IBM i access as a separate project. Use Build with Bob to generate the agent scaffolding and MCP tool definitions. | Do not wait for an IBM-supplied IBM i skill or connector. Nothing IBM has published suggests one is coming before TechXchange in October 2026. |
| Any shop still evaluating watsonx Code Assistant for i | Stop. It never shipped independently. Bob is the successor and the current product. | Do not budget a modernization project around the watsonx Code Assistant for i name. |
Sources: IBM Newsroom July 15, 2026; IT Jungle July 13, 2026; watsonx Orchestrate release notes, August 2026; IBM announcement on Bob and watsonx Orchestrate, August 19, 2026.
Product by product, what is actually available
watsonx products, IBM Bob and realistic IBM i use cases as of September 2026
| Product | Realistic IBM i use case | Status |
|---|---|---|
| IBM Bob with the Premium Package for i | RPG, COBOL, CL, DDS and SQL explanation, generation, fixed-to-free conversion, refactoring, documentation, unit tests, and Db2 for i SQL work in Database Mode | GA since June 24, 2026 |
| watsonx Orchestrate with Build with Bob | An agent that spans IBM i and other applications, with Bob generating the agent and its tools; IBM i access through the IBM i MCP Server or custom tools | Build with Bob is a preview in the August 2026 release on IBM Cloud and AWS; the IBM i MCP Server is beta |
| watsonx Orchestrate, AgentOps and knowledge sources | Monitoring agent quality and giving one agent more than one knowledge source | GA on IBM Cloud and AWS as of the August 2026 release |
| watsonx.ai 2.4 | A custom generative AI application over Db2 for i data through your own RAG design, with OpenSearch as the vector layer | GA; the integration is yours to build |
| watsonx Assistant | A custom chatbot integrated with Db2 for i through additional integration work | GA; no IBM i connector |
| IBM Power Autonomous Operations | Not a watsonx product. An AI agent for the Power infrastructure under IBM i, driven through chat | GA expected September 23, 2026 |
If your goal is RPG modernization or code assistance, start with IBM Bob and the Premium Package for i, not the watsonx platform. If your goal is an agent that spans IBM i and other systems, Build with Bob plus the IBM i MCP Server is now the shortest route, with two caveats worth repeating: Build with Bob is a preview, and IBM has not documented that exact combination. If your goal is a custom AI application over Db2 for i data, budget for integration work and for a vector layer that lives outside Db2 for i. Page last revised September 2, 2026 against the watsonx Orchestrate August 2026 release notes.