Claude Code experimental agent teams: Opus leads, Haiku swarms

Pontiuz @0xPontiuzOriginally posted 2026.10.26

Open original on X

THIS IS PURE F*CKING GOLD Anthropic just quietly shipped one of the strongest setups for Claude Code The idea: make Opus 5.5 the team lead, and let cheap Haiku 5.5 teammates swarm the work in parallel Opus-grade planning on every task, without paying Opus to babysit a hundred routine turns You just launch Claude Code like this: export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 claude --model opus --teammate-mode auto here's the split: → Opus 5.5 leads the team, turns your goal into a task DAG, and signs off at the end → Haiku 5.5 teammates self-claim unblocked tasks, each in its own isolated context → Sonnet 5.5 takes the heavy multi-file patches without blocking anyone else → teammates talk to each other over a P2P mailbox, so Opus never reads the chatter Opus only steps in at three moments: → locking the dependency DAG before anyone starts → approving the diff plan before a teammate touches code → signing off on verified results before anything ships Opus leads · Haiku claims · Sonnet patches JEV engineering is the same move one layer down: the forks that need no thinker (which file, which teammate, retry or stop) clear through JEV in milliseconds, and the big models only see the ones that actually split the full tree > Opus 5.5 runs the lead session and owns the task DAG > security audits auth and JWT handling on Haiku 5.5 > perf-scout hunts p99 latency bottlenecks on Haiku 5.5 > qa-engine runs the full test suite on Haiku 5.5 > patcher lands multi-file fixes on Sonnet 5.5 once its blockers clear > teammates hand off findings through the P2P mailbox > Opus 5.5 reads only the verified PR diff > JEV routes micro-forks in milliseconds 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 lead session on Opus 5.5 and have it break every goal into a dependency DAG first 3. Spawn three Haiku 5.5 teammates (security, perf-scout, qa-engine) and one Sonnet 5.5 patcher 4. Teammates self-claim unblocked tasks, share findings over the P2P mailbox, and draft a diff plan before editing anything 5. Route fast deterministic forks (tool choice, task pickup, retries) through JEV Show me every change as a diff first, no edits until I say go" ↳ http://code.claude.com/docs/en/agent-teams save it, you'll run this on every serious codebase

This post quotes another post: x.com/0xtrackmind/status/2113644871529418857