oh-my-codex (OMX) v2

Codex-native orchestration for builders who want one default path from a vague prompt to a durable multi-worker runtime.

OMX v2 is not the old Codex-to-Claude bridge. It is a full Codex product built around:

• durable .omx/ state
• tmux-aware team execution
• a real agent catalog
• a plugin SDK plus Codex plugin bridge
• a first-party hook pack for Codex hooks
• CLI, MCP, docs, demos, and packaged assets in one repo

What ships

CLI

omx setup
omx doctor
omx hud
omx team
omx explore
omx session
omx autoresearch
omx agents
omx plugins
omx hooks
omx version

Skills

• $ultrawork
• $deep-interview
• $plan
• $research
• $team
• $review
• $tdd
• $doctor
• $hud
• $trace
• $autoresearch
• $architect
• $executor
• $reviewer

MCP families

• omx_task_*
• omx_state_*
• omx_memory_*
• omx_note_*
• omx_explore_*
• omx_team_*
• omx_plugin_*
• omx_hook_*
• omx_agent_*

Durable contract

.omx/
├── hud-config.json
├── logs/
├── memory/
├── plans/
├── research/
├── sessions/
├── state/
└── team/

Product areas

Runtime

• durable task graph, review queue, inbox, and execution ledger
• tmux-first worker runtime on macOS/Linux, degraded mock mode when tmux is missing
• resumable sessions and persistent team state

Agents

• committed machine-readable catalog for architect, planner, researcher, executor, reviewer, operator
• prompt templates under templates/agents
• omx agents list|show|install|validate

Plugins

• local plugin SDK using .codex-plugin/plugin.json
• repo marketplace generation under .agents/plugins/marketplace.json
• first-party bundle at plugins/omx-product
• omx plugins init|pack|validate|install-local|list|enable|disable|doctor

Hooks

• repo-local install to <repo>/.codex/hooks.json
• optional personal install to ~/.codex/hooks.json
• shipped handlers for SessionStart, PreToolUse, PostToolUse, UserPromptSubmit, and Stop
• presets: memory, safety, review, telemetry, workspace-context

Quick start

1. Ask your agent - Paste this to your agent

Install this to .codex - https://github.com/staticpayload/oh-my-codex/

That does the full local onboarding flow:

• installs workspace dependencies when needed
• builds OMX
• links the omx CLI globally with npm link
• runs omx setup
• runs omx doctor

2. Use OMX in any project

Once omx is linked, move into the project you actually want to work on and run:

omx setup

If you want the old manual path, it still works:

npm install
npm run build
cd packages/cli && npm link
node packages/cli/dist/bin.js setup apply

3. Check the environment

omx doctor
omx hud

4. Work through the default path

$ultrawork "ship the feature end to end"

Command map

Setup

omx setup
omx setup --force
omx setup --dry-run
omx setup repair
omx setup uninstall
omx setup migrate-v1
omx setup --no-plugin --no-hooks

Team runtime

omx team init
omx team spawn executor
omx team queue "implement hook doctor"
omx team claim <taskId> executor
omx team complete <taskId> executor "implemented and verified"
omx team review <taskId> reviewer approved "looks good"
omx team inbox
omx team logs executor
omx team shutdown

Plugins

omx plugins validate
omx plugins pack
omx plugins install-local
omx plugins doctor

Hooks

omx hooks install --presets=workspace-context,memory,safety,review
omx hooks status
omx hooks explain safety

Explore

omx explore index
omx explore refs renderHud
omx explore rename-preview oldName newName
omx explore diagnostics
omx explore tmux

Repo layout

packages/
├── cli/
├── core/
└── mcp-server/

crates/
└── omx-explore/

plugins/
└── omx-product/

hooks/
└── handlers/

templates/
└── agents/

Docs

• Install guide
• Runtime guide
• Plugin guide
• Hook guide
• Agent guide
• Architecture
• Migration
• Troubleshooting
• FAQ
• Security notes

Demos

• Plugin authoring demo
• Repo marketplace demo
• Hook pack demo
• Team runtime demo
• Ultrawork demo

Development

npm run build
npm run test
cargo test -p omx-explore

Codex is the first-party executor in v2. There is no Claude bridge in this release.