Claude Code /advisor Runs Opus as Codebase Strategist
Key insights
- Opus 4.7 acts as a strategic coordinator dispatching parallel Sonnet workers to read files within a single Claude Code session.
- The architecture resolves context-window limits by distributing file reads across multiple lower-cost runners, each holding only its assigned subset.
- Strong r/ClaudeAI community response signals validated demand for multi-model orchestration in large-monorepo development workflows.
Why this matters
Context limits are the primary friction point for AI-assisted work on large codebases, and /advisor demonstrates that multi-model orchestration can address this without custom infrastructure or third-party tooling. The senior-junior model architecture generalizes well beyond code reading: any task benefiting from strategic decomposition and parallel execution could follow the same pattern using Claude's existing slash command framework. For teams managing large monorepos, this is the first community-validated pattern for keeping Opus-level reasoning active without forcing every file into a single context window.
Summary
A developer released /advisor, a Claude Code slash command putting Opus 4.7 in charge while routing actual file reads to parallel Sonnet instances.
Opus runs a Glob pass to map codebase structure, then dispatches targeted reads to concurrent Sonnet workers. Each runner holds only its assigned subset, keeping individual context windows manageable. Opus aggregates results and provides strategic guidance across the full session.
Essentially: (Opus 4.7, Claude Sonnet) operating as a senior-junior team inside one Claude Code session.
- Opus handles structural mapping and coordination; Sonnet handles the parallel file reads.
- The pattern targets large-monorepo pain where one context window cannot hold the full codebase.
- Early r/ClaudeAI response shows strong interest from teams already hitting context limits at scale.
Multi-model orchestration inside Claude Code is now working without third-party tooling.
Potential risks and opportunities
Risks
- Sonnet runners operating without full context risk producing incomplete file summaries, potentially causing Opus to give flawed strategic advice on cross-file dependencies in large refactors
- Anthropic's future Claude Code updates could alter model-routing behavior or the slash command interface, making community-built orchestration patterns like /advisor unmaintainable without ongoing community fixes
- Teams adopting this pattern at scale face compounding API costs if Opus 4.7 coordination calls multiply as monorepo size grows, since Opus is significantly more expensive per token than Sonnet
Opportunities
- Developer tooling companies (Cursor, Replit, Sourcegraph) could productize the senior-junior model orchestration pattern as a native feature targeting enterprise monorepo users
- Anthropic could formalize multi-model slash command primitives in Claude Code, giving /advisor-style patterns a first-class integration path and reducing community maintenance burden
- AI engineering consultancies specializing in large codebase migration gain a reproducible, low-overhead analysis method that does not require custom infrastructure or proprietary orchestration frameworks
What we don't know yet
- Whether orchestration overhead from Opus's Glob pass offsets parallelization gains on codebases below a certain file count threshold has not been benchmarked publicly
- Cost breakdown between Opus 4.7 coordination calls and Sonnet worker calls across a realistic monorepo session remains undisclosed
- No information on whether Anthropic plans to formalize multi-model slash command orchestration patterns in official Claude Code documentation or tooling
Originally reported by reddit.com
Read the original article →Original headline: r/ClaudeAI: Developer Ships /advisor Slash Command for Claude Code — Opus Acts as Strategist Coordinating Parallel Sonnet File-Reading Runners