Claude Code swarm：Opus 规划、Haiku 扫描、Jev 处理分支

Grirk @Grirku原推发布于 2026.10.18

在 X 上打开原推

THIS IS A PURE FUCKING GOLDMINE Anthropic just showed one of the cleanest Claude Code tricks. Opus 5.5 writes the plan as a script, then sits idle at zero tokens while 12 cheap agents actually do the work. Same task, two ways: Opus solo was still at 49% and burning 231k tokens. The swarm finished in 9:05 on 165k tokens 2× faster. You launch it like this: claude --model opus --swarm haiku,sonnet Here’s the split: → Opus 5.5 writes plan.js and stops reading anything → 6× Haiku 5.5 audit every file in parallel → 4× Sonnet 5.5 patch each fix in its own isolated copy → 2× Haiku 5.5 cross-check (8 of 9 findings survive) Opus only appears twice: → writing the plan → signing off on the verified fixes Opus plans. Haiku scans. Sonnet ships. JEV sits one layer down and resolves 3,767 micro-forks (which model, which lane, retry or stop) in code. Only the real splits ever reach Opus. The full tree > Opus 5.5 runs the main session on xhigh and writes the plan > scan audits files on Haiku 5.5 ×6 > patch applies fixes on Sonnet 5.5 in isolated copies > verify cross-checks on Haiku 5.5 > Opus only reads what survived, then signs off > JEV handles deterministic forks in milliseconds Paste the tree + this prompt into Claude Code ↓ Rebuild my Claude Code setup around this tree: Run the main session on Opus 5.5 with effort xhigh and --swarm haiku,sonnet. Have Opus write the plan as a script: scan on Haiku 5.5, patch on Sonnet 5.5 in isolated copies, verify on Haiku 5.5. Let the phases overlap each finding moves forward as soon as its own stage finishes, no waiting for the batch. Never surface raw agent output to the main session, only verified results. Route deterministic forks (model choice, lane choice, retries) through JEV. Show me every change as a diff first. No edits until I say go. save it, it’ll come in handy.

这条是引用着另一条写的：x.com/mirku21/status/2098836008468992471