Claude Code advisor 模式与 Jev 分层

SECTOR @sector_sol原推发布于 2026.10.08

在 X 上打开原推

holy sh*t. Anthropic has an advisor mode for Claude Code. stop making Opus do work Haiku could handle while Sonnet builds ur strongest model doesn’t need to babysit every file search keep it on call for the decisions that actually matter the setup: → Sonnet 5.5 runs the main session writes the code, applies diffs, runs tests → Haiku 5.5 handles scoped repo searches finds files, pulls docs, reports back without dumping the whole codebase into the main chat → Opus 5.5 acts as the advisor gets called when the lead needs a stronger second opinion start a session with: claude --model sonnet --advisor opus or enable it inside an existing session: /advisor opus the three checkpoints worth asking for: 1. before committing to a big plan are we about to build around the wrong assumption? did we miss an auth rule or a schema contract? 2. when the same error comes back are we fixing the cause or just producing increasingly creative patches? 3. before calling the task done does the full diff actually hold up? what breaks outside the happy path? Sonnet keeps moving Haiku does the legwork Opus checks the expensive mistakes one catch people will skip: the advisor receives the full conversation and uses additional tokens it isn’t a free background reviewer and those checkpoints are instructions, not guaranteed automatic triggers Jev fits the same idea one layer lower the original post describes using it for narrow routing decisions: which file, which tool, retry or stop that’s a separate layer, not something /advisor magically installs the useful principle is simple: don’t spend frontier-model reasoning on every mechanical branch paste this into Claude Code: “Review my current Claude Code setup and propose a lead / researcher / advisor workflow. 1. Inspect user settings, project settings and existing subagents. Identify anything that overrides the selected models. 2. Propose Sonnet as the lead with high effort where supported. Use Haiku for scoped, read-only file discovery and documentation tasks. Configure Opus as the advisor using supported settings. 3. Add instructions to consult the advisor: - before committing to a substantial multi-file plan - when the same test or compiler error fails twice - before declaring a long task complete 4. Keep researcher outputs compact: relevant file paths, findings, source links and unresolved questions. No unrelated edits or giant context dumps. Verify every setting against the installed version. Do not invent CLI flags or configuration keys. Show every proposed change as a diff. Do not edit anything until I approve.” save this before ur next debugging session turns into Opus reading the same folder for the seventh time

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