claude-code - 💡(How to fix) Fix [BUG] 2.1.111 on $200 Max auto select xhigh effort on update, auto effort removed [3 comments, 3 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#49237Fetched 2026-04-17 08:46:56
View on GitHub
Comments
3
Participants
3
Timeline
7
Reactions
0
Author
Timeline (top)
commented ×3labeled ×3closed ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Updated to v2.1.111 on a Max $200 plan. Previously used model 4.6 with medium/auto effort. On selecting Recommended Opus 4.7, effort selected was xhigh instead of medium. Auto effort removed. Placing effort next to max will waste thousands of tokens

What Should Happen?

Effort selection should mirror prior selection in 2.1.210 or medium as a proper default.

Error Messages/Logs

Steps to Reproduce

  1. update Claude CLI
  2. start claude cli
  3. /model select Opus 4.7 (recommended)
  4. type /effort to see effort at xhigh

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.111

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

No response

extent analysis

TL;DR

The issue can likely be mitigated by manually setting the effort to "medium" after selecting the Opus 4.7 model.

Guidance

  • Verify that the issue is indeed a regression by checking the behavior in the previous version (if possible) to confirm that the effort selection was preserved.
  • Try setting the effort to "medium" manually using the /effort command after selecting the Opus 4.7 model to see if this resolves the issue.
  • If the issue persists, consider reporting the desired default effort behavior as a feature request or bug to the developers.
  • Check the documentation for any updates on the default effort settings for the Opus 4.7 model.

Notes

The lack of information on the last working version and additional details might limit the ability to provide a comprehensive fix.

Recommendation

Apply workaround: Manually set the effort to "medium" after selecting the Opus 4.7 model, as this seems to be the intended default behavior based on the user's expectations.

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