Custom statusLine command stopped working in 2.1.53+

Resolved 💬 7 comments Opened Feb 25, 2026 by colangelo Closed Mar 28, 2026

Bug Report

Custom statusLine with type: "command" stopped rendering in versions 2.1.53, 2.1.54, 2.1.55, and 2.1.56. Works correctly in 2.1.52.

Configuration

"statusLine": {
    "type": "command",
    "command": "node \"/Users/<redacted>/.config/claude/statusline-command.js\""
}

in ~/.claude/settings.json.

Steps to Reproduce

  1. Configure a custom statusLine command in settings.json (even "command": "echo HELLO" fails)
  2. Start Claude Code on any version from 2.1.53 to 2.1.56
  3. Observe: no custom status line rendered, falls back to default

Expected Behavior

Custom statusLine command output should be displayed at the bottom of the terminal, as it does in 2.1.52.

Actual Behavior

The custom statusLine is completely absent. The default Claude Code status line is shown instead (or nothing at all).

Debugging Done

  • The JS script runs correctly when invoked manually (echo '{}' | node statusline-command.js produces output)
  • Tested with a trivial "command": "echo TEST" — also fails on 2.1.53+, works on 2.1.52
  • No changes to settings.json between working and broken versions
  • disableAllHooks is not set
  • Tested on macOS 26.3 (Apple Silicon)

Workaround

Pinned to 2.1.52 via npm install -g @anthropic-ai/claude-code@2.1.52.

Environment

  • macOS 26.3 (Darwin 25.3.0, Apple Silicon)
  • Terminal: iTerm2 + tmux next-3.7
  • Node: v22.x
  • Claude Code installed via npm

View original on GitHub ↗

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