多智能体开发流水线里用 Jev 做零成本路由
Opus 5.5 写码、Fable 5.1 把关的多层 agent 架构,其中 Jev router 负责文件与工具分支的即时路由,附配置提示词。
anthropic quietly unlocked the most powerful claude code loop: opus 5.5 + fable 5.1 opus writes the code. fable reviews the entire session before you break production. and it runs completely autonomously in a single terminal. here is the exact multi-tier architecture i use for 24/7 autonomous dev: → opus 5.5 (high effort) = session director & planner → explorer = indexes the codebase & reads files → worker = writes diffs & runs test suites → researcher = pulls external docs & api specs → jev router = instant zero-cost routing for file/tool forks → fable 5.1 = on-call advisor triggered ONLY at key gates fable stays silent during routine execution. it only kicks in: • before generating a big plan: "are we touching the right files?" • when an error repeats twice: "what false assumption are we making?" • before marking done: "what edge case did we miss?" to configure your environment automatically, paste this prompt into claude code ↓ "reorganize my claude code setup into this multi-agent tree: 1. scan ~/.claude/agents and .claude/agents for existing explorer, worker, and researcher roles. define only the missing subagents. 2. configure each subagent with model: opus and effort: medium. if any role has a custom model set, preserve it and report. 3. configure the main session with effortLevel: high and advisorModel: fable in ~/.claude/settings.json. 4. check for CLAUDE_CODE_DISABLE_ADVISOR_TOOL and any flags blocking advisor telemetry. report without modifying. 5. append this rule to ~/.claude/CLAUDE.md: invoke the advisor strictly before large plan generation, on duplicate runtime errors, and before declaring a milestone complete. 6. show all proposed updates as a git-style diff first. do not write changes until confirmed." save this for your next autonomous build session.
这条是引用着另一条写的:x.com/0xwhrrari/status/2105643919119696297