Status bar shows 'max effort' while /effort slider indicates xhigh

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.