// the find
Yeachan-Heo/oh-my-codex
OmX - Oh My codeX: Your codex is not alone. Add hooks, agent teams, HUDs, and so much more.
oh-my-codex (OMX) is a workflow layer that wraps OpenAI Codex CLI with structured planning/execution phases, team coordination via tmux worktrees, persistent state in `.omx/`, and a catalog of reusable skills and role keywords. It is for teams already using Codex CLI who want a repeatable agentic workflow without wiring it up themselves. If you are not already committed to Codex CLI as your AI coding engine, this is not the entry point.
The worktree isolation model is well thought out — each concurrent session gets its own git worktree, which is the right way to avoid multiple agents stomping on each other's branch state. The Rust crates for the runtime core (authority, dispatch, mailbox, replay) suggest the team actually modeled the state machine rather than bolting it on as an afterthought. The `$deep-interview` → `$ralplan` → `$ultragoal` pipeline gives teams a concrete vocabulary for the planning/execution boundary, which is genuinely missing from vanilla Codex. Release cadence is impressive: 0.20.x in active shipping with QA docs for every minor version.
The conceptual surface area is enormous for what is essentially a prompt orchestration layer — HUDs, missions, sparkshell, wiki, MCP bridges, OpenClaw, hermes-bridge, herdr-bridge, a custom tmux mux, and a GEO visibility benchmark. That is not a toolkit, that is a platform accumulating features faster than they can be stabilized. Windows support is explicitly second-class and may break, which is fine to say but signals the core team is already spread thin. Documentation is HTML files served from GitHub Pages with no versioning, meaning a breaking change in 0.18 that the docs haven't caught up to will silently bite new users. And the entire thing collapses if OpenAI changes the Codex CLI API or hook surface — there is no abstraction between OMX and Codex internals.