Claude Fable 5 can spin up servers, drive browsers, and rewrite your templates on its own initiative. Simon Willison calls running that unsandboxed 'a top contender for a Challenger disaster.' Forge shipped the answer the same week — isolated stacks with per-run JWT roots, auto-swept orphans, and tenant-level worker isolation. Here's what landed and why.
Every Claude Code turn becomes an immutable, git-backed snapshot in Forge. Roll back to any point, branch into a different path, continue in the cloud with one click, and resume on any machine with full context. Local-only AI sessions are over.
Two days ago Anthropic shipped Dynamic Workflows in Claude Code — Claude writes an orchestration script that fans out hundreds of subagents, with adversarial verification. It's genuinely good. But it's ephemeral, model-authored, code-centric task orchestration. Forge is a durable, human-governed, audited team workflow. Here's the honest difference.
Claude Code, Cursor, Devin can write code. None of them can reliably ship that code to production by themselves — because production isn't code, it's infrastructure, secrets, and verifiable provenance. Here's how Forge + Simple Container actually deliver on the multi-agent 0-to-prod promise.
Forge started as a five-agent SDLC pipeline. Today the same engine runs any team you can describe in plain English — research, marketing, ops, support, software delivery. SDLC stays our deepest preset; the engine is general.
Forge agents now have personas, XP, character sheets, and per-run memory — and you can race two teams of them against the same GitHub issue, side by side.
Introducing Forge — an AI-powered multi-agent platform where five specialized agents collaborate to turn GitHub issues into production-ready code.