Build with Bob in watsonx Orchestrate: What Shipped, and What Is Still a Preview

Build with Bob is a preview. Not generally available, not covered by a GA support commitment, and not an IBM i connector. That is the direct answer, and it is worth leading with, because most of the August 2026 watsonx Orchestrate release did reach general availability. Skim the announcement and you come away thinking the whole thing shipped.

It did not. One piece carries a preview label, a long list of others carry a GA label, and knowing which is which decides what you are allowed to hang a delivery date on.

What Build with Bob actually does

Open the Create an agent dialog in watsonx Orchestrate and there is now a Build with Bob option. Pick it and Orchestrate hands you to IBM Bob in a workspace already pointed at your Orchestrate environment. IBM describes the handoff plainly: one click installs the extension and loads the relevant MCP servers and skills, taking you from watsonx Orchestrate to a fully configured Bob environment without assembling any of it yourself.

Two MCP servers get wired up, and the split between them is the interesting part. The watsonx-orchestrate-adk server drives the Agent Development Kit command line, so Bob can create and deploy artifacts rather than only describe them. The watsonx-orchestrate-adk-docs server puts the current Orchestrate documentation in front of the model, so what Bob generates matches the product as it ships rather than whatever the model remembers. From there you describe the agent you want in plain language, and Bob writes the agent definition, the tools it calls, and the workflow that ties them together. It will also refine an agent you already have, the part most demos skip and the part that matters after week one.

None of this is capability invented for the release. Niklas Heidloff published the manual version on January 8, 2026: two MCP servers wired into Bob by hand, one serving the Orchestrate documentation and one driving the command line, a custom Agent Architect mode, and a working agent generated in under five minutes. Build with Bob is that pattern with the setup removed.

That is a real improvement, and it is also a reason to stay calm about the preview label. The method underneath the button already worked before IBM put a button on it.

Read the labels, because they are not all the same

The August release was a large one and the availability labels are mixed. Get this straight before you brief anybody, because the single preview item is the one with the headline attached to it.

What the preview label actually costs you

Three practical consequences, in the order they tend to bite.

It is SaaS only. Preview availability is AWS and IBM Cloud. If your Orchestrate environment runs anywhere else, this feature does not exist for you yet, whatever the announcement implies.

IBM has not published a GA date, and has not said whether the entry point changes shape before it gets one. That is ordinary for a preview, and it is also the whole risk. Nothing carrying a preview label should be load-bearing on a date you have already promised somebody.

Then the third one, which cuts the other way. What Bob produces is an Agent Development Kit project: agent definitions, tool definitions, a workflow, sitting as files in your repository. The extension that produces them is generally available on both marketplaces. If the button in Orchestrate changed tomorrow, you would install the extension, run Initialize Workspace, and carry on with the same two MCP servers. The preview label sits on the convenience, not on the method, which is a much better place for it to sit.

Where this sits in the Bob to Orchestrate to IBM i chain

Bob builds the agent. watsonx Orchestrate runs it. Neither of them reaches IBM i on its own, and the August release did not change that. Nothing in the release notes, the IBM announcement, or the published developer walkthroughs mentions IBM i, Db2 for i, or RPG, and Orchestrate still ships no IBM i connector. What changed is how quickly you can produce the agent shell and its tool definitions, not what those tools are wired to.

The piece that closes the gap is the open-source IBM i MCP Server, and an Orchestrate tool that calls it is work you do yourself. Bob is a sensible thing to write it with, since consuming MCP servers is already how Bob talks to Orchestrate. We walk the full three-part chain, including a build order and the questions to settle before anything writes to a live system, in Bob, watsonx Orchestrate and the IBM i MCP Server. Product detail lives on the IBM Bob and IBM watsonx Orchestrate listings.

What an IBM i team should and should not plan around

The honest read

The temptation with an announcement like this is to treat the headline as the news. Bob and watsonx Orchestrate in the same sentence looks like IBM finally connected its IBM i coding agent to its enterprise agent platform. Read the release notes instead and the actual news is smaller, more useful, and more honest: IBM shipped a GA extension that makes Bob a competent watsonx Orchestrate developer, and put a preview-labeled shortcut to it inside Orchestrate.

For an IBM i shop that is still a good week's work. Install the extension, generate an agent against something low-stakes, and find out whether the output is worth reviewing. That question is answerable now, and it does not depend on any preview surviving.

What to watch next is on our IBM i AI watch list for fall 2026. IBM TechXchange runs October 26 to 29, 2026 in Atlanta, the same event where Project Bob was first shown in 2025, and it is the likeliest venue for either a GA date on this preview or a prebuilt IBM i skill for watsonx Orchestrate. Neither has been announced.