View and configure status displays for Codex CLI and OMX workflows. Show the model, context usage, active modes, worker counts, and turns, with compact or detailed presets, live updates, and JSON output for scripts.
Show or configure the OMX HUD (two-layer statusline)
Review the instructions the agent will receive before you install.
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":
$autopilot or $ultragoal) and check againNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.
Investigate repository behavior, architecture, or possible causes without changing files. Trace relevant code and supporting material, then rank explanations by evidence and confidence, with concrete file references and clear distinctions between observations, conclusions, and unresolved questions.
Ask Claude or Gemini through a locally installed command-line tool for focused questions, reviews, brainstorming, or second opinions. Save the prompt, original response, summary, and next steps in a reusable Markdown file.
Take an idea or issue through requirements clarification, reviewed planning, implementation, and verification. Supervise all stages in one recoverable OMX workflow, preserving artifacts and progress so work can resume or return to planning when findings require changes.
Run a persistent research workflow with a defined goal and explicit acceptance checks. It saves progress and finishes only when a recorded result passes either a validation script or an architect review of the research output.
Find the replacement for a research command removed in OMX 0.21. This migration notice directs existing autoresearch-goal usage to $autoresearch, the canonical research loop that requires validation before proceeding.