Claude Code 多模型工作流：Opus 规划、Sonnet 并行、Fable 校验

mirku @mirku21原推发布于 2026.10.04

在 X 上打开原推

Official Anthropic tip for Claude Code: don't exhaust Opus 5.5 context on repetitive multi-file routines when Sonnet 5.5 can swarm them in parallel and Fable 5.1 can verify the result turn mass-agent sweeps into deterministic code with dynamic workflows claude --effort ultracode /workflows Opus 5.5 acts as the lead architect, drafting the workflow script, setting input schemas, and synthesizing final verified reports Sonnet 5.5 workers swarm the execution pipeline across dozens of files, handling bulk refactors and migrations at medium effort Fable 5.1 stands by as the dedicated verifier, entering the pipeline at three decisive moments: → before a fan-out: does this workload justify a 50-agent script or can a tight 5-step pipeline solve it? → on worker failure: can the step replay from cache or does the pipeline branch need a clean rerun? → before reporting: did every reported finding survive adversarial cross-checking and voting? Sonnet 5.5 executes. Fable 5.1 cross-examines. Opus 5.5 authors and reports Jev engineering runs the identical pattern one layer down: mechanical choices that need no cognitive reasoning (which file to inspect, which tool to invoke, retry or stop) resolve in 16ms, so frontier models only wake up when execution paths actually split Plan on high. Delegate on medium. Keep Fable on call. - the full workflow architecture > Opus 5.5 on high drafts the orchestration script inside .claude/workflows/ > pipeline() fans out Sonnet 5.5 workers across target paths concurrently > each worker operates inside an isolated working copy to eliminate file collisions > Fable 5.1 cross-checks claims and votes down unverified findings > intermediate state lives in script variables, leaving Claude's context 100% clean > 1h prompt cache prefix hold eliminates redundant system prompt processing paste the setup and this prompt into Claude Code below: "Configure my Claude Code workspace for dynamic workflows: 1. Audit ~/.claude/workflows and .claude/workflows for existing scripts: > Draft workflow definitions for codebase audits, parallel migrations, and adversarial verification > Pin model: sonnet, effort: medium for pipeline workers, and model: fable for verifier agents > Configure workers to operate on isolated copies to eliminate edit conflicts 2. In ~/.claude/settings.json, enable dynamic workflows: > Set ultracode = true > Lock main session effortLevel to high > Set subagentPromptCacheTtl = '1h' to share prompt prefixes across parallel fan-outs 3. Set workflow runtime controls: > Set autoContinueAtUsageLimit = true so long batch runs automatically resume after limit resets > Set CLAUDE_CODE_WORKFLOW_PREFIX_STAGGER_MS = 5000 for prompt prefix caching > Set large workflow warning threshold to 25 agents 4. Add a rule to ~/.claude/CLAUDE.md: all multi-file audits must pass an adversarial Fable cross-check before findings are reported to the lead session Show every configuration diff first. Do not apply edits until confirmed" ↳ http://code.claude.com/docs/en/workflows

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