It is a two-layer statusline. Layer 1 is the Codex built-in statusLine showing model, git branch, and context usage. Layer 2 is the omx hud command showing orchestration state like ralph, ultrawork, autopilot, team, pipeline, ecomode, and turns.

Run omx setup. It adds [tui] status_line to ~/.codex/config.toml and writes .omx/hud-config.json with the default focused preset. If changes do not appear, restart Codex CLI once.

What presets are available?

Three: minimal, focused (default), and full. Use omx hud --preset=minimal, --preset=focused, or --preset=full.

Why does omx hud show "No active modes"?

This is expected when no workflows are running. Start a workflow to see orchestration details.

HUD Skill

SkillDev tools

The hud skill shows or configures the OMX HUD, a two-layer statusline for your terminal. The bottom layer shows the model name, git branch, and remaining context; the top layer shows orchestration details like loops, worker count, and turn numbers read from local state files. It offers minimal, focused, and full presets plus watch and JSON output modes.

Available today. Use it from your connected AI after setup.

No other account needed.

Have the OMX tooling and Codex CLI v0.101.0 or later available.

Then ask your AI: use the HUD Skill skill

What your AI can do with it

Show the current HUD with modes, turns, and activity
Watch the HUD with a live-updating display
Output raw state as JSON for scripting
Switch between minimal, focused, and full presets
Read orchestration state from .omx/state/ files
Configure the built-in statusline in ~/.codex/config.toml

Getting started

Have the OMX tooling and Codex CLI v0.101.0 or later available.
Run omx setup to configure both HUD layers and write .omx/hud-config.json.
If HUD or statusline changes do not appear, restart Codex CLI once.
Run omx hud to see the current status, or omx hud --watch for live updates.

What this skill tells your AI

The instructions your AI receives, as published by yeachan-heo/oh-my-codex in skills/hud/SKILL.md and read by ahel’s review.

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.

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_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:

Ensure Codex CLI v0.101.0+ is installed
Run omx setup to configure [tui] section
Restart Codex CLI

If omx hud shows "No active modes":

This is expected when no workflows are running
Start an explicitly requested supported workflow ($autopilot or $ultragoal) and check again

Signals

GitHub stars: 33k
Forks: 3k
Last commit: Oct 2026

Questions

What is the OMX HUD?: It is a two-layer statusline. Layer 1 is the Codex built-in statusLine showing model, git branch, and context usage. Layer 2 is the omx hud command showing orchestration state like ralph, ultrawork, autopilot, team, pipeline, ecomode, and turns.
How do I set it up?: Run omx setup. It adds [tui] status_line to ~/.codex/config.toml and writes .omx/hud-config.json with the default focused preset. If changes do not appear, restart Codex CLI once.
What presets are available?: Three: minimal, focused (default), and full. Use omx hud --preset=minimal, --preset=focused, or --preset=full.
Why does omx hud show "No active modes"?: This is expected when no workflows are running. Start a workflow to see orchestration details.

Advanced

Item type: skill
Key: hud-2
Source: github.com/yeachan-heo/oh-my-codex

github.com/yeachan-heo/oh-my-codex

More in Dev tools

teach
Skill · mattpocock implement
Skill · mattpocock ponytail
Skill · dietrichgebert caveman
Skill · juliusbrussee grilling
Skill · mattpocock shadcn
Skill · shadcn