explaingit

yeachan-heo/oh-my-codex

📈 Trending27,711TypeScriptAudience · developerComplexity · 3/5ActiveSetup · moderate

TLDR

A workflow layer for OpenAI's Codex CLI that breaks down complex coding tasks into structured steps: clarify intent, review plans, execute with single or parallel agents, and persist context between sessions.

Mindmap

mindmap
  root((repo))
    What it does
      Workflow structure
      Context persistence
      Multi-agent execution
      Terminal HUD display
    Key skills
      Deep interview
      Plan review
      Single-threaded loop
      Parallel team agents
    Use cases
      Architectural changes
      Multi-step features
      Complex refactoring
    Tech stack
      TypeScript
      Node.js
      OpenAI Codex
    Audience
      Codex CLI users
      Developers

Things people build with this

USE CASE 1

Break down architectural changes into structured steps with AI review and approval before execution.

USE CASE 2

Execute multi-step feature development with persistent memory across multiple Codex sessions.

USE CASE 3

Coordinate parallel AI agents to work on different parts of a complex task simultaneously.

USE CASE 4

Maintain project context and decision logs automatically in a .omx folder for reproducible workflows.

Tech stack

TypeScriptNode.jsOpenAI Codex

Getting it running

Difficulty · moderate Time to first run · 30min

Requires OpenAI API key and Codex CLI installation; Node.js/TypeScript build step needed.

License could not be detected automatically. Check the repository's LICENSE file before use.

In plain English

OMX, short for oh-my-codex, is a workflow layer that sits on top of the OpenAI Codex CLI, a command-line coding assistant from OpenAI. The README is clear that OMX does not replace Codex: Codex still does the actual agent work, while OMX wraps it with stronger defaults, reusable workflows, and persistent state so longer tasks are easier to manage. In practice, after installing both the Codex CLI and OMX through npm, you launch a session with a single command and drive your work using keyword shortcuts inside Codex. The README highlights a handful: $deep-interview for clarifying a request, $ralplan for proposing and approving a plan, $ralph for carrying an approved plan through to completion, $team for splitting work across parallel executors, and $ultragoal for stitching multiple Codex goals into a durable launch. Plans, logs, memory, and runtime state are stored in a project-local .omx/ directory so progress survives across sessions. A doctor command checks the install is healthy, and an exec command proves Codex can actually authenticate and complete a model call. You would reach for OMX if you already use Codex regularly and want more structure around it, repeatable roles, clearer hand-offs between planning and execution, and a way to coordinate parallel work or persistent loops. If you prefer plain Codex with no extra layer, the README says you probably do not need OMX. The project is written in TypeScript, requires Node.js 20 or newer, and the recommended environment is macOS or Linux with tmux available; native Windows is supported but explicitly less polished. The full README is longer than what was provided.

Copy-paste prompts

Prompt 1
Set up Oh My Codex in my project and configure it to use deep-interview mode for planning a major refactor.
Prompt 2
Show me how to use the $team skill to run parallel agents on different components of my codebase.
Prompt 3
How do I persist context between Codex sessions using OMX's .omx folder and $ultragoal for long-running work?
Prompt 4
Walk me through the $ralplan workflow: how do I review and approve an AI-generated plan before execution?
Prompt 5
Configure OMX to display a terminal HUD that shows the current step, logs, and memory state during execution.
Open on GitHub → Explain another repo

Generated 2026-05-21 · Model: sonnet-4-6 · Verify against the repo before relying on details.