Claude Code agent teams: Jev routes deterministic forks in milliseconds
Opus 5.5 decomposes tasks, Haiku 5.5 works in parallel, Sonnet 5.5 ships patches, and Jev makes millisecond decisions on deterministic forks, with launch commands and a task tree.
THIS IS ABSOLUTE F*CKING GOLD Anthropic just showed the real Claude Code agent teams loop in motion. The idea: Opus 5.5 leads, Haiku 5.5 swarms in parallel, JEV clears the micro-forks in milliseconds. Opus-level architecture on every task, without burning Opus context on routine turns. You just launch it like this: bash export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 claude --model opus --teammate-mode auto here's the split: → Opus 5.5 leads the team, decomposes the task DAG, assigns mutexes, and signs off → Haiku 5.5 swarms as autonomous teammates (security / perf-scout / qa-engine) across isolated contexts → Sonnet 5.5 takes the heavy multi-file patches without blocking peers → JEV routes the deterministic forks (which file, which model, retry or stop) in milliseconds Opus only steps in at three moments: → breaking the goal into a dependency DAG before the run → approving plans before teammates edit files → signing off on verified results before anything ships Opus leads · Haiku swarms · Sonnet ships · JEV forks the full tree in the video: > Opus 5.5 main session coordinates the task list (effort xhigh) > security (Haiku) audits JWT / timingSafeEqual and patches the leak > perf-scout (Haiku) profiles p99 Redis locks and confirms 2.8x faster > qa-engine (Haiku) runs the full test matrix (58/58 green) > atomic mutex DAG locks tasks so peers never collide > peer p2p bus + mailbox for direct debate and self-claim > JEV fork layer splits sharp / haiku / sonnet in real time > Opus signs off: 12/12 tasks done · consensus approved · zero regressions paste the tree and this prompt into Claude Code ↓ Rebuild my Claude Code setup around this tree: 1. Enable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 with --teammate-mode auto 2. Run the main lead session on Opus 5.5 to decompose tasks into a dependency DAG 3. Spawn three parallel Haiku 5.5 teammates for security, perf, and qa 4. Have them self-claim unblocked tasks, coordinate via P2P mailbox, and draft plans before editing 5. Route heavy patches to Sonnet 5.5 and clear fast forks through JEV Show me every change as a diff first, no edits until I say go
This post quotes another post: x.com/mirku21/status/2098836008468992471