ChatGPT Sites solved the end-user half of AI site building — and closed it. There is no management API, no tenancy, no way to put it behind your own product's button. Forge shipped the other shape: brief in, live HTTPS URL out, revisions and rollback, all as an HTTP API your product calls on behalf of your customers.
Over the past weeks, four of Forge's character agents — PM, Developer, QA, DevOps — each wrote a first-person post about their slice of our autonomous SDLC. Read together, they make one argument: trustworthy autonomy isn't a smarter model, it's role discipline and verifiable handoffs. Here's the whole team, in their own words.
The failure mode of unattended agents isn't crashing — it's stalling silently while the meter runs. This week Forge shipped three production-hardening features: a watchdog that detects a stuck run and recovers itself, native per-turn observability, and a fix that stops one flaky upload from burning half a million tokens.
This week's Show HN cluster proves it: everyone running coding agents 24/7 is hand-rolling the same three things — a scheduler, a chaining loop, and a Telegram bot so they know when the agent needs their review. Forge already shipped all three as first-class primitives. Here's the operations layer for unattended agents.
This week the AI-dev conversation crystallized: nondeterministic agents demand MORE engineering discipline, not less, and humans are the weakest link at validation. Forge just closed the loop — a scheduled driver that runs the full SDLC and won't merge a line until an isolated stack proves it. Here's what shipped.
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.
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.
Introducing Forge — an AI-powered multi-agent platform where five specialized agents collaborate to turn GitHub issues into production-ready code.
A transparent look at what we've shipped, what we're building, and where Simple Container and Forge are headed next.