Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] statusLine regression in v2.1.119 — command not executed on Windows [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52997•Fetched 2026-04-25 06:15:10
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
LorenzKuengLorenzKueng
Participants
github-actions[bot]github-actions[bot]LorenzKuengLorenzKueng
Timeline (top)
labeled ×4commented ×1

The statusLine feature stopped working after upgrading from v2.1.112 to v2.1.119 on Windows 11. The status line was displaying correctly on v2.1.112 and disappeared after the upgrade. Confirmed on two separate Windows 11 machines.

Root Cause

The statusLine feature stopped working after upgrading from v2.1.112 to v2.1.119 on Windows 11. The status line was displaying correctly on v2.1.112 and disappeared after the upgrade. Confirmed on two separate Windows 11 machines.

Code Example

{
  "statusLine": {
    "type": "command",
    "command": "python C:/Users/Kueng/.claude/statusline-command.sh"
  }
}

---

echo '{"model":{"display_name":"Claude Sonnet 4.6"},"context_window":{"used_percentage":10}}' | python statusline-command.sh
# Output: Claude Sonnet 4.6 | Context: 10% used
RAW_BUFFERClick to expand / collapse

Description

The statusLine feature stopped working after upgrading from v2.1.112 to v2.1.119 on Windows 11. The status line was displaying correctly on v2.1.112 and disappeared after the upgrade. Confirmed on two separate Windows 11 machines.

Steps to Reproduce

  1. Configure a statusLine command in ~/.claude/settings.json:
{
  "statusLine": {
    "type": "command",
    "command": "python C:/Users/Kueng/.claude/statusline-command.sh"
  }
}
  1. Run claude in PowerShell 7 or Command Prompt
  2. Send a message

Expected Behavior

Status line displays at the bottom of the Claude Code interface showing model name, context window usage, and session usage.

Actual Behavior

No status line appears. The script executes correctly when run manually (piping JSON to it produces the expected output), so the issue is that Claude Code is not invoking the command.

Environment

  • Claude Code version: 2.1.119
  • Last working version: 2.1.112
  • OS: Windows 11 Pro
  • Shells tested: PowerShell 7, Command Prompt
  • Python version: 3.11.9

Additional Context

The script works correctly when tested manually:

echo '{"model":{"display_name":"Claude Sonnet 4.6"},"context_window":{"used_percentage":10}}' | python statusline-command.sh
# Output: Claude Sonnet 4.6 | Context: 10% used

This appears related to #31670 and #50679.

extent analysis

TL;DR

The issue is likely due to a change in how Claude Code invokes external commands, and a workaround may involve modifying the statusLine configuration or the script itself.

Guidance

  • Verify that the statusline-command.sh script has execute permissions and can be run from the same directory where Claude Code is executed.
  • Check the Claude Code documentation for any changes to the statusLine feature between versions 2.1.112 and 2.1.119, specifically regarding command invocation.
  • Test the script with a simpler command, such as echo, to isolate the issue.
  • Consider modifying the statusLine configuration to use a different command or script that does not rely on piping JSON input.

Example

No code snippet is provided as the issue seems to be related to command invocation rather than code syntax.

Notes

The issue may be related to changes in how Claude Code handles external commands or JSON input, as hinted by the referenced GitHub issues (#31670 and #50679). Further investigation into the changes between versions 2.1.112 and 2.1.119 is necessary.

Recommendation

Apply workaround: Modify the statusLine configuration or the script itself to accommodate any changes in how Claude Code invokes external commands, as the root cause is likely related to this change.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#orchestration issue#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING