Bug Description
Title: Custom statusLine command in ~/.claude/settings.json is not executed
Environment:
- Platform: macOS Darwin 24.6.0
- Model: claude-opus-4-5-20251101
Configuration (~/.claude/settings.json):
{
"statusLine": {
"type": "command",
"command": "/Users/jkaster/.claude/statusline-command.sh"
}
}
Expected behavior: The statusLine command script should be called periodically (every ~300ms) when conversation messages update, receiving JSON input via stdin and displaying the first line of stdout as the
status line.
Actual behavior: The script is never called. Adding debug logging to the script confirms no invocations occur - no log file is created.
Verification steps taken:
- JSON syntax validated with jq - valid
- Script is executable (chmod +x) - confirmed -rwxr-xr-x
- Script runs correctly when invoked manually with mock JSON input
- Script outputs single line to stdout with ANSI colors
- No project-level settings override the statusLine config
To reproduce:
- Add statusLine configuration to ~/.claude/settings.json
- Create executable script at the specified path
- Start Claude Code session
- Observe that custom status line never appears and script is never invoked
Environment Info
- Platform: darwin
- Terminal: iTerm.app
- Version: 2.0.62
- Feedback ID: a8fe6feb-5dcf-46c6-ad2d-6e73825b0cff
Errors
Bug Description
Title: Custom statusLine command in ~/.claude/settings.json is not executed
Environment:
Configuration (~/.claude/settings.json):
{
"statusLine": {
"type": "command",
"command": "/Users/jkaster/.claude/statusline-command.sh"
}
}
Expected behavior: The statusLine command script should be called periodically (every ~300ms) when conversation messages update, receiving JSON input via stdin and displaying the first line of stdout as the
status line.
Actual behavior: The script is never called. Adding debug logging to the script confirms no invocations occur - no log file is created.
Verification steps taken:
To reproduce:
Environment Info
Errors