THIS IS A ACTUAL F*CKING GOLDMINE Anthropic just shared one of the best tricks for Claude Code The idea: run Sonnet, Haiku 5.5 and Opus 5.5 at once, each doing only what it's best at Better results and way fewer tokens: every task lands on the right model You just start Claude Code like this: CLAUDE_CODE_SUBAGENT_MODEL=haiku claude --model sonnet here's how it splits: → Sonnet 5.5 runs the main session, writes the code, and applies fixes → Haiku 5.5 swarms the repo in parallel: search, grep, docs, and test audits at 340 tok/s → Opus 5.5 stays on call as architect for the big decisions and signs off on diffs → you stop burning Opus context on routine tasks and stop flooding main session with raw logs Opus only steps in at three moments: → before a plan locks → when the same error hits twice → before calling it done (signing off on git diff) Sonnet builds, Haiku swarms, Opus reviews JEV engineering is the same move one layer down: the forks that need no thinker (which file, wh