Anthropic recently published a nice pattern: pair a cheaper executor (Sonnet) with a stronger advisor (Opus) consulted only at strategic moments — task start, when stuck, before declaring done, every N turns.
The official advisor_20260301 API tool only accepts Claude executors though. With the recent tightening of quotas on Max/Pro plans, I got curious: what if the executor were a local model? Same pattern, but the bulk of the turns never touches the Claude API.
So I built /local-advisor, a Claude Code slash command:
/local-advisor "your task here"
Local Qwen or essentially any other local model (via Ollama) runs the inner loop. At trigger points it dumps a transcript snapshot to disk; Claude Code reads it, writes strategic advice, the local executor resumes. The two never talk directly… handoff is entirely file-based, which makes the whole run auditable after the fact. Repo: https://github.com/Shubha1m/Advisor_Skill Early days, definitely rough edges. Would genuinely appreciate feedback on the trigger heuristics, the prompt design for the advisor, or anything else you think could be sharper. submitted by /u/RealCharzard
Originally posted by u/RealCharzard on r/ClaudeCode