claude-code - 💡(How to fix) Fix /effort displays 'xhigh' instead of 'max' when CLAUDE_CODE_EFFORT_LEVEL=max is set via env var [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#52781Fetched 2026-04-25 06:21:07
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

When CLAUDE_CODE_EFFORT_LEVEL=max is configured in settings.json under the env block, running /effort at the start of a new session displays xhigh instead of max.

Root Cause

When CLAUDE_CODE_EFFORT_LEVEL=max is configured in settings.json under the env block, running /effort at the start of a new session displays xhigh instead of max.

Code Example

{
     "env": {
       "CLAUDE_CODE_EFFORT_LEVEL": "max"
     }
   }
RAW_BUFFERClick to expand / collapse

Summary

When CLAUDE_CODE_EFFORT_LEVEL=max is configured in settings.json under the env block, running /effort at the start of a new session displays xhigh instead of max.

Steps to Reproduce

  1. Set CLAUDE_CODE_EFFORT_LEVEL=max in ~/.claude/settings.json:
    {
      "env": {
        "CLAUDE_CODE_EFFORT_LEVEL": "max"
      }
    }
  2. Start a new Claude Code session
  3. Run /effort

Expected Behavior

/effort should display max as the current effort level, since the env var is active and the docs explicitly state it persists across sessions when configured this way.

Actual Behavior

/effort displays xhigh instead of max, even though the env var is set correctly.

Relevant Documentation

From https://code.claude.com/docs/en/model-config:

low, medium, high, and xhigh persist across sessions. max provides the deepest reasoning with no constraint on token spending and applies to the current session only, except when set through the CLAUDE_CODE_EFFORT_LEVEL environment variable.

This implies max should be a recognized, persistent state when set via CLAUDE_CODE_EFFORT_LEVEL, but /effort does not reflect it.

Notes

The actual effort behavior may still be max — this appears to be a display inconsistency in the /effort command rather than a functional bug. Still, the misleading display makes it hard to verify the setting is taking effect.

extent analysis

TL;DR

The display inconsistency in the /effort command can likely be resolved by updating the settings.json configuration to use a different effort level or by verifying the actual effort behavior despite the display issue.

Guidance

  • Verify that the actual effort behavior is indeed max by checking the output or performance of subsequent commands, as the display inconsistency might not affect the functionality.
  • Check if there are any other configuration options or environment variables that could be overriding the CLAUDE_CODE_EFFORT_LEVEL setting.
  • Consider setting the effort level to a different value (e.g., high or xhigh) to see if the display updates correctly, which could help isolate the issue.
  • Review the documentation again to ensure that the CLAUDE_CODE_EFFORT_LEVEL environment variable is correctly set and recognized by the system.

Example

No code snippet is provided as the issue seems to be related to configuration and display rather than code functionality.

Notes

The provided information suggests that the issue might be specific to the display of the effort level in the /effort command rather than a functional bug. Therefore, the solution might involve updating the configuration or verifying the actual behavior rather than changing code.

Recommendation

Apply workaround: Given the potential display inconsistency, it's recommended to verify the actual effort behavior and consider using a different effort level to test the functionality, rather than relying solely on the display of the /effort command.

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 /effort displays 'xhigh' instead of 'max' when CLAUDE_CODE_EFFORT_LEVEL=max is set via env var [1 comments, 2 participants]