claude-statusbar control skill

Use this skill any time the user wants to inspect, change, customize, or diagnose the cs status bar. Replaces the older individual slash commands (/statusbar, /statusbar-theme, /statusbar-style, /statusbar-preview, /statusbar-doctor, /statusbar-reset) — they still work but this skill covers all of them with conversational intent.

Decision tree

Match the user's intent to the right cs command. Run it via Bash, then give a short confirmation (one line, no lecture).

No-quota mode (third-party relay / Bedrock / Vertex)

When Claude Code points at a third-party relay (ANTHROPICBASEURL ≠ api.anthropic.com) or a cloud backend (CLAUDECODEUSEBEDROCK / CLAUDECODEUSEVERTEX), the official 5h/7d quota doesn't exist. cs detects this and switches to a no-quota layout: the two quota battery bars are dropped and the context window is promoted to its own ctx[…] battery bar (green→yellow→red on 70/85% used), followed by the model name + the usual live-activity tail. This mirrors claude-hud's behavior and is what to reach for when a user says "用 API 就没状态了 / 连上下文都没了".

• Detection is automatic (api_mode = auto, the default). A transcript-based

heuristic also catches relays whose env var didn't reach the statusLine subprocess (an assistant turn exists yet quota never arrived → no-quota).

• Force it on a setup where auto-detect misses: cs config set api_mode on

(or per-shell CSAPIMODE=on). Force the official layout back with apimode off. CSAPI_MODE env wins over the saved config.

• Works under both the inline and fast-mode (daemon) render paths.

AgentParty / Codex bridge line

Claude Code support is the full native statusLine integration configured by cs --setup. Codex support is narrower: when AgentParty writes ~/.agentparty/state/<workspaceId>/statusline.json for the current workspace, cs appends a local-only line with channel, human/agent identity, listener mode, unread count, and last-message preview.

Use cs config set show_party false to hide it. This bridge never calls the AgentParty CLI, reads tokens, or makes network requests.

Per-severity color overrides (v3.4.1+)

The user can override the three severity colors independently of theme:

cs config set color_ok   "#4ec85b"   # calm / safe
cs config set color_warn "#e8b260"   # warning
cs config set color_hot  "#e87474"   # critical

cs config set color_ok ""            # clear back to theme default

Accepts #rrggbb, #rgb, or bare rrggbb. The override layers on top of whatever theme is active — no need to switch theme just to tune one color.

When user says "make 余量颜色 / safe color / green sharper", "warning 偏淡", "critical too red" — go to the override, not the theme.

Vibe → theme suggestion

If the user describes a vibe instead of naming a theme, suggest one and ask before switching:

Render anatomy (so you can explain what you're changing)

5h[██16% ░░░]⏰2h27m | 7d[██32%  ░░]⏰4d05h | Opus 4.7(280k/1M) | $ 1.42 | cache 4m23s
└─ 5h ─────┘└──5h──┘  └─ 7d ──┘ └─7d─┘   └────context───────┘  └cost┘  └─cache─┘

Every numeric segment colors itself by its own severity (since v3.4):

• 5h → theme.s* chosen from msgspct
• 7d → theme.s* chosen from weeklypct
• model+context → theme.s* chosen from ctxused_pct (None → neutral)
• cache → its own string-age severity (COLD → red, <1m → yellow, else green)
• [ ], ( ), | → theme.mute (recede behind data)

Common diagnostic flows

"Status bar isn't showing" → cs doctor. It self-checks:

• Claude Code's ~/.claude/settings.json has the statusLine block
• the cs binary is on PATH
• whether the daemon is alive (if fast-mode configured)
• whether the cache files are stale

"refreshInterval too high" → cs doctor will recommend cs --setup --fast when it sees refreshInterval ≤ 2s on the inline command. Fast mode drops 1Hz CPU from ~6% to ~2%.

"Color won't change after cs config set theme X" → check the user isn't on a Claude Code session that read settings.json at start. Ask them to send a new prompt; the next render picks up the new theme.

"Codex / AgentParty name isn't showing" → confirm AgentParty has written ~/.agentparty/state/<workspaceId>/statusline.json for the current cwd and that show_party is still true.

Don't

• Don't lecture about ANSI codes or terminal compatibility unless asked.
• Don't suggest editing ~/.claude/claude-statusbar.json by hand. Use

cs config set <key> <value>.

• Don't change theme just to fix one color — use `colorok / colorwarn /

color_hot` overrides.

• Don't run destructive commands (cs config reset, cs daemon stop)

without confirming with the user.

Style of response

Be terse. Run the command, paste the one-line confirmation, point at the next step if relevant. The status bar is on screen — they can see the result immediately, no need to describe it.