Yeachan-Heo/oh-my-codex

OmX - Oh My codeX: Your codex is not alone. Add hooks, agent teams, HUDs, and so much more.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 3 minutes ago
Added to GitGenius on April 25th, 2026
Created on February 2nd, 2026
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 2,534
Total Stargazers: 33,004 (+1)
Total Subscribers: 84 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 3.4 hours
90th percentile: 8.2 hours
Tracked items: 1,201

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 15% of issues opened in the past year have been closed. Three people close 97% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 4
Closed in 7 days: 4
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 4
Closed in 7 days: 4
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (269)
  • enhancement (145)
  • audit (54)
  • kind:bugs-glitches (26)
  • priority:P1 (26)
  • area:team (23)
  • kind:architecture (18)
  • audit:2026-02-22 (16)

Detailed Description

Oh My codeX (OMX) is a workflow layer built on top of OpenAI's Codex CLI that enhances the code generation experience by adding structured workflows, agent teams, heads-up displays, and extended functionality. Written in TypeScript, the project serves as a productivity multiplier for developers already using Codex, transforming it from a basic code execution engine into a comprehensive development assistant with planning, research, and multi-goal coordination capabilities.

The repository is primarily designed for macOS and Linux environments with Codex CLI, though the maintainers acknowledge that native Windows and Codex App support receive less active development and may behave inconsistently. The core value proposition centers on keeping Codex as the execution engine while making it easier to start stronger sessions by default, run consistent workflows from clarification through completion, and maintain project guidance, plans, logs, and state in a dedicated .omx directory structure.

OMX implements a canonical default workflow accessible through commands like $deep-interview, $ralplan, and $ultragoal. The $deep-interview command handles initial clarification, $ralplan synthesizes architecture and planning, and $ultragoal provides durable multi-goal handoffs as the default completion path. Additional specialized workflows include $prometheus-strict for interview-driven plan hardening on high-risk work, $best-practice-research for upstream evidence gathering, $autoresearch for bounded validator-gated research, and $team for coordinated parallel work when specific stories require it.

The repository connects to related projects including oh-my-claudecode and nousresearch/hermes-agent through overlapping contributor networks.

The official npm package is oh-my-codex, installed globally via npm install -g oh-my-codex, with documentation covering getting started, agents, skills, integrations, and OpenClaw integration.

OMX supports flexible installation and setup scopes. Users can install globally for user-level Codex setup or configure project-scoped setups where specific repositories own durable AGENTS.md guidance files. The project includes an official Codex plugin layout at plugins/oh-my-codex with marketplace metadata, though this does not replace the global CLI and scoped setup. The runtime includes diagnostic tools like omx doctor for verifying installation integrity and omx exec for testing authentication and model calls.

The recommended workflow involves launching OMX from git projects with optional flags like --madmax for bypassing approvals and --xhigh for extended reasoning effort. On macOS and Linux with tmux available, OMX launches in detached tmux sessions by default to enable HUD and runtime panes. The --worktree option provides safer concurrent execution by isolating sessions into separate git checkouts, particularly important when using --madmax in trusted repositories.