oh-my-codex CLI
oh-my-codex (OMX)
A layer on top of Codex CLI: one flow from clarifying a task to verification, agent teams, hooks, a HUD and state in .omx/
- 33,650 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Runs agents that execute commands and change code
- The --madmax mode disables approvals and the sandbox
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/oh-my-codex-omxDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Runs agents that execute commands and change code
- The --madmax mode disables approvals and the sandbox
This is third-party code. Review the repository files before installing.
What it does
OMX keeps Codex as the executor and wraps a workflow around it. A task is clarified with $deep-interview, the plan is agreed in $ralplan, and $ultragoal turns it into a chain of durable goals with artifacts. $team runs parallel work in tmux, $ralph is a single-owner completion loop, and $best-practice-research and $autoresearch handle research. Plans, logs, memory and modes live in .omx/, project guidance in AGENTS.md.
Who it is for. For developers already using Codex CLI who want a stricter process for long tasks.
Good fit when
- A large task that needs clarification, planning and verification
- You want several Codex agents working in parallel
- You want plans and session history kept in the repository
Not a fit when
- You want plain Codex without an extra workflow
- You work on native Windows or in Codex App: the README warns support is weaker
Example request
$deep-interview "clarify the auth refactor", then $ralplan and $ultragoalLimitations
Requires Node.js 20+, an installed and authenticated Codex CLI, and tmux for team mode. macOS and Linux are the main platforms. The --madmax flag disables Codex approvals and sandbox. Codex runs on the OpenAI API.
How to disable. Remove the package with npm uninstall -g oh-my-codex, then delete the generated OMX sections from AGENTS.md and the project's .omx/ folder.
FAQ
Does the Codex plugin replace the CLI?
No. The README states the plugin in plugins/oh-my-codex does not replace the global omx CLI: plugin hooks call the installed omx.
How do I check the setup?
omx doctor checks files and hooks, and a short omx exec call confirms Codex is authenticated and responding.
Discussion
No questions or reviews yet.
Related
CLI toolsOpenAI's coding agent that runs locally in your terminal, with IDE and desktop versions
Orchestrator plugin for OpenCode and Codex CLI: multiple agents, hooks, built-in MCPs, ultrawork mode and hash-anchored edits
The /codex-workflows skill: Claude Code writes a script, dozens of Codex agents run it, and the run shows on a map
Codex MCP Server: Codex inside Claude Code
Codex MCP Server
An MCP server that hands tasks to the Codex CLI from inside Claude Code: code questions, change review, web search and resumable sessions
A local-first control plane for long-running agents: goals, decisions and status persist across Codex and Claude Code sessions
Codex Astra + Luna Orchestrator
Codex Astra Orchestrator + Luna Subagents
Codex profiles where GPT-6 Astra orchestrates and reviews while GPT-5.6 Luna runs the explorer, worker, tester and researcher subagents
README in short
The README presents OMX as a workflow layer for Codex CLI and gives a recommended path: install the package, run omx setup in the right scope and launch omx with --worktree. It covers the AGENTS.md merge policy, running parallel sessions via OMX_ROOT and the risks of --madmax. It also describes the Codex plugin, research skills and the install check. MIT licensed.