Claude Code team setup with Opus as lead and Haiku as swarm
Opus 5.5 decomposes tasks into a DAG and signs off, Haiku 5.5 runs subtasks in parallel, and Jev handles micro-branch decisions in milliseconds.
THIS IS ABSOLUTE F*CKING GOLD Anthropic just shared one of the best tricks for Claude Code The idea: run Opus 5.5 as lead, and swarm cheap Haiku 5.5 teammates in parallel Opus-level architecture on every task, without burning Opus context on 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, decomposes tasks into a DAG, and signs off → Haiku 5.5 swarms as autonomous teammates across isolated context windows → Sonnet 5.5 implements heavy multi-file refactors without blocking peers → you stop burning Opus context on a hundred agent transcripts Opus only steps in at three moments: → breaking your goal into a dependency DAG before the run → approving diff plans before teammates edit files → signing off on verified results before anything ships Opus leads · Haiku swarms · Sonnet ships JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split the full tree > Opus 5.5 runs the lead session and coordinates the task DAG > security audits auth and JWT handling on Haiku 5.5 > perf-scout profiles p99 latency bottlenecks on Haiku 5.5 > qa-engine executes full test suites on Haiku 5.5 > patcher refactors complex multi-file logic on Sonnet 5.5 > Opus 5.5 reads only verified PR diffs > 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 main lead session on Opus 5.5 to decompose tasks into a dependency DAG 3. Spawn three parallel teammates on Haiku 5.5 for security, perf, and qa 4. Have teammates self-claim unblocked tasks, coordinate findings via P2P mailbox, and draft plans before modifying code 5. Route heavy multi-file patches to Sonnet 5.5 and clear fast deterministic forks 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 use this on every serious codebase
This post quotes another post: x.com/mirku21/status/2098836008468992471