Your Codex CLI needed a workflow layer

What it does

OMX is an orchestration layer that wraps OpenAI’s Codex CLI without replacing it. It enforces a structured pipeline—$deep-interview for clarification, $ralplan for planning, and $ultragoal for durable execution—while keeping project guidance, logs, and memory in a local .omx/ directory. Essentially, it adds a project manager and a filing cabinet to a very eager intern.

The interesting bit

The clever part is the safety plumbing around reckless speed. OMX integrates with git worktrees to isolate sessions, particularly when running with --madmax (which bypasses Codex’s approval sandbox), and uses tmux to maintain persistent HUD panes so long-running agent teams survive terminal closures.

Key highlights

• Canonical workflow commands ($deep-interview, $ralplan, $ultragoal) force the AI to clarify, plan, then execute
• Durable state management under .omx/ for plans, memory, and mode tracking
• tmux-based persistent runtime with HUD panes for concurrent agent teams
• Git worktree integration provides checkout isolation for high-risk or concurrent sessions
• Ships as both a global CLI and an official Codex plugin, though the plugin relies on the installed CLI rather than replacing it

Caveats

• Native Windows and the Codex App are explicitly unsupported second-class citizens; the project is “primarily designed and actively tuned” for macOS and Linux with Codex CLI

Verdict

Reach for OMX if you want Codex to stop freelancing and follow a rigorous clarify-plan-execute protocol. If you are happy with plain Codex or develop primarily on Windows, you probably do not need this layer.