Claude Code 用 /advisor 加 Jev 分流小决策

Mr. Buzzoni @Mr_Buzzoni原推发布于 2026.10.19

在 X 上打开原推

Claude Code tip: once Opus 5.5 is your main model, stop letting your Fable 5.1 quota go to waste put it on call with /advisor run /advisor fable Opus 5.5 does all the building Fable 5.1 follows the session in the background and cuts in three times: -> before a plan: does this hold up? -> when one error keeps returning: am I fixing the wrong thing? -> before "done": what slipped through? Fable 5.1 checks the direction. Opus 5.5 does the typing Jev engineering takes it one step further: the small forks (which file, which tool, retry or stop) go to Jev in under half a second, so the pricey models only see the calls that can change the result where this setup pays off most right now: long reverse engineering runs with REA, the open source MCP that lets Opus 5.5 take any app apart down to the binary • the full setup > Opus 5.5 on high drives the main session > subagent one reads the code > subagent two edits and runs tests > subagent three checks the docs > all three on medium > Fable 5.1 on call give Claude Code the tree plus this prompt 👇 "Configure Claude Code to match this tree: 1. Reuse suitable subagents from ~/.claude/agents and .claude/agents. > Draft new ones only where a role is missing > Give each model: opus, effort: medium > List any that pin another model and leave them 2. Set main session effort to high with effortLevel in ~/.claude/settings.json 3. Look for env vars that turn off the advisor (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, anything that blocks flag fetching) and CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them and leave them be 4. Add a rule to ~/.claude/CLAUDE.md: check with the advisor before a big plan, when an error repeats, and before marking a long task done Show me the changes first, edit nothing until I confirm." ↳ https://code.claude.com/docs/en/advisor

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