| name | claude-statusbar |
| description | Manage `cs` (claude-statusbar) — switch theme/style/density, override severity colors, preview combinations, run doctor, reset config, install, upgrade (`cs upgrade` — the only supported upgrade path), or remove the bar, toggle fast/daemon mode, show cost or prompt-cache age, or toggle the AgentParty/Codex bridge line. Use whenever the user mentions cs, claude-statusbar, status bar, status line, 状态栏, AgentParty, Codex, show_party, 主题, theme switching, style switching, color customization, 余量颜色, 警告颜色, severity color, /statusbar, cs preview, cs doctor, fast mode, daemon, refreshInterval, 5h/7d window, context window display, prompt cache, or asks to install / upgrade / update / 升级 / configure / diagnose / customize the bottom status line in Claude Code or Codex/AgentParty workflows. |
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).
| User intent | Command |
|---|
| Inspect current config | cs config show |
| List themes | cs themes |
| List styles | cs styles |
Switch theme to <name> | cs config set theme <name> |
Switch style to <name> | cs config set style <name> |
| Change density | cs config set density <compact|regular|cozy> |
| Show all 27 combinations | cs preview |
| Filter preview to one style/theme | cs preview --style <s> or cs preview --theme <t> |
| Diagnose problem | cs doctor |
| Wipe config | cs config reset |
| Install / first-time setup | cs --setup |
| Upgrade / update to latest version | cs upgrade — NEVER guess uv tool install / pip install -U / pipx upgrade: it detects the install channel that is actually running cs and picks the right one (many users don't have uv at all) |
| Enable fast mode (daemon) | cs --setup --fast |
| Disable fast mode | cs daemon stop then re-run cs --setup |
| Toggle session cost display | cs config set show_cost true|false |
| Toggle prompt-cache countdown | cs config set show_cache_age true|false |
| Toggle project + branch 2nd line | cs config set show_project_branch true|false (default true) |
| Toggle AgentParty/Codex bridge line | cs config set show_party true|false (default true) |
| Hide weekly bar | cs config set show_weekly false |
| Set warning threshold | cs config set warning_threshold <0-100> |
| Set critical threshold | cs config set critical_threshold <0-100> |
| Auto-collapse to hairline below width | cs config set auto_compact_width <px> |
| Force / disable no-quota (API) mode | cs config set api_mode <auto|on|off> |
No-quota mode (third-party relay / Bedrock / Vertex)
When Claude Code points at a third-party relay (ANTHROPIC_BASE_URL ≠
api.anthropic.com) or a cloud backend (CLAUDE_CODE_USE_BEDROCK /
CLAUDE_CODE_USE_VERTEX), 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 CS_API_MODE=on). Force the official layout back with
api_mode off. CS_API_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"
cs config set color_warn "#e8b260"
cs config set color_hot "#e87474"
cs config set color_ok ""
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:
| Vibe / context | Theme |
|---|
| Muted, professional, dark terminal | graphite (default) |
| Soft, warm, dark | twilight |
| Classic dev / Nord-inspired | nord |
| High contrast, vivid | dracula |
| Warm, cute, light bg | sakura |
| Light terminal | linen |
| Pure grayscale / no color | mono |
| Popular pastel, easy on long viewing | catppuccin-mocha |
| Deeper neon-blue mood | tokyo-night |
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 msgs_pct
- 7d →
theme.s_* chosen from weekly_pct
- model+context →
theme.s_* chosen from ctx_used_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
color_ok / color_warn / 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.
