claude-code - 💡(How to fix) Fix [FEATURE] Feature: Auto model-switching with user approval (Sonnet → Opus on complexity) [1 comments, 2 participants]

TL;DR

Implement a complexity classifier to automatically detect complex tasks and prompt the user to switch from the default Sonnet model to Opus, ensuring cost-effective and efficient task completion.

Guidance

• Introduce a configuration option to enable or disable the auto-upgrade feature, allowing users to control the behavior based on their needs and cost considerations.
• Develop a complexity classifier that assesses task complexity based on heuristics such as the number of files involved, algorithmic design, and multi-step reasoning, and prompts the user to switch to Opus when the complexity score exceeds a threshold.
• Implement a client-side routing layer in Claude Code to handle the model switching without requiring changes to the Claude API.
• Consider adding an option for the user to choose whether to revert to Sonnet automatically after the complex task completes or keep using Opus for the session.

Example

{
  "defaultModel": "claude-sonnet-4-6",
  "autoUpgrade": {
    "enabled": true,
    "upgradeModel": "claude-opus-4-6",
    "requireConfirmation": true,
    "revertAfterTask": true // optional
  }
}

Notes

The proposed solution requires careful consideration of the complexity classifier's heuristics and threshold to ensure accurate detection of complex tasks and minimize unnecessary prompts. Additionally, the cost implications of switching to Opus should be clearly communicated to the user.

Recommendation

Apply the proposed solution with a complexity classifier and user confirmation prompt, as it provides a balanced approach to cost-effectiveness and task efficiency. This approach allows users to control costs while still benefiting from the more powerful Opus model when needed.