The statusline issues on Windows
Issues the maintainers labelled both platform:windows and area:statusline.
70 issues · 13 open · 57 resolved (81%) · first seen Feb 24, 2026
Is this getting better or worse?
This class of problem is converging. 22 new reports in the last 90 days vs 44 in the 90 before — -50%. The open backlog peaked at 14 in 2026-05 and sits at 13 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
40 of these reports name the Claude Code build they were running, spanning 31 releases. Heaviest reporters:
- Claude Code v2.1.74
- Claude Code v2.1.237
- Claude Code v2.1.150
- Claude Code v2.1.143
- Claude Code v2.1.117
- Claude Code v2.1.92
- Claude Code v2.1.83
- Claude Code v2.1.71
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 31 days across 57 closures. Of the 57 closures with a recorded reason, 14% were closed as completed and 49 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
25 of these issues post a workaround someone says worked. The highest-engagement ones:
- Context window status bar shows 200k for Claude Sonnet 4.6, but model supports 1M tokens
- …lls still use the full 1M window for requests. No user-side workaround Since this is a hardcoded internal model config, there's no way for the user to override it. The display will show 200K until the CLI is updated with…
Found in the thread of #61734 · resolved - effortLevel "max" not serialized to settings.json and not passed to statusLine stdin
- …30:02Z) - OS: Windows 11 Pro - Model: Opus 4.6 (1M context) Workaround None currently available. Custom statusLine scripts cannot detect "max" effort level from either stdin JSON or settings.json fallback.
Found in the description of #34837 · resolved - Windows: statusline cancellation (taskkill /T) and cross-session liveness probes overload WMI - WmiPrvSE pinned at 300-550% CPU with ~10 concurrent sessions
- …) can be avoided on machines where MSYS2 bash is unreliable Workaround that resolved it here - Ported the statusline script to Node (80 ms vs 481 ms, output identical) so renders finish inside the 300 ms debounce window…
Found in the description of #73785 · resolved - Status bar / token counter freezes during long single Write tool calls (desktop app)Status bar / token counter freezes during long single Write tool calls (desktop app)
- …t + show the active tool name, same as any other tool call. Workaround Any keystroke in the input box (even a single letter, Enter not required) snaps the UI back to live. The typed keystroke is delivered to the model as…
Found in the description of #46614 · resolved - VS Code extension runs statusLine (never rendered in IDE) -> focus/panel-reveal war across multiple chat sessions in one window (Windows)
- …s apart = normal "a chat produced output" reveals, no war): Workaround Remove the config from . Eliminates the war immediately. Expected The VS Code extension should not execute in IDE mode (it renders no status line), o…
Found in the description of #70497 · 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–70
Ranked by community engagement (reactions weighted over comments).
- Context window status bar shows 200k for Claude Sonnet 4.6, but model supports 1M tokens
- [Bug] Statusline command not executed on Windows in v2.1.71
- effortLevel "max" not serialized to settings.json and not passed to statusLine stdin
- used_percentage uses wrong context window size for 1M context models
- [BUG] Misreporting of model in status line
- [BUG] [VS Code Extension] Restore context window usage percentage indicator
- [Windows] Statusline and hook commands spawn bash.exe without CREATE_NO_WINDOW, causing visible console flash every ~10 seconds
- Add persistent usage/credit display to Claude Code
- Docs/bug: statusLine.command silently fails on Windows when path contains unquoted backslashes (Git Bash interaction)
- [Chat] Display context window usage percentage indicator
- Windows: statusline cancellation (taskkill /T) and cross-session liveness probes overload WMI - WmiPrvSE pinned at 300-550% CPU with ~10 concurrent sessions
- statusLine Not Rendering on Windows
- Status bar / token counter freezes during long single Write tool calls (desktop app)Status bar / token counter freezes during long single Write tool calls (desktop app)
- VS Code extension runs statusLine (never rendered in IDE) -> focus/panel-reveal war across multiple chat sessions in one window (Windows)
- [BUG] statusLine command receives "high" instead of "xhigh" for effort level
- Expose current permission mode in statusline JSON
- [BUG] context_window.used_percentage includes cache_read_input_tokens, inflated after /clear
- Desktop app: bring back the context-usage indicator (or make the footer widget configurable)
- statusLine command: terminal_width missing from JSON input
- [BUG] StatusLine command exits 126 when spawned by Claude Code, exit 0 when invoked manually (Windows / Git Bash)
- statusLine: external binaries produce no captured stdout — requires bash -c wrapper
- Custom statusline doesn't refresh after /rename
- [Bug] Unable to exit /status command with ESC or CTRL+C
- [BUG] /clear accumulates session cost in status line instead of resetting to $0.00
- .claude.json corrupted with 'Unexpected EOF' when statusline is enabled — race condition
- Feature request: Allow users to disable the 'ctrl+c to copy' hint in status bar
- [BUG] Branch indicator in status bar does not update when branch changes mid-session
- [BUG] statusline-setup agent generates jq-dependent script that fails on Windows
- Add Windows Terminal to OSC 8 hyperlink auto-detect allowlist
- Statusline: context_window.used_percentage always 0 on native Windows (Git Bash)
- [Feature Request] Expose effortLevel in statusLine.command JSON payload
- [BUG] Status bar no longer shows repository name, only branch name
- [BUG] ssh remote hostname no longer visible
- [Bug] StatusLine agent generates incompatible bash script for Windows Git Bash environments
- Feature request: PostCompact hook + statusline refresh after /compact
- [BUG] Status line feature has external dependencies (jq, bc) and no working default
- [BUG] Running-task activity header leaks from the working session into other idle sessions of the same project
- [BUG] Statusline not displaying on Windows [fixed]
- [BUG] pwsh.exe FailFast (0xE9 ERROR_PIPE_NOT_CONNECTED) in ConsoleHost.Start, triggered by spawned statusline / hook subprocesses on Windows
- [BUG] CONSISTENT AND AGGRESSIVE PUSH BY CLAUDE TO CLEAR CONTEXT "new task? /clear to save 189.6k tokens"
- Feature request: configurable statusLine position (below the mode/footer line)
- [Feature Request] Display context usage and token limit progress bars in CLI prompt
- statusLine: add optional periodic refresh interval
- [BUG] Edited N times
- [FEATURE] Add context usage indicator so users can gauge how full the context window is
- [Feature Request] Allow statusline scripts to set session color and name via JSON control messages
- C:/Program Files/Git/clear leaves stale agent entries in the Agents status panel
- [Bug] Statusline setup not working - pls help
- Add rate limit utilization to statusLine JSON
- [Bug] Status line not always visible
- Custom statusLine command resets shell CWD between Bash tool calls
- [BUG] status line in win11 powershell does not stay on the bottom but stays at the start of the conversation
- Feature: Expose sub-agent context window usage in statusline / parent session telemetry
- [BUG] StatusLine intermittently renders '…' on 2.1.52 (Windows)
- German status line: "Läuft einem Befehl" — wrong case and wrong verb for "Running a command"
- statusLine command fails silently on Windows when path contains spaces (no Git Bash, quotes stripped by `powershell -Command`)
- [BUG] Status line disappears after assistant response and does not re-render (still reproducible in 2.1.205, refreshInterval workaround does not help)
- Usage credits indicator always shows $ (USD) even when account is billed in a different currency (e.g. BRL)
- [BUG] Status line never renders on Windows Terminal in Claude Code 2.1.202: XTVERSION query gets no reply through ConPTY.
- French sessions: activity status line produces French/English hybrid words (e.g. "Inventaired")
- [BUG] Windows paths with backslashes in settings.json statusLine.command are double-unescaped
- [BUG] rate_limits absent from statusLine JSON for Claude Max plan (v2.1.156, Windows)
- CLAUDE_CODE_NO_FLICKER=1 suppresses custom statusLine command on Windows CLI
- Statusline Nerd Font glyphs render as literal \uXXXX escapes only in Agent-Teams tmux-spawned panes
- [Feature Request] Persist per-model weekly rate limits in statusLine payload
- Windows: statusline pwsh.exe processes never exit -- hundreds of orphans per hour under multi-session use
- [BUG] Server-managed `allowManagedHooksOnly: true` silently disables custom statusLine (contradicts docs)
- Windows Terminal: status glyph renders in arbitrary color via system emoji font, not a fixed/brand color
- [BUG] Windows + Git Bash: statusLine/hook command paths with backslashes are silently mangled - status line never renders (root cause behind #57629)
- Claude Desktop app reports 200k context for Sonnet 5; CLI reports 1M (same account/model)