Claude Code 多模型分工工作流，Jev 只做轻量路由

SECTOR @sector_sol原推发布于 2026.10.19

在 X 上打开原推

your opus context is too expensive for this sh*t stop filling it with transcripts from agents doing repetitive work claude code workflows let a script coordinate the run instead of making the main model babysit every step here's the setup i'd use: → opus designs the workflow → haiku handles read-only discovery → sonnet makes scoped changes → a separate verifier checks the evidence → opus reviews what actually survived the model split is something you configure, not a default to assume start here: claude --model opus --effort ultracode the important change isn't “spawn more agents” it's moving the execution loop into code the workflow holds the intermediate results the main session gets the useful outcome instead of every worker's running commentary for a large repo, structure the work like this: 1. discover the files in scope 2. scan them for a specific class of issue 3. collect findings with paths and evidence 4. reject duplicates and unsupported claims 5. patch confirmed issues in isolated worktrees 6. independently verify the changes 7. review the final diff before committing opus shouldn't need to reread 50 conversations to decide whether one patch is ready and if JEV is already part of your stack, keep it on the lightweight routing decisions rather than pretending every branch needs heavyweight reasoning paste this into claude code: “Propose a reusable workflow for this repository. Use Opus for architecture and final review, Haiku for read-only discovery, and Sonnet for edits where available. Give editing agents separate worktrees and clearly bounded file ownership. Require an independent verifier for every reported issue and proposed fix. Stop correction loops after two rounds without progress. Report unresolved failures instead of hiding them. Begin with one directory and report usage before expanding. Show the proposed workflow and configuration changes as diffs first. Do not edit or commit anything until I approve.” one thing worth remembering: cleaner context does not mean free compute parallel workers still consume tokens, so test the split on a small task before pointing it at the whole repo save this for the next audit or migration that would otherwise drown your main session in logs

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