The statusline issues on Windows
Issues the maintainers labelled both platform:windows and area:statusline.
84 issues · 17 open · 67 resolved (80%) · first seen Feb 24, 2026
Is this getting better or worse?
This class of problem is converging. 23 new reports in the last 90 days vs 32 in the 90 before — -28%. The open backlog peaked at 17 in 2026-09 and sits at 17 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
48 of these reports name the Claude Code build they were running, spanning 37 releases. Heaviest reporters:
- Claude Code v2.1.74
- Claude Code v2.1.268
- Claude Code v2.1.260
- 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
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 67 closures. Of the 67 closures with a recorded reason, 12% were closed as completed and 59 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
31 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 - [Windows] Cancelled statusLine commands leave permanently suspended child processes
- …sline runs. Shell-form hooks still need the Job Object fix. Workaround in use: an async SessionStart hook in exec form that kills , and with one suspended thread, 0 CPU time and an age over 120 s, plus whose parent is go…
Found in the thread of #98976 · still open - Ultracode arms with no ultracode setting in any scope; header shows plain "with xhigh effort" while it is active
- …exists anywhere on disk is a session title I typed by hand as a workaround ( , ) - which is rather the point: the only way to see the state is to write it down yourself. So the arming is real, session-only, and recorded…
Found in the thread of #91033 · still open
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–84
Ranked by community engagement (reactions weighted over comments).
- Desktop app: bring back the context-usage indicator (or make the footer widget configurable)
- 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
- Fable 5.1 weekly limit is never surfaced in the CLI: the client receives it, labels it 'Fable', then drops it
- [Feature Request] Persist per-model weekly rate limits in statusLine payload
- Windows: statusline cancellation (taskkill /T) and cross-session liveness probes overload WMI - WmiPrvSE pinned at 300-550% CPU with ~10 concurrent sessions
- [Windows] Cancelled statusLine commands leave permanently suspended child processes
- Ultracode arms with no ultracode setting in any scope; header shows plain "with xhigh effort" while it is active
- 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
- 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)
- Windows: per-second statusLine bash spawns turn the MSYS add_item/errno 1 race into a permanent outage of every Bash call
- German status line: "Läuft einem Befehl" — wrong case and wrong verb for "Running a command"
- [BUG] Server-managed `allowManagedHooksOnly: true` silently disables custom statusLine (contradicts docs)
- 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)
- Expose current permission mode in statusline JSON
- [BUG] context_window.used_percentage includes cache_read_input_tokens, inflated after /clear
- 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
- 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
- [BUG] Status line disappears after assistant response and does not re-render (still reproducible in 2.1.205, refreshInterval workaround does not help)
- [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] statusline-setup agent generates jq-dependent script that fails on Windows
- Feature request: configurable statusLine position (below the mode/footer line)
- 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
- statusline: individual rate_limits windows are omitted instead of null, so a status line cannot tell "unknown" from "0% used"
- statusLine command fails silently on Windows when path contains spaces (no Git Bash, quotes stripped by `powershell -Command`)
- [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)
- [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] 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)
- [BUG] VS Code extension: bottom status-bar model chip shows stale "Sonnet 4.6" even though /model and the current model are correctly "Sonnet 5"
- Context ring no longer warns before the window limit — session died at 'Prompt is too long' with no prior warning
- Windows: statusline pwsh.exe processes never exit -- hundreds of orphans per hour under multi-session use
- 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)
- Usage credits indicator always shows $ (USD) even when account is billed in a different currency (e.g. BRL)
- CLAUDE_CODE_NO_FLICKER=1 suppresses custom statusLine command on Windows CLI
- [FEATURE] Expose MCP server connection status to statusLine commands and hooks
- [FEATURE] statusLine payload: expose the focused subagent view's model/effort (and repaint on view switch)
- [BUG] Visible thinking uses whimsical/cutesy verbs even after explicit instruction to stop
- Status line configured in settings.json is never executed/rendered on native Windows (v2.1.268)
- Status line: expose per-model weekly rate limit (Fable) in rate_limits, or keep cachedUsageUtilization fresh
- [BUG] GitButler diff stat counts appear inflated/incorrect in status bar
- [BUG] statusline JSON keeps workspace.current_dir at the launch directory after EnterWorktree, so the status line shows the wrong directory and branch for the rest of the session (2.1.251)
- Statusline Nerd Font glyphs render as literal \uXXXX escapes only in Agent-Teams tmux-spawned panes