OmX - Oh My codeX: Your codex is not alone. Add hooks, agent teams, HUDs, and so much more.

Start Codex stronger, then let OMX add better prompts, workflows, and runtime help when the work grows.

Website: https://yeachan-heo.github.io/oh-my-codex-website/
Docs: Getting Started · Agents · Skills · Integrations · Demo · OpenClaw guide

OMX is a workflow layer for OpenAI Codex CLI.

It keeps Codex as the execution engine and makes it easier to:

• start a stronger Codex session by default
• run one consistent workflow from clarification to completion
• invoke the canonical skills with $deep-interview, $ralplan, $team, and $ralph
• keep project guidance, plans, logs, and state in .omx/

If you want the default OMX experience, start here:

npm install -g @openai/codex oh-my-codex
omx setup
omx --madmax --high

Then work normally inside Codex:

$deep-interview "clarify the authentication change"
$ralplan "approve the auth plan and review tradeoffs"
$ralph "carry the approved plan to completion"
$team 3:executor "execute the approved plan in parallel"

That is the main path. Start OMX strongly, clarify first when needed, approve the plan, then choose $team for coordinated parallel execution or $ralph for the persistent completion loop.

Use OMX if you already like Codex and want a better day-to-day runtime around it:

• a standard workflow built around $deep-interview, $ralplan, $team, and $ralph
• specialist roles and supporting skills when the task needs them
• project guidance through scoped AGENTS.md
• durable state under .omx/ for plans, logs, memory, and mode tracking

If you want plain Codex with no extra workflow layer, you probably do not need OMX.

• Node.js 20+
• Codex CLI installed: npm install -g @openai/codex
• Codex auth configured
• tmux on macOS/Linux if you later want the durable team runtime
• psmux on native Windows if you later want Windows team mode

Launch OMX the recommended way:

omx --madmax --high

Then try the canonical workflow:

$deep-interview "clarify the authentication change"
$ralplan "approve the safest implementation path"
$ralph "carry the approved plan to completion"
$team 3:executor "execute the approved plan in parallel"

Use $team when the approved plan needs coordinated parallel work, or $ralph when one persistent owner should keep pushing to completion.

OMX does not replace Codex.

It adds a better working layer around it:

• Codex does the actual agent work
• OMX role keywords make useful roles reusable
• OMX skills make common workflows reusable
• .omx/ stores plans, logs, memory, and runtime state

Most users should think of OMX as better task routing + better workflow + better runtime, not as a command surface to operate manually all day.

1. Run omx setup
2. Launch with omx --madmax --high
3. Use $deep-interview "..." when the request or boundaries are still unclear
4. Use $ralplan "..." to approve the plan and review tradeoffs
5. Choose $team for coordinated parallel execution or $ralph for persistent completion loops

1. $deep-interview — clarify scope when the request or boundaries are still vague.
2. $ralplan — turn that clarified scope into an approved architecture and implementation plan.
3. $team or $ralph — use $team for coordinated parallel execution, or $ralph when you want a persistent completion loop with one owner.

These are useful, but they are not the main onboarding path.

Use the team runtime when you specifically need durable tmux/worktree coordination, not as the default way to begin using OMX.

omx team 3:executor "fix the failing tests with verification"
omx team status <team-name>
omx team resume <team-name>
omx team shutdown <team-name>

These are operator/support surfaces:

• omx setup installs prompts, skills, config, and AGENTS scaffolding
• omx doctor verifies the install when something seems wrong
• omx hud --watch is a monitoring/status surface, not the primary user workflow

• omx explore --prompt "..." is for read-only repository lookup
• omx sparkshell <command> is for shell-native inspection and bounded verification

Examples:

omx explore --prompt "find where team state is written"
omx sparkshell git status
omx sparkshell --tmux-pane %12 --tail-lines 400

omx team needs a tmux-compatible backend:

On some Intel Macs, OMX startup — especially with --madmax --high — can spike syspolicyd / trustd CPU usage while macOS Gatekeeper validates many concurrent process launches.

If this happens, try:

• xattr -dr com.apple.quarantine $(which omx)
• adding your terminal app to the Developer Tools allowlist in macOS Security settings
• using lower concurrency (for example, avoid --madmax --high)

• Getting Started
• Demo guide
• Agent catalog
• Skills reference
• Integrations
• OpenClaw / notification gateway guide
• Contributing
• Changelog

• English
• 한국어
• 日本語
• 简体中文
• 繁體中文
• Tiếng Việt
• Español
• Português
• Русский
• Türkçe
• Deutsch
• Français
• Italiano
• Ελληνικά
• Polski

MIT