The statusline issues on macOS — page 2
Issues the maintainers labelled both platform:macos and area:statusline.
150 issues · 25 open · 125 resolved (83%) · first seen Feb 24, 2026
Is this getting better or worse?
This class of problem is converging. 46 new reports in the last 90 days vs 95 in the 90 before — -52%. The open backlog peaked at 37 in 2026-03 and sits at 25 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
113 of these reports name the Claude Code build they were running, spanning 69 releases. Heaviest reporters:
- Claude Code v2.1.81
- Claude Code v2.1.74
- Claude Code v2.1.233
- Claude Code v2.1.170
- Claude Code v2.1.143
- Claude Code v2.1.92
- Claude Code v2.1.87
- Claude Code v2.1.77
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 29 days across 125 closures. Of the 125 closures with a recorded reason, 31% were closed as completed and 86 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
28 of these issues post a workaround someone says worked. The highest-engagement ones:
- [Desktop] Display current worktree/cwd name in app UI (statusLine equivalent)
- …tree name as a badge on the session card Currently the only workaround is to manually run inside every new session, which defeats the convenience of automatic worktree creation. Environment - macOS desktop app (Claude Co…
Found in the description of #60097 · still open - False positive 'Update available' banner when already on latest version
- …hes the cask version) For now, users on the stable cask can work around this by installing instead:
Found in the thread of #49251 · resolved - Status line: no way to distinguish ultracode from xhigh (no `ultracode` field in stdin JSON)
- …e not reflected anywhere in the statusline payload. Current workaround, for anyone landing here: have the statusline script read from with jq and show a marker when it is and the stdin is . That approximates the configur…
Found in the thread of #69068 · still open - Custom statusline colors washed out in truecolor terminals since 2.1.78
- …he terminal advertises truecolor support ( , tmux feature). Workaround None that preserves correct colors. Adjusting RGB values in the script to compensate for the transformation is trial-and-error and doesn't fully rest…
Found in the description of #35806 · resolved - Context usage percentage only counts input tokens, causing misleading 'Context limit reached' at ~20%
- …: 1. field (used by status line scripts) 2. command display Workaround Users can work around this by writing a custom status line script that manually calculates total usage from the individual token fields: Environment…
Found in the description of #28167 · resolved
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 101–150
Ranked by community engagement (reactions weighted over comments).
- [BUG] Statusline JSON: rate_limits.five_hour.used_percentage returns epoch timestamp instead of 0/null when 5h window has no data yet
- `${CLAUDE_PLUGIN_ROOT}` is not expanded for `statusLine.command` (works for hooks/MCP/LSP/monitors)
- [Feature Request] Expose Sonnet model-specific rate limits in statusline JSON
- [Bug] Statusline command triggers unexpected file search and premature auto-compact at 160k tokens
- Update notice shown for Homebrew install that is already at latest version
- OSC 8 hyperlinks stripped in statusline output
- Status line: context percentage text intermittently disappears on re-render
- Statusline Ansi component drops SGR 5 (blink) attribute
- [Feature Request] Add effort level to statusline JSON input and session state exposure
- Status line shows ~200k context remaining when using 1M context window model
- Statusline shows stale team name after TeamDelete
- statusLine: allow custom status to render on same line as built-in permission indicator
- [BUG] Unused MCP server name replaces session title in status bar
- [BUG] Hallucinated user in /Users directory while using /statusline
- Statusline not starting in specific project folder
- [Bug] Incorrect day abbreviation in weekly usage limit message
- [BUG] Session name lost from status line when exiting plan mode
- Multi-line status line causes cursor offset in interactive selection UI
- Support multi-line status line output
- [BUG] status line: all lines beyond the first line disappear when the first line is truncated by "Context low ..." message
- [BUG] Status line JSON contains literal newlines in session_name, breaking jq parsing
- Workspace trust dialog fails to prompt on launch, silently disabling gated features (e.g. statusLine)
- [BUG] Statusline doesn't refresh after /compact
- [BUG] `rate_limits` still missing from statusline JSON on v2.1.228 (macOS, Pro, firstParty auth) — same as closed #40094
- [Feature Request] Display current model name below input area
- statusLine command that fails silently (missing script) renders blank with no error
- [Bug] Context usage percentage displays incorrectly, inconsistent with previous value
- Daily token badge undercounts usage: claude-fable-5 excluded from headline sum but counted in model breakdown %
- [Feature Request] Preserve statusline visibility in selection dialogs
- Statusline corrupts on redraw with double-width Nerd Font glyphs (plane-15 / ≥ U+F0000 undercounted as 1 cell)
- Bug: Remote Control via remoteControlAtStartup has no persistent indicator — startup notice scrolls off, nothing in status line / corner
- [Feature Request] Make worktree/branch label truncation in info bar configurable
- [BUG] Background agent panel no longer visible in v2.1.122+
- /clear drops session_name from statusline JSON input (preserved internally)
- CLAUDE_CODE_NO_FLICKER=1 (fullscreen rendering) breaks statusLine display
- Withdrawn
- [Bug] Status Line not updating while telltale indicator functions correctly
- Feature request: reserved statusline-adjacent region for ambient UI (companions, graphics widgets)
- Stale "Auto-update failed" indicator persists after successful health check, and flickers during response generation
- [FEATURE] Expose usage-credit state to the session (status line payload) — the plan-limit percentage alone makes agents mis-pace
- [FEATURE] Desktop app: show the GitHub issue as a footer chip next to the PR chip (statusLine and footerLinksRegexes are silently inert)
- [Feature Request] Display token count permanently in UI
- [Bug] toggleBrief command lacks visual feedback and statusline state exposure
- Expose Fable weekly usage (seven_day_fable) in status line rate_limits
- [Feature Request] Show task completion percentage in the status line, not just elapsed time
- Footer PR badge stuck on previous PR after switching branches with gh pr checkout
- Custom statusLine command still silently falls back to default in 2.1.215 (regression since 2.1.53, see #28526)
- statusline/cost: session cost ($) and duration not reset by /clear
- [BUG] statusline triggers sysctl command on every run
- [Bug] Anthropic API: claude-sonnet-5 context window reported as 200k instead of 1M tokens