Summary
Not a bug in ccstatusline itself, but a Claude Code behavior change that makes ccstatusline silently disappear for many users — worth a Troubleshooting note in the README.
Since Claude Code 2.1.232, the status line renders as an empty row in any project whose workspace trust was inherited from a parent directory. ccstatusline is never executed at all (verified with a logging wrapper around the command — zero invocations), so nothing on the ccstatusline side can fix or even detect it.
Root cause (Claude Code side)
- Claude Code ≥ 2.1.51 only executes a custom
statusLine command in projects with accepted workspace trust (hasTrustDialogAccepted: true in ~/.claude.json) — a deliberate security gate.
- Before 2.1.232, git repos nested under an already-trusted parent directory (e.g.
~/Projects) inherited trust, the trust dialog never appeared, and the per-project flag stayed at its default false while everything still worked.
- Claude Code 2.1.232 changelog: "Fixed nested git repositories inheriting trust from a parent directory; each repository now requires its own trust confirmation." After updating, every such repo becomes untrusted by its own flag, no trust dialog is re-shown, and the status line just silently goes empty — only in those folders.
The confusing part for users: ccstatusline runs perfectly when invoked manually from the same folder, config is intact, other folders still work → it looks exactly like a ccstatusline bug. In my case dozens of repos under ~/Projects were affected at once.
Fix / workaround
Set "hasTrustDialogAccepted": true for the affected project path in ~/.claude.json (or get Claude Code to show the trust dialog again) and start a new session.
Suggestion
Add a short Troubleshooting entry to the README, something like:
Status line is empty in one specific folder (Claude Code ≥ 2.1.232)?
Claude Code only runs custom status line commands in trusted workspaces. Nested git repositories no longer inherit trust from a parent folder since 2.1.232, and the trust prompt may not reappear. Check hasTrustDialogAccepted for that project path in ~/.claude.json.
I'm also aware the underlying UX regression (no re-prompt, no indication) belongs to anthropics/claude-code; filing here since ccstatusline users are the ones who hit it as "my status line vanished".
Diagnosed on macOS, Claude Code 2.1.232, ccstatusline via npm.
Summary
Not a bug in ccstatusline itself, but a Claude Code behavior change that makes ccstatusline silently disappear for many users — worth a Troubleshooting note in the README.
Since Claude Code 2.1.232, the status line renders as an empty row in any project whose workspace trust was inherited from a parent directory. ccstatusline is never executed at all (verified with a logging wrapper around the command — zero invocations), so nothing on the ccstatusline side can fix or even detect it.
Root cause (Claude Code side)
statusLinecommand in projects with accepted workspace trust (hasTrustDialogAccepted: truein~/.claude.json) — a deliberate security gate.~/Projects) inherited trust, the trust dialog never appeared, and the per-project flag stayed at its defaultfalsewhile everything still worked.The confusing part for users:
ccstatuslineruns perfectly when invoked manually from the same folder, config is intact, other folders still work → it looks exactly like a ccstatusline bug. In my case dozens of repos under~/Projectswere affected at once.Fix / workaround
Set
"hasTrustDialogAccepted": truefor the affected project path in~/.claude.json(or get Claude Code to show the trust dialog again) and start a new session.Suggestion
Add a short Troubleshooting entry to the README, something like:
I'm also aware the underlying UX regression (no re-prompt, no indication) belongs to anthropics/claude-code; filing here since ccstatusline users are the ones who hit it as "my status line vanished".
Diagnosed on macOS, Claude Code 2.1.232, ccstatusline via npm.