CtrlK
BlogDocsLog inGet started
Tessl Logo

hud

Show or configure the OMX HUD (two-layer statusline)

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/hud/SKILL.md
SKILL.md
Quality
Evals
Security

HUD Skill

The OMX HUD uses a two-layer architecture:

  1. 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.

  2. Layer 2 - omx hud CLI command: Shows OMX-specific orchestration state (ralph, ultrawork, autopilot, team, pipeline, ecomode, turns). Reads .omx/state/ files.

Quick Commands

CommandDescription
omx hudShow current HUD (modes, turns, activity)
omx hud --watchLive-updating display (polls every 1s)
omx hud --jsonRaw state output for scripting
omx hud --preset=minimalMinimal display
omx hud --preset=focusedDefault display
omx hud --preset=fullAll 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_line to ~/.codex/config.toml (Layer 1)
  • Writes .omx/hud-config.json with 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:

  1. Ensure Codex CLI v0.101.0+ is installed
  2. Run omx setup to configure [tui] section
  3. 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
Repository
Yeachan-Heo/oh-my-codex
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.