Preflight Checklist
Problem Statement
Currently, Claude Code's auto mode classifier automatically defaults to whichever main model is currently active in the session. For instance, when using a high-capability model like Claude 4.8 Opus as the primary model, the sub-task classification and routing decisions are also executed by Claude 4.8 Opus.
This behavior introduces two major pain points:
- Performance Bottleneck (Slowness): Using a heavy, high-parameter model like Opus for simple intent classification or step routing drastically slows down the automated loop execution.
- Exorbitant Costs: Running every minor classification check through Opus 4.8 rapidly consumes API tokens, making the workflow highly cost-inefficient.
Furthermore, Anthropic's own engineering blog post (https://www.anthropic.com/engineering/claude-code-auto-mode) highlights that Sonnet 4.6 already delivers highly effective and accurate results when acting as the auto mode permission classifier. Since Sonnet 4.6 is substantially faster and much more cost-effective, forcing the classifier to run on a heavy primary model like Opus 4.8 creates unnecessary overhead and prevents users from achieving the optimal balance of speed and cost outlined in your documentation.
Proposed Solution
We propose introducing a dedicated configuration option or environment variable—such as CLAUDE_CODE_AUTO_MODE_MODEL—to decouple the auto mode classifier from the main coding model.
For example, a user could configure their environment as follows:
export CLAUDE_CODE_AUTO_MODE_MODEL=claude-sonnet-4-6
Alternative Solutions
No response
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
No response
Additional Context
No response
Preflight Checklist
Problem Statement
Currently, Claude Code's auto mode classifier automatically defaults to whichever main model is currently active in the session. For instance, when using a high-capability model like Claude 4.8 Opus as the primary model, the sub-task classification and routing decisions are also executed by Claude 4.8 Opus.
This behavior introduces two major pain points:
Furthermore, Anthropic's own engineering blog post (https://www.anthropic.com/engineering/claude-code-auto-mode) highlights that Sonnet 4.6 already delivers highly effective and accurate results when acting as the auto mode permission classifier. Since Sonnet 4.6 is substantially faster and much more cost-effective, forcing the classifier to run on a heavy primary model like Opus 4.8 creates unnecessary overhead and prevents users from achieving the optimal balance of speed and cost outlined in your documentation.
Proposed Solution
We propose introducing a dedicated configuration option or environment variable—such as
CLAUDE_CODE_AUTO_MODE_MODEL—to decouple the auto mode classifier from the main coding model.For example, a user could configure their environment as follows:
export CLAUDE_CODE_AUTO_MODE_MODEL=claude-sonnet-4-6Alternative Solutions
No response
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
No response
Additional Context
No response