claude-code - 💡(How to fix) Fix [FEATURE] Allow model switch from plan approval menu [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45422Fetched 2026-04-09 08:05:48
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3closed ×1commented ×1

Fix Action

Fix / Workaround

Current workaround

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When using plan mode, a common workflow is to use a more capable model (e.g., Opus) for planning and a faster/cheaper model (e.g., Sonnet) for implementation. However, once the plan approval menu appears ("Would you like to proceed?"), the terminal input is captured by the numbered options and it is no longer possible to run slash commands like /model sonnet.

Current workaround

  1. Accept the plan (option 1 or 2)
  2. Press ESC to interrupt execution
  3. Run /model sonnet
  4. Send a "continue" message to resume

This is functional but requires an extra interruption and a "continue" prompt that feels unnecessary.

Proposed Solution

  • Allow a 4th option in the plan approval menu to switch the model before proceeding, or
  • Keep the slash command input accessible while the plan approval menu is shown, so the user can run /model <model> before selecting an option.

Why this matters

The plan mode is designed to separate thinking from doing. Pairing it with model switching (expensive model to plan, cheaper model to execute) is a natural and cost-effective workflow, but the
current UX makes it unnecessarily cumbersome.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Allowing a model switch option in the plan approval menu or keeping slash command input accessible can improve the workflow.

Guidance

  • Consider adding a 4th option to the plan approval menu to switch models before proceeding, which would simplify the current workaround.
  • Alternatively, explore the possibility of keeping the slash command input accessible while the plan approval menu is shown, enabling users to switch models seamlessly.
  • Evaluate the feasibility of integrating model switching into the plan approval menu to enhance user experience and workflow efficiency.
  • Assess the potential impact of this change on the overall CLI commands and flags feature category.

Example

No specific code snippet is provided due to the lack of technical implementation details in the issue.

Notes

The proposed solution aims to address a specific pain point in the plan mode workflow, but its implementation may depend on the underlying architecture and technical constraints of the system.

Recommendation

Apply a workaround, such as adding a 4th option to the plan approval menu, as it directly addresses the user's need for a more streamlined workflow.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING