The statusline issues on Linux

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

51 issues · 9 open · 42 resolved (82%) · first seen Jan 30, 2026

Is this getting better or worse?

This class of problem is converging. 13 new reports in the last 90 days vs 21 in the 90 before — -38%. The open backlog peaked at 12 in 2026-08 and sits at 9 today.

0 3 6 9 12 2026-012026-042026-072026-10
2026-01 — First reports2026-03 — Most new reports (10)2026-08 — Peak backlog (12 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

37 of these reports name the Claude Code build they were running, spanning 31 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 34 days across 42 closures. Of the 42 closures with a recorded reason, 12% were closed as completed and 37 as not-planned or duplicate. The most recent completed fix landed in 2026-05.

Workarounds reported by the community

10 of these issues post a workaround someone says worked. The highest-engagement ones:

[FEATURE] Expose current effort level (including "max") in statusLine JSON input
…to display the current effort level accurately. The current workaround is reading from , but this has two problems: 1. "max" effort is session-only and never persisted — the schema enum is , so max isn't stored anywhere…
Found in the description of #34709 · resolved
Let me start a session before deciding which repo to work in
…lidity. 3. refuses subdirectories of the session cwd So the workaround of populating manually doesn't work either: anything under the session cwd is treated as already accessible and skipped, even though the sub-path is…
Found in the description of #61466 · resolved
[BUG] Bottom status row PR badge on long-lived background jobs stays pinned to the first PR ever linked, even after it merges
…on rewrites it from memory on every state change); the only workaround we found is stop the job, strip entries with , then reattach. Why it matters For a short-lived job that produces one PR, first equals latest and the…
Found in the description of #77826 · resolved
Statusline payload reports context_window_size: 200000 on 1M-context session (claude-fable-5) — used_percentage pegs at 100%
…may partly be this root cause where a 1M model is in play. Workaround Statusline scripts can fall back to (which is accurate) and, once it exceeds the reported , infer the 1M window and recompute the percentage locally.
Found in the description of #76751 · resolved
[BUG] Custom statusLine permanently stops being invoked after a subagent/response completes at project scope — but not at user scope
…oad that revives a dead line WITHOUT a full restart (useful workaround, and a hint that the invocation loop can be re-initialized). - Workaround: define in (user scope) instead of project scope. - Possibly related: 21304…
Found in the description of #63973 · 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–51

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. The statusline issues on macOS

    177 issues
  2. The statusline issues on Windows

    84 issues
  3. Model behaviour issues on Linux

    2,108 issues
  4. Core CLI issues on Linux

    1,482 issues
  5. Terminal UI issues on Linux

    1,401 issues
  6. Security issues on Linux

    974 issues
  7. Tool calls issues on Linux

    705 issues
  8. MCP servers issues on Linux

    383 issues