Agent skill
hud
Show or configure the OMX HUD (two-layer statusline)
Install this agent skill to your Project
npx add-skill https://github.com/Yeachan-Heo/oh-my-codex/tree/main/skills/hud
SKILL.md
HUD Skill
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_linein~/.codex/config.toml. Zero code required. -
Layer 2 -
omx hudCLI command: Shows OMX-specific orchestration state (ralph, ultrawork, autopilot, team, pipeline, ecomode, turns). Reads.omx/state/files.
Quick Commands
| 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 |
Presets
minimal
[OMX] ralph:3/10 | turns:42
focused (default)
[OMX] ralph:3/10 | ultrawork | team:3 workers | turns:42 | last:5s ago
full
[OMX] ralph:3/10 | ultrawork | autopilot:execution | team:3 workers | pipeline:exec | turns:42 | last:5s ago | total-turns:156
Setup
omx setup automatically configures both layers:
- Adds
[tui] status_lineto~/.codex/config.toml(Layer 1) - Writes
.omx/hud-config.jsonwith default preset (Layer 2) - Default preset is
focused; if HUD/statusline changes do not appear, restart Codex CLI once.
Layer 1: Codex Built-in StatusLine
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
Layer 2: OMX Orchestration HUD
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 counts
Configuration
HUD config stored at .omx/hud-config.json:
{
"preset": "focused"
}
Color Coding
- Green: Normal/healthy
- Yellow: Warning (ralph >70% of max)
- Red: Critical (ralph >90% of max)
Troubleshooting
If the TUI statusline is not showing:
- Ensure Codex CLI v0.101.0+ is installed
- Run
omx setupto configure[tui]section - Restart Codex CLI
If omx hud shows "No active modes":
- This is expected when no workflows are running
- Start a workflow (ralph, autopilot, etc.) and check again
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
configure-notifications
Configure OMX notifications - unified entry point for all platforms
ultraqa
QA cycling workflow - test, verify, fix, repeat until goal met
build-fix
Fix build and TypeScript errors with minimal changes
ask-claude
Ask Claude via local CLI and capture a reusable artifact
tdd
Test-Driven Development enforcement skill - write tests first, always
analyze
Run deep investigation of architecture, bugs, performance issues, or dependencies and return structured findings with file:line evidence. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs root cause analysis before making changes. Routes to architect agent or Codex MCP for thorough cross-file reasoning.
Didn't find tool you were looking for?