Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Status bar shows 'max effort' while /effort slider indicates xhigh [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#53217•Fetched 2026-04-26 05:21:22
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
ryofukutaniryofukutani
Participants
github-actions[bot]github-actions[bot]ryofukutaniryofukutani
Timeline (top)
labeled ×3commented ×1

The status bar effort label and the actual effort setting (as shown by the /effort slider) are inconsistent. The status bar reports with max effort, but /effort confirms the active setting is xhigh.

Root Cause

The status bar effort label and the actual effort setting (as shown by the /effort slider) are inconsistent. The status bar reports with max effort, but /effort confirms the active setting is xhigh.

Code Example

Whatchamacalliting… (15m 33s · ↓ 47.6k tokens · almost done thinking with max effort)
RAW_BUFFERClick to expand / collapse

Summary

The status bar effort label and the actual effort setting (as shown by the /effort slider) are inconsistent. The status bar reports with max effort, but /effort confirms the active setting is xhigh.

Steps to Reproduce

  1. Start a Claude Code session on Opus 4.7 (1M context) with effort set to xhigh (via /effort, env, or settings.json).
  2. Submit a prompt that triggers a long thinking phase.
  3. Observe the status bar message during thinking.
  4. Run /effort to confirm the active setting.

Actual Behavior

Status bar message during thinking (verbatim copy-paste):

Whatchamacalliting… (15m 33s · ↓ 47.6k tokens · almost done thinking with max effort)

/effort slider shows the pointer on xhigh (not max).

Expected Behavior

Status bar message should reflect the active effort level. With xhigh active, it should read e.g. with xhigh effort, not with max effort.

Impact

  • Cosmetic, but misleading: a user reading max effort may believe they are paying for / running the highest tier when they are one step below.
  • Token budgets and latency expectations may be misset based on the displayed label.

Environment

  • Claude Code version: 2.1.120
  • OS: macOS 26.2 (Build 25C56)
  • Model: Opus 4.7 (1M context) — claude-opus-4-7[1m]
  • Active effort: xhigh (confirmed via /effort slider)
  • Mode: Auto mode active

Notes

  • Filed by Claude Code on behalf of the user after the user copy-pasted the status bar text verbatim.
  • Slider screenshot (effort = xhigh) was reviewed by Claude Code in-session but is not attached here; reproducible from the steps above.

extent analysis

TL;DR

Update the status bar label to reflect the actual effort setting, which is xhigh, to ensure consistency with the /effort slider.

Guidance

  • Verify that the effort setting is correctly stored and retrieved from the settings.json file or environment variables.
  • Check the code responsible for updating the status bar message to ensure it uses the correct effort setting value.
  • Review the mapping between effort settings and their corresponding labels to ensure xhigh is correctly mapped to its label.
  • Test the fix by running the steps to reproduce and confirming the status bar message reflects the correct effort setting.

Example

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

Notes

The fix may require updating the code that generates the status bar message to use the correct effort setting value. Additionally, the issue may be specific to the Opus 4.7 model or Claude Code version 2.1.120.

Recommendation

Apply a workaround to update the status bar label to reflect the actual effort setting, as the issue is cosmetic but misleading, and a full fix may require code changes.

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…
#retriever error#indexing error#inference speed#output truncation#response parsing

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 Status bar shows 'max effort' while /effort slider indicates xhigh [1 comments, 2 participants]