claude-code - 💡(How to fix) Fix statusLine command never invoked when CLAUDE_CODE_NO_FLICKER=1 is set

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…

Custom statusLine commands configured in ~/.claude/settings.json are never invoked when CLAUDE_CODE_NO_FLICKER=1 is set. The status line area is completely blank — the configured script is never executed.

Root Cause

Custom statusLine commands configured in ~/.claude/settings.json are never invoked when CLAUDE_CODE_NO_FLICKER=1 is set. The status line area is completely blank — the configured script is never executed.

Code Example

{
     "statusLine": {
       "type": "command",
       "command": "/path/to/statusline.sh",
       "refreshInterval": 5
     }
   }
RAW_BUFFERClick to expand / collapse

Description

Custom statusLine commands configured in ~/.claude/settings.json are never invoked when CLAUDE_CODE_NO_FLICKER=1 is set. The status line area is completely blank — the configured script is never executed.

Reproduction

  1. Configure a custom statusLine in ~/.claude/settings.json:
    {
      "statusLine": {
        "type": "command",
        "command": "/path/to/statusline.sh",
        "refreshInterval": 5
      }
    }
  2. Verify the script works manually: echo '{}' | /path/to/statusline.sh produces output.
  3. Launch Claude Code with CLAUDE_CODE_NO_FLICKER=1 exported.
  4. The status line area is blank. Adding a probe (echo "$(date)" >> /tmp/probe.log) to the script confirms it is never called.

Expected behavior

The statusLine command should be invoked and its output rendered in NO_FLICKER mode, same as in standard mode.

Environment

  • Claude Code version: 2.1.137
  • OS: macOS 15.5 (Darwin 24.6.0, arm64)
  • Terminal: Ghostty
  • Shell: zsh

Context

NO_FLICKER mode is the only usable rendering mode for some terminal setups — standard mode produces unusable flickering. Losing the status line to get stable rendering is a significant trade-off, especially since the status line is the primary way to surface project context (model, branch, health) without scrolling.

Related: #13517 (same symptom reported for standard mode)

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…

FAQ

Expected behavior

The statusLine command should be invoked and its output rendered in NO_FLICKER mode, same as in standard mode.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING