statusLine Not Rendering on Windows

Resolved 💬 2 comments Opened May 9, 2026 by ZERO-LOVER Closed Jun 7, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code Issue Report — statusLine Not Rendering on Windows

Title

statusLine.command produces no visible output on Windows (v2.1.138)

Description

I installed the claude-hud plugin and ran /claude-hud:setup, which configured statusLine in my settings.json. After fully restarting Claude Code, I expected to see a HUD/status line below the input prompt, but nothing appears.

Environment

| Item | Value |
|------|-------|
| OS | Windows 11 Pro (10.0.26200) |
| Claude Code | v2.1.138 |
| Terminals tested | IntelliJ IDEA Terminal, Windows PowerShell |
| Node.js | D:\DEV\ENV\nodejs\node.exe (confirmed working) |

Configuration

Relevant excerpt from settings.json:

{
  "statusLine": {
    "type": "command",
    "command": "powershell -Command \"& {$env:COLUMNS=120; $claudeDir=if ($env:CLAUDE_CONFIG_DIR) { $env:CLAUDE_CONFIG_DIR } else { Join-Path $HOME '.claude' };$p=(Get-ChildItem (Join-Path $claudeDir 'plugins\\cache\\*\\claude-hud\\*') -Directory | Where-Object { $_.Name -match '^\\d+(\\.\\d+)+$' } | Sort-Object { [version]$_.Name} -Descending | Select-Object -First 1).FullName; & 'D:\\DEV\\ENV\\nodejs\\node.exe' (Join-Path $p 'dist\\index.js')}\""
  }
}

Steps to Reproduce

  1. Install claude-hud plugin via marketplace.
  2. Run /claude-hud:setup to write the statusLine config to settings.json.
  3. Fully restart Claude Code.
  4. Observe that no status line appears below the input prompt.

Isolation Test

To rule out a plugin-specific issue, I replaced the command with a minimal infinite loop:

powershell -Command "while($true) { Write-Host 'TEST-HUD-LINE'; Start-Sleep -Seconds 3 }"

Expected: The text TEST-HUD-LINE should appear below the input field every 3 seconds.
Actual: Nothing is rendered. The HUD area remains completely empty.

Verification Checklist

  • [x] claude-hud plugin is installed correctly under ~/.claude/plugins/cache/...
  • [x] Running node dist\index.js manually in PowerShell works fine (outputs "Initializing...")
  • [x] settings.json is valid and the statusLine key is present
  • [x] Claude Code was fully restarted between each test
  • [x] Tested in both IntelliJ IDEA Terminal and standalone PowerShell

Conclusion

Since even a basic Write-Host loop produces no output, the statusLine mechanism itself appears to be non-functional on my Windows installation. I would appreciate any guidance or a fix.

What Should Happen?

When statusLine.type is set to "command" in settings.json, the command output should be rendered as a persistent status line below the input prompt in Claude Code. For example, running a simple Write-Host 'TEST-HUD-LINE' loop should display the text at the bottom of the terminal interface, and the claude-hud plugin should show its HUD (session info, tool activity, etc.) after setup and restart.

Error Messages/Logs

Steps to Reproduce

  1. On Windows 11, open Claude Code v2.1.138 in PowerShell or IntelliJ IDEA Terminal.
  2. Install claude-hud via /plugin install claude-hud.
  3. Run /claude-hud:setup and follow the prompts to configure statusLine in settings.json.
  4. Fully restart Claude Code (quit and run claude again).
  5. Observe that no status line appears below the input prompt.
  6. (Minimal isolation) Edit settings.json to replace the statusLine.command with:

```powershell
powershell -Command "while($true) { Write-Host 'TEST-HUD-LINE'; Start-Sleep -Seconds 3 }"

7. Restart Claude Code again — still no output is rendered.

### Claude Model

Other

### Is this a regression?

I don't know

### Last Working Version

v2.1.138

### Claude Code Version

v2.1.138

### Platform

Other

### Operating System

Windows

### Terminal/Shell

IntelliJ IDEA terminal

### Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗