Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] CLAUDE_CODE_EFFORT_LEVEL=max displays as xhigh in /effort effort slider on v2.1.111 [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#49281•Fetched 2026-04-17 08:45:42
View on GitHub
Comments
1
Participants
2
Timeline
10
Reactions
0
Author
silentsilenceesilentsilencee
Participants
github-actions[bot]github-actions[bot]silentsilenceesilentsilencee
Timeline (top)
labeled ×3cross-referenced ×2renamed ×2subscribed ×2

Error Message

Error Messages/Logs

Root Cause

It is unclear whether this is: (a) purely a UI display bug where max is correctly active at the API layer but rendered as xhigh in the slider, or (b) a validation bug where max is being silently coerced/downgraded to xhigh because the new xhigh tier was introduced without updating all the level-resolution logic.

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?

When CLAUDE_CODE_EFFORT_LEVEL=max is set as an environment variable (or when effortLevel: "max" is set in ~/.claude/settings.json), the /model command's effort slider displays the current level as xhigh rather than max.

The slider UI shows five tiers: low | medium | high | xhigh | max. Despite max being explicitly configured, the slider position lands on xhigh.

It is unclear whether this is: (a) purely a UI display bug where max is correctly active at the API layer but rendered as xhigh in the slider, or (b) a validation bug where max is being silently coerced/downgraded to xhigh because the new xhigh tier was introduced without updating all the level-resolution logic.

I believe it is surfaced more visibly by the recent addition of the xhigh tier released with Opus 4.7.

What Should Happen?

When CLAUDE_CODE_EFFORT_LEVEL=max is set, the /model slider should display the position as max (the rightmost tier), matching the configured value.

Additionally, /effort with no arguments should report the active level and its source (env var, settings file, session override, etc.) so users can verify the configured value is actually in effect, independent of the slider display.

Error Messages/Logs

Steps to Reproduce

  1. Install Claude Code v2.1.111 on macOS (native binary install at ~/.local/share/claude/versions/2.1.111).

  2. Set the effort level to max via environment variable. For example, in a shell wrapper or .zshrc

  3. Launch a new Claude Code session

  4. Observe the effort slider. The position is on xhigh, not max, despite max being explicitly configured.

Environment:

  • OS: macOS
  • Claude Code version: 2.1.111
  • Install type: native binary (standalone installer, not npm)
  • Model: opus[1m]
  • Shell: zsh

Claude Model

Opus

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

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The effort slider in Claude Code may be displaying xhigh instead of max due to a potential validation bug or UI display issue, and verifying the active effort level through the /effort command without arguments can help determine if it's a display issue or an actual configuration problem.

Guidance

  • Verify the actual effort level in effect by running the /effort command without arguments to see if it reports max as the active level, which can help distinguish between a UI display bug and a validation bug.
  • Check the ~/.claude/settings.json file to ensure that effortLevel is set to "max" to confirm the configuration source.
  • Test setting the effort level to max through different methods (environment variable vs. settings file) to see if the issue persists across configurations.
  • Consider comparing the behavior with previous versions where this worked to identify any changes that might have introduced this issue.

Example

No specific code example is applicable here, but running /effort in the Claude Code session could output something like:

Active effort level: max (source: environment variable)

or

Active effort level: xhigh (source: environment variable)

which would indicate whether the issue is with the display or the actual configuration.

Notes

The introduction of the xhigh tier with Opus 4.7 seems to coincide with the appearance of this issue, suggesting that the problem might be related to how the new tier is handled in the level-resolution logic.

Recommendation

Apply a workaround by closely monitoring the output of the /effort command to verify the active effort level, as this can provide insight into whether the max level is being correctly applied despite the UI display 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…
#api#installation#tensor shape#autograd error#environment variable

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 [BUG] CLAUDE_CODE_EFFORT_LEVEL=max displays as xhigh in /effort effort slider on v2.1.111 [1 comments, 2 participants]