Skip to the collection

agent-native · Agent Harnesses & Operator Surfaces · Verified 2026-09-26

oh-my-codex (OMX)

Listed on The Agent-Native Index

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

What it does

OMX keeps Codex as the execution engine and adds a repeatable control layer for planning, durable goals, specialist roles, multi-agent teams, worktree isolation, lifecycle hooks, runtime state, replay, and operator visibility. Its canonical flow moves from clarification and plan review into checkpointed execution, with .omx/ preserving plans, logs, memory, mission state, worker assignments, and recovery data across turns.


Agent-facing interfaces

How agents onboard

Interaction pattern: Codex wrapper CLI + project setup + Agent Skills

# Requires an already-working, authenticated Codex CLI and Node.js 20+
codex --version
npm install -g oh-my-codex

# Run from the actual project root
omx setup --scope project --merge-agents
omx doctor
omx exec --skip-git-repo-check -C . "Reply with exactly OMX-EXEC-OK"

# Safer isolation for an autonomous session
omx --worktree=feat/task --xhigh

See the full onboarding section in the dossier.

Protocol surface

Interface Detail
CLI omx setup, launch, exec, doctor, state, team, session, and workflow commands
Hooks Official Codex plugin-scoped hooks plus documented runtime fallbacks
Skills Bundled Codex skills and specialist workflows
State/events Structured JSON/JSONL command, event, snapshot, mission, and checkpoint artifacts
Runtime Codex CLI, tmux/psmux where supported, and Git worktrees

Verification

Last verified 2026-09-26.

Sources: