with one click
hud
[OMX] Show or configure the OMX 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
[OMX] Show or configure the OMX 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
| name | hud |
| description | [OMX] Show or configure the OMX HUD (two-layer statusline) |
| role | display |
| scope | .omx/** |
The OMX 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 - omx hud CLI command: Shows OMX-specific orchestration state (ralph, ultrawork, autopilot, team, pipeline, ecomode, turns). Reads .omx/state/ files.
| Command | Description |
|---|---|
omx hud | Show current HUD (modes, turns, activity) |
omx hud --watch | Live-updating display (polls every 1s) |
omx hud --json | Raw state output for scripting |
omx hud --preset=minimal | Minimal display |
omx hud --preset=focused | Default display |
omx hud --preset=full | All elements |
[OMX] ralph:3/10 | turns:42
[OMX] ralph:3/10 | ultrawork | team:3 workers | turns:42 | last:5s ago
[OMX] ralph:3/10 | ultrawork | autopilot:execution | team:3 workers | pipeline:exec | turns:42 | last:5s ago | total-turns:156
omx setup automatically configures both layers:
[tui] status_line to ~/.codex/config.toml (Layer 1).omx/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 omx hud command reads these state files:
.omx/state/ralph-state.json - Ralph loop iteration.omx/state/ultrawork-state.json - Ultrawork mode.omx/state/autopilot-state.json - Autopilot phase.omx/state/team-state.json - Team workers.omx/state/pipeline-state.json - Pipeline stage.omx/state/ecomode-state.json - Ecomode active.omx/state/hud-state.json - Last activity (from notify hook).omx/metrics.json - Turn countsHUD config stored at .omx/hud-config.json:
{
"preset": "focused"
}
If the TUI statusline is not showing:
omx setup to configure [tui] sectionIf omx hud shows "No active modes":
[OMX] Run an anti-slop cleanup/refactor/deslop workflow
[OMX] 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.
[OMX] Ask Claude via local CLI and capture a reusable artifact
[OMX] Ask Gemini via local CLI and capture a reusable artifact
[OMX] Full autonomous execution from idea to working code
[OMX] Stateful validator-gated research loop with native-hook persistence