claude-code - 💡(How to fix) Fix [Feature Request] Hide or disable /effort levels incompatible with current model [2 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#52566Fetched 2026-04-24 06:03:44
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×2

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description UX: Hide or disable /effort levels that don't apply to the current model

When using /effort on Sonnet 4.6, the xhigh and max options appear in the menu with descriptions saying "Opus 4.7 only." This is confusing — it's unclear whether setting them has any effect, and the second /effort invocation silently cancelled without explanation.

Suggestion: Grey out or hide effort levels that are incompatible with the active model, or show an inline warning before confirming the selection (e.g., "xhigh requires Opus 4.7 — switch models first?"). This would prevent users from thinking they've enabled deeper reasoning when they haven't.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.118
  • Feedback ID: 2551507e-b5f6-404c-9c4a-7b159d7e9a43

Errors

[]

extent analysis

TL;DR

Disable or hide effort levels incompatible with the current model to prevent user confusion.

Guidance

  • Identify the current model and its compatible effort levels to determine which options should be hidden or disabled.
  • Modify the UI to grey out or hide incompatible effort levels, such as "xhigh" and "max", when using Sonnet 4.6.
  • Consider adding an inline warning or prompt to inform users that certain effort levels require a different model, like "xhigh requires Opus 4.7 — switch models first?".
  • Verify that the second /effort invocation no longer silently cancels without explanation after implementing the changes.

Example

No code snippet is provided as the issue does not contain sufficient technical details.

Notes

The solution may require modifications to the UI and logic handling effort levels, which could involve updating the application's codebase.

Recommendation

Apply workaround: Modify the UI to hide or disable incompatible effort levels and add inline warnings to prevent user confusion, as upgrading to a fixed version is not mentioned in the issue.

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

claude-code - 💡(How to fix) Fix [Feature Request] Hide or disable /effort levels incompatible with current model [2 comments, 2 participants]