[Bug] PowerShell statusLine stopped rendering after upgrade to v2.1.68 on Windows 11

Bug Description

PowerShell-based statusLine configuration that was working correctly for weeks stopped rendering after upgrading Claude Code to v2.1.68. The status line simply does not appear — no errors, no output, just silently broken.

Environment

• Claude Code version: 2.1.68
• Platform: Windows 11 Pro (10.0.26200)
• Shell: Git Bash (bash)
• Terminal: Windows Terminal
• PowerShell: Windows PowerShell v1.0 (System32)

Configuration

~/.claude/settings.json:

{
  "statusLine": {
    "type": "command",
    "command": "powershell -NoProfile -ExecutionPolicy Bypass -File C:\Users\DavidSoden\.claude\statusline.ps1"
  }
}

The PowerShell script reads JSON from stdin, parses it with ConvertFrom-Json, and outputs ANSI-colored status text via Write-Host -NoNewline. The script executes correctly when tested manually.

Steps to Reproduce

1. Configure a PowerShell-based statusLine command in ~/.claude/settings.json
2. Confirm it works (it did for weeks on prior versions)
3. Upgrade Claude Code to v2.1.68
4. Status line no longer renders

Expected Behavior

The status line should continue to render after upgrading, as it did in previous versions.

Actual Behavior

Status line silently disappears. No error output. The PowerShell script is never invoked.

Workaround

Switching to a bash + python script instead of PowerShell restores functionality:

{
  "statusLine": {
    "type": "command",
    "command": "bash /c/Users/DavidSoden/.claude/statusline.sh"
  }
}

This confirms the issue is specifically with how Claude Code v2.1.68 handles PowerShell-based statusLine commands on Windows, not with the script itself.

Related Issues

• #13517 — Custom statusLine command not being executed
• #17020 — statusLine configuration not working in v2.1.1
• #5754 — Settings deleted on update
• #2690 — Upgrade wiped config files