---
name: red-statusline
working-mode: interactive
description: Install or inspect the RedSkills statusline for the active host. RedSkills renders one statusline from the `redskilled` daemon; Claude Code wires it through `.claude/settings.json` as a command-backed statusLine, while Codex configures the built-in `tui.status_line` footer and the dev plugin's SessionStart self-heal hook. Preserves existing config unless replacement is explicitly requested.
disable-model-invocation: true
---
# Statusline
**Wire the RedSkills statusline surface for the current host — stop as soon as a gate condition is met.** Keep the host branch hot here; read [HOST-NOTES.md](HOST-NOTES.md) only for the exact adapter recipe, shared line shape, or rationale needed by the selected host.
## 1. Identify The Host
**Pick one branch.** Use Claude Code when `.claude/` or Claude plugin state is the active surface, Codex when the active client is Codex CLI, and OpenCode only when the user asks about the OpenCode runner lane.
**Respect explicit intent.** Install only when the user asks to install, fix, replace, or configure. Otherwise inspect and report the current state.
## 2. Claude Code
1. Inspect `.red/config.yaml`, `.claude/settings.json`, and whether `jq` is available.
2. **Opt-out gate** — if `.red/config.yaml` has top-level `statusline: false` or nested `afk.statusline: false`, stop and tell the user it is disabled.
3. **Existing-config gate** — if `.claude/settings.json` already has `statusLine`, preserve it unless the user explicitly asked to replace it. Replacement touches only `statusLine`; keep every other key.
4. **Apply the adapter recipe** — read [HOST-NOTES.md](HOST-NOTES.md#claude-code-adapter-recipe), then write or merge the cached-bundle-first `statusLine` block exactly as documented there.
5. **Verify the write, and say what the probe did not prove** — confirm `.claude/settings.json` is valid JSON, contains `.statusLine.command`, and renders by piping minimal session JSON into the same command from the recipe. A passing probe **proves the command, not the host wiring**; never report it as proof the line will appear.
6. **Report `written, restart needed` whenever you wrote** — Claude Code loads `.claude/settings.json` at **session start**, so the key just written is on disk and absent from the running process. Name the cure: **start a new session** (`/reload-plugins` reloads plugins, not project settings). A blank line in THIS session after a passing probe means **restart, not misconfiguration** (#3075). Say nothing about restarting when a gate above left an existing `statusLine` alone — that run changed no setting.
## 3. Codex
1. Inspect the active `~/.codex/config.toml` footer preference with the rs_dev `codex_statusline` read tool.
2. **Preserve host preference** — if `tui.status_line` is already custom, leave it alone unless the user explicitly asks to fix or replace it.
3. **Apply the adapter recipe only on request** — read [HOST-NOTES.md](HOST-NOTES.md#codex-adapter-recipe), then run the explicit fixer or write the recommended global footer. Treat this as host-global config, not repo state.
4. **Report AFK visibility honestly** — Codex gets native footer widgets plus `/afk monitor`; it cannot inject the shared command-backed producer into the footer yet.
## 4. OpenCode
**Install nothing.** OpenCode is a runner lane, not an interactive host UI with a footer adapter. Point the user to `/afk monitor`, `/afk dashboard`, and Actions output. The full note is in [HOST-NOTES.md](HOST-NOTES.md#opencode-adapter).
## 5. Report The Worker Modes
**Keep one host renderer.** the daemon statusline renderer renders the local bedrock, performs one bounded local socket read, and appends the daemon's finished Worker tail. The dev CLI that used to do this was deleted in #4031 — ADR 0147 §1 leaves `redskilled` as the execution chain's only shipped binary. Configure only that dev command in Claude Code; running a second daemon CLI beneath it duplicates the daemon document (#3559). Use `npx -y -p @reddb-io/red-skills@ red-skills-redskilled statusline` only for direct inspection: `global` names every project's owner, and `--verbose` adds the last line each Worker published.
**State the mode and the declared defaults, do not guess them.** Read `plugins.dev.statusline.*` from `.red/config.yaml` and report what it declares; the keys are in [HOST-NOTES.md](HOST-NOTES.md#worker-statusline-modes-and-config).
## 6. Finish
Tell the user which host branch you used, what changed or why nothing changed, and how to observe live AFK state.
## Reference Map
- **Shared architecture and line shapes:** [HOST-NOTES.md](HOST-NOTES.md#shared-architecture-and-line-shapes).
- **Claude Code command-backed adapter:** [HOST-NOTES.md](HOST-NOTES.md#claude-code-adapter-recipe).
- **Codex native footer adapter:** [HOST-NOTES.md](HOST-NOTES.md#codex-adapter-recipe).
- **OpenCode no-install note:** [HOST-NOTES.md](HOST-NOTES.md#opencode-adapter).
- **Worker modes and the config block:** [HOST-NOTES.md](HOST-NOTES.md#worker-statusline-modes-and-config).
## Invocation Notes
- Invoke as `/red-statusline` (Claude Code) or `$red-statusline` (Codex). Wire the host you are running under; do not imply the statusline feature belongs to only one client.
- `/red-setup` may offer the Claude Code command-backed adapter during project bootstrap. Under Codex, use this skill to inspect or configure the native footer path.
## MCP vs. Command-Backed Render Path
The statusline has two client architectures — read [HOST-NOTES.md](HOST-NOTES.md#two-client-architecture) for the boundary rule before touching either path. In brief:
- **Command-backed host (`statusLine`)** — the daemon statusline renderer composes stdin/local-git bedrock with one daemon-fed tail over a bounded local socket read (ADR 0141). Keep it cached-bundle-first and invoke it once.
- **Agents and UIs** — consume structured project data through the `dev:afk` MCP tool `statusline_aggregate`, while daemon-backed host surfaces expose structured host state. They do not carry Claude's stdin-only model, context, or subscription-window facts.
When diagnosing a blank statusline, rule out the stale session first — a `statusLine` written during the running session reaches the host only at the next start — then probe the `statusLine` command directly (step 5 of the Claude Code recipe in HOST-NOTES.md). The MCP path is NOT in scope either way.