The statusline issues on macOS

Issues the maintainers labelled both platform:macos and area:statusline.

177 issues · 33 open · 144 resolved (81%) · first seen Feb 24, 2026

Is this getting better or worse?

This class of problem is converging. 44 new reports in the last 90 days vs 59 in the 90 before — -25%. The open backlog peaked at 37 in 2026-03 and sits at 33 today.

0 9 19 28 37 2026-022026-052026-082026-10
2026-02 — First reports2026-03 — Peak backlog (37 open)

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

138 of these reports name the Claude Code build they were running, spanning 84 releases. Heaviest reporters:

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 30 days across 144 closures. Of the 144 closures with a recorded reason, 28% were closed as completed and 104 as not-planned or duplicate. The most recent completed fix landed in 2026-10.

Workarounds reported by the community

35 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 1–100

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. The statusline issues on Windows

    84 issues
  2. The statusline issues on Linux

    51 issues
  3. Terminal UI issues on macOS

    3,716 issues
  4. Core CLI issues on macOS

    3,648 issues
  5. Model behaviour issues on macOS

    3,249 issues
  6. The desktop app issues on macOS

    2,253 issues
  7. Tool calls issues on macOS

    1,780 issues
  8. MCP servers issues on macOS

    1,686 issues