IBM's 'Bob' Enters the Agentic Coding Race, Betting on Legacy Modernization

IBM is pitching Bob as an agentic development assistant that goes beyond autocomplete, positioning it against tools like Copilot and Cursor. Its headline features include spawning parallel subagents that each carry their own context and tools for long-running background work, a ‘Literate Coding’ mode that turns natural-language descriptions into in-context implementations, a ‘Bob Shell’ for CLI and CI/CD use, and ‘Bobalytics’ for tracking agent contributions and costs across the software delivery lifecycle. Guardrails get explicit billing: Bob operates in approval-gated modes and, per one testimonial, declines to answer rather than hallucinate unknown RPG op-codes.

The real differentiator is enterprise legacy modernization rather than greenfield development. Bob leans hard into IBM’s own turf — reading and refactoring RPG and COBOL, IBM i and mainframe workflows, and bulk Java version upgrades (one customer claims a Java 11-to-25 migration in three days versus a month) — plus native connections to Red Hat, Instana, and other IBM ecosystem services. Compliance framing (HIPAA, FedRAMP) and premium ‘purpose-built’ packages reinforce that the target buyer is large organizations sitting on decades of legacy code, not individual developers.

Worth reading skeptically: the page is a product landing site, and its evidence is almost entirely vendor testimonials and unaudited productivity claims rather than independent benchmarks. Still, the strategic signal is clear — IBM is staking out the modernization niche (mainframe, IBM i, RPG/COBOL, mass Java upgrades) where its incumbency is strongest, instead of competing head-on for everyday code completion.