[Feature Request] Automatic Model Switching Between Plan and Execution Modes

[francois-gaquere]

Bug Description
Feature Request: Automatic Model Switching in Claude Code
Currently, users must manually switch between models depending on the task (Plan mode vs. execution). This creates friction and leads to suboptimal usage — either using Opus for simple code tasks (wasteful) or Sonnet for architecture planning (underperforming).
Suggested behavior:

Automatically use Opus 4.6 when entering Plan mode
Automatically switch to Sonnet 4.6 when execution begins (file creation, edits, bash commands)
Allow users to override manually at any time

Why this matters:
The two phases of development (thinking vs. doing) are already clearly separated in Claude Code's UX. The model selection should reflect this naturally. Most users don't realize they should switch models between phases — and those who do find it tedious.
Expected outcome:
Better results at lower token cost, with zero added complexity for the user.

Environment Info

• Platform: darwin
• Terminal: cursor
• Version: 2.1.50
• Feedback ID: 299b208f-d401-44e7-a60f-fa7ed7104ebe

Errors

[]

[Lknechtli]

Additionally, it would be nice if each mode was configurable completely separately - there's already /model opusplan, which gets us partway there, but it would be nice if we could have a separate /model configuration for each mode instead.

This would give us the ability to do something like high thinking in plan, and medium otherwise.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.