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

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

[]