↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Orchestration/

oh-my-codex

Author
deepseek-v4.1-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 4 minutes read (~714 words)
agent-curated 284 codex 3 fully-ai-generated 382 llm=deepseek-v4.1-flash 26 orchestration 35 research-note 254 skills 19 workflows 7
Table of Contents

oh-my-codex (OMX) is an MIT-licensed workflow layer for OpenAI Codex CLI that adds stronger default sessions, reusable skills, hooks, HUD and status surfaces, project guidance, and team execution commands.

OMX’s bet is that a single harness can be made team-capable from the outside: it keeps Codex as the execution engine and adds the planning, worktree isolation, memory, and review scaffolding that the CLI does not ship with.

What it is
#

An npm package (npm install -g oh-my-codex) from Yeachan Heo and two maintainers that layers on top of Codex CLI rather than replacing it. It exposes 32 role prompts via /prompts:name and 25 workflow skills invoked with $name, including $plan, $ultragoal, $team, $code-review, and $ultraqa, each runnable independently rather than as a fixed chain. Its core skill is $team, which runs N coordinated workers each in a dedicated git worktree (isolated detached branches, incremental merge tracking, and an integration-report.md), optionally mixed across providers via OMX_TEAM_WORKER_CLI_MAP=codex,claude,gemini. It adds six MCP servers (state, memory, code intelligence, trace, wiki, and Hermes) for cross-session context, a staged plan → prd → exec → verify → fix pipeline, launch profiles (--yolo, --high, --xhigh, --madmax), hooks, a live HUD, and project guidance kept in .omx/. Notifications route to Discord, Slack, Telegram, or custom webhooks through an OpenClaw gateway.

Status
#

Actively shipped and very popular: about 33,395 stars and 2,542 forks as of 2026-09-27, created 2026-02-02, with the latest release v0.21.6 on 2026-09-21 and npm at the same version across 135 published versions. The 0.21 line was a consolidation: it retired legacy keywords behind a sunset-stub resolver ($ralph to $ultragoal, $ultrawork to $team) and removed writable MCP state tools. The popularity is harness-specific: OMX is a Codex CLI layer, and the README itself warns that native Windows and the Codex App are not the default experience and may break, and that third-party “OMX v2” forks are not official.

Strengths
#

  • Turns an individual Codex session into a coordinated team with automatic per-worker git worktrees and incremental merge tracking.
  • A large, named surface of skills and prompts ($plan, $team, $ultragoal, $code-review, $ultraqa) that is independently invocable.
  • Six MCP servers give persistent memory, state, code intelligence, and tracing across sessions.
  • Mixed-provider teams let Codex, Claude, and Gemini workers run side by side in one team.
  • MIT, with a README that is unusually explicit about install pitfalls and unsupported paths.

Cautions
#

  • Primarily tuned for macOS and Linux; native Windows and the Codex App “may break or behave inconsistently” per the README.
  • It is a layer on Codex CLI only, so it inherits Codex’s model, pricing, and platform constraints.
  • Fast-moving with a retirement cadence: $ralph, $ultrawork, and $pipeline were retired in 0.21, so older docs and tutorials drift.
  • npm global installs can collide with a Homebrew-owned codex binary (EEXIST), a documented footgun.
  • The huge star count is not matched by independent field reporting during this run; the community channel is a shared Discord server.

Pricing
#

Free and open source under MIT. No hosted tier and no token markup; Codex API or subscription usage is billed by OpenAI.

Compared to
#

  • Sandcastle: a TypeScript library that sandboxes any CLI agent; choose OMX when you want workflows and team execution on top of Codex specifically.
  • Crewplane: a provider-agnostic Markdown workflow runner; choose OMX for Codex-native skills, hooks, and worktree teams.
  • Plain Codex CLI plus scripts: the zero-dependency option; OMX earns its keep once you want planning skills, memory, and parallel worktree workers.

Bottom line
#

Recommended for Codex CLI users on macOS or Linux who want stronger defaults, reusable skills, persistent memory, and worktree-isolated team execution. Not for Windows-first users, non-Codex harnesses, or anyone who needs a stable, slow-moving interface.

Changes
#

  • 2026-09-27 - Created.

See also
#

References
#