with one click
hud
Show or configure the RCS HUD (two-layer statusline)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Show or configure the RCS HUD (two-layer statusline)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compatibility visual-delivery runtime for Roblox creator UI, HUD, and plugin work; the canonical completion owner is now Forge.
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.
Persistent Roblox Studio execution loop that carries an approved creator plan to verified completion
Run an anti-slop cleanup/refactor/deslop workflow
Ask Claude via local CLI and capture a reusable artifact
Ask Gemini via local CLI and capture a reusable artifact
| name | hud |
| description | Show or configure the RCS HUD (two-layer statusline) |
| role | display |
| scope | .rcs/** |
| surface-class | operator |
| domain | creator-runtime |
| audience | operator |
| artifact-type | skill |
The RCS HUD uses a two-layer architecture:
Layer 1 - Codex built-in statusLine: Real-time TUI footer showing model, git branch, and context usage. Configured via [tui] status_line in ~/.codex/config.toml. Zero code required.
Layer 2 - rcs hud CLI command: Shows RCS-specific workflow state (forge, ultrawork, autopilot, team, pipeline, ecomode, turns). Reads .rcs/state/ files.
| Command | Description |
|---|---|
rcs hud | Show current HUD (modes, turns, activity) |
rcs hud --watch | Live-updating display (polls every 1s) |
rcs hud --json | Raw state output for scripting |
rcs hud --preset=minimal | Minimal display |
rcs hud --preset=focused | Default display |
rcs hud --preset=full | All elements |
[RCS] forge:3/10 | turns:42
[RCS] forge:3/10 | ultrawork | team:3 workers | turns:42 | last:5s ago
[RCS] forge:3/10 | ultrawork | autopilot:execution | team:3 workers | pipeline:exec | turns:42 | last:5s ago | total-turns:156
rcs setup automatically configures both layers:
[tui] status_line to ~/.codex/config.toml (Layer 1).rcs/hud-config.json with default preset (Layer 2)focused; if HUD/statusline changes do not appear, restart Codex CLI once.Configured in ~/.codex/config.toml:
[tui]
status_line = ["model-with-reasoning", "git-branch", "context-remaining"]
Available built-in items (Codex CLI v0.101.0+):
model-name, model-with-reasoning, current-dir, project-root, git-branch, context-remaining, context-used, five-hour-limit, weekly-limit, codex-version, context-window-size, used-tokens, total-input-tokens, total-output-tokens, session-id
The rcs hud command reads these state files:
.rcs/state/forge-state.json - Forge loop iteration.rcs/state/ultrawork-state.json - Ultrawork mode.rcs/state/autopilot-state.json - Autopilot phase.rcs/state/team-state.json - Team workers.rcs/state/pipeline-state.json - Pipeline stage.rcs/state/ecomode-state.json - Ecomode active.rcs/state/hud-state.json - Last activity (from notify hook).rcs/metrics.json - Turn countsHUD config stored at .rcs/hud-config.json:
{
"preset": "focused"
}
If the TUI statusline is not showing:
rcs setup to configure [tui] sectionIf rcs hud shows "No active modes":