Opus 5.5 当指挥官带 12 个 agent 分四队交付 v2.0

Sprytix @Sprytixl原推发布于 2026.10.19

在 X 上打开原推

THIS IS ACTUAL F*CKING GOLD Anthropic just shared one of the best tricks for Claude Code. The idea: stop treating Claude like one worker. Make Opus 5.5 a commander and give it 12 agents in 4 squads. Same release, two ways: Opus alone was 2% through on one thread. The command center shipped the whole v2.0 in 2 minutes on 12 threads. You just launch Claude Code like this: claude --model opus --command-center 12 "ship v2.0" here's the split: → Opus 5.5 turns "ship v2.0" into 12 tasks across 4 squads → CODE and OPS squads run on Sonnet 5.5, TEST and DOCS on Haiku 5.5 → every agent reports back in one line, never raw logs → Opus only wakes up when something breaks or needs approval the part most people get wrong: the commander watches everything. read 12 agent transcripts and your expensive model becomes the slowest part of the room. here the commander stays at 8k of context the entire run. it plans, it waits, it reads 12 one-line reports, it opens the release gate. REA sits underneath on anything legacy: before a squad touches old code, REA reverse-engineers it into a spec, so agents build from the spec and never from 500 files nobody understands. Opus commands. Sonnet builds. Haiku checks. REA explains the old code. JEV engineering is the same move one layer down: the forks that need no thinker (which squad, which model, retry or stop) go to JEV in milliseconds, and the commander only sees the ones that actually split the full tree > Opus 5.5 runs as commander, splits the mission into tasks and squads > CODE squad on Sonnet 5.5 writes endpoints, refactors auth, migrates the db > TEST squad on Haiku 5.5 runs unit, e2e and load tests > DOCS squad on Haiku 5.5 writes changelog, api docs and release notes OPS squad on Sonnet 5.5 handles staging, health checks and canary rollout REA reverse-engineers any legacy module into a spec before a squad touches it every agent reports one line, the commander never reads raw output Opus 5.5 holds the release gate and waits for all 12 reports JEV routes micro-forks in milliseconds paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Run the main session on Opus 5.5 as a commander: it plans, assigns and approves, it never writes code. 2. Split work into 4 squads: CODE and OPS on Sonnet 5.5, TEST and DOCS on Haiku 5.5, 12 agents total. 3. Every agent reports a one-line structured result. Raw logs never enter the main session. 4. Before any squad touches legacy code, run REA on it first and have the squad build from the spec, not the old files. 5. Add one rule to CLAUDE.md: nothing ships until every squad has reported and the commander opens the release gate. 6. Route deterministic forks (squad choice, model choice, retries) through JEV. Show me every change as a diff first. No edits until I say go." ↳ https://code.claude.com/docs/en/model-config save it, you'll use this on every release from now on.

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