Forge meeting agents join real Google Meet calls as participants: they arrive with their persona, their history and the roadmap already in context, they can pull another agent into the same call by name, and the two of them talk to each other in front of the room. Every tool they call renders as a structured card in a transcript you can watch live.
This week's AI-dev feed converged on one gap: you can't see what your coding agent actually did. Agentmetry and Episko shipped 'flight recorders' to bolt observability on after the fact. Forge never had the gap — every character turn already produces an auditable transcript and a commit-linked handoff. Here's why observability you add is weaker than observability that's structural.
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 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.