[BUG] Status line disappears after assistant response and does not re-render (still reproducible in 2.1.205, refreshInterval workaround does not help)

Preflight Checklist

• [x] I have searched existing issues and found the closely related #43826 (same symptom, closed as "not planned" on 2.1.84). This report adds new diagnostic evidence and shows the refreshInterval workaround does not fix it.
• [x] This is a single bug report
• [x] I am using the latest version of Claude Code

What's Wrong?

Same core symptom as #43826: the status line renders correctly on session startup, but disappears permanently after an assistant response completes and never re-renders for the rest of the session — even after multiple subsequent turns.

Additionally, I set "statusLine": { "refreshInterval": 10 } (per the official docs' recommended workaround for idle-session cases) hoping periodic forced re-execution would restore rendering. It does not. I instrumented the status line script to append a timestamp to a heartbeat log file on every invocation. After the status line visually disappears, the heartbeat log continues to update every ~10 seconds without interruption — proof that the script keeps executing correctly and Claude Code keeps invoking it, but the terminal output is never redrawn. This points to the bug being in the CLI's render pipeline itself, not in the event-trigger mechanism that #43826 speculated about.

What Should Happen?

The status line should be redrawn every time the configured command script is invoked (whether triggered by an event or by refreshInterval), as described in the documentation.

Error Messages/Logs

No error output, no crash. The script's own heartbeat log confirms successful, uninterrupted execution every ~10s while the terminal shows nothing.

Steps to Reproduce

1. Configure a command-type status line in ~/.claude/settings.json, with refreshInterval: 10:

``json
{
"statusLine": {
"type": "command",
"command": "powershell -File ~/.claude/statusline-command.ps1",
"refreshInterval": 10
}
}
``

1. (Optional, for verification) Add a line to the top of the script that appends Get-Date to a log file, so execution can be confirmed independently of rendering.
2. Start a Claude Code session in VS Code's integrated terminal — status line appears correctly.
3. Send a prompt and wait for the response to complete.
4. Observe: status line disappears and never returns, even though the heartbeat log shows the script is still being invoked on schedule.
5. The only recovery is restarting the Claude Code session.

Claude Model

Sonnet (default)

Is this a regression?

No — this is a continuation of #43826, unresolved since at least 2.1.84.

Last Working Version

N/A — reproducible across all versions I've tested from 2.1.x through the current 2.1.205.

Claude Code Version

2.1.205 (Claude Code)

Platform

Anthropic API (Claude Pro/subscription auth)

Operating System

Windows 11 Pro (10.0.22631)

Terminal/Shell

VS Code integrated terminal (PowerShell), opened as an editor tab (terminal.integrated.defaultLocation: "editor")

Additional Information

• Related: #43826 (same core symptom, closed as "not planned" on 2.1.84), #29383, #25539.
• Ruled out via troubleshooting before filing: terminal line-height threshold bug, CLAUDE_CODE_NO_FLICKER Windows rendering bug (#44119) — both explicitly disabled/mitigated in settings and still not the cause.
• The new evidence here (heartbeat log proving continued script execution during the "frozen" period) suggests this is not merely a missed re-render trigger but a genuine rendering/redraw bug in the CLI itself, since even a forced periodic re-invocation via refreshInterval fails to restore the display.
• Workaround: sending any new message or toggling vim mode sometimes forces a redraw; a full session restart always works.