
oh-my-codex-workflow
Expert in Oh My Codex (OMX) - workflow layer for OpenAI Codex CLI with agents, skills, and team coordination
- Installs
- 272
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/reason-machines/codex-skills --skill oh-my-codex-workflow- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads oh-my-codex-workflow automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Oh My Codex (OMX) Workflow
Skill by ara.so — Codex Skills collection.
What OMX Does
Oh My Codex (OMX) is a workflow layer for OpenAI Codex CLI that enhances the base Codex experience with:
- Canonical workflow:
$deep-interview→$ralplan→$ralphor$team - Agent teams: Coordinated parallel execution with tmux-backed worktrees
- Persistent state: Plans, logs, memory, and mode tracking in
.omx/ - Role keywords: Reusable specialist roles (executor, architect, reviewer, etc.)
- Skills system: Installable workflows like
$deep-interview,$ralplan,$team,$ralph - Project guidance: Scoped
AGENTS.mdfor project-specific context - Runtime hooks: Native Codex lifecycle integration via
.codex/hooks.json
OMX keeps Codex as the execution engine and adds better task routing, workflow orchestration, and runtime support around it.
Installation
Prerequisites
- Node.js 20+
- Codex CLI:
npm install -g @openai/codex - Configured Codex auth (check with
codex login status) tmuxon macOS/Linux for team runtime (optional but recommended)
Install OMX
# Install both Codex CLI and OMX globally
npm install -g @openai/codex oh-my-codex
# Run setup to install prompts, skills, hooks, and scaffolding
omx setup
# Verify installation
omx doctor
# Smoke test actual Codex execution
omx exec --skip-git-repo-check -C . "Reply with exactly OMX-EXEC-OK"
Update OMX
# Check npm, install latest, and refresh setup
omx update
# Or manually:
npm install -g oh-my-codex
omx setup
Core Workflow
The Recommended Path
# 1. Launch OMX with recommended settings
omx --madmax --high
# Inside the Codex session:
# 2. Clarify scope (when boundaries are unclear)
$deep-interview "clarify the authentication change"
# 3. Create and approve implementation plan
$ralplan "approve the auth plan and review tradeoffs"
# 4a. Execute with persistent completion loop
$ralph "carry the approved plan to completion"
# OR 4b. Execute with coordinated parallel team
$team 3:executor "execute the approved plan in parallel"
# 5. Convert to durable goals (for multi-session work)
$ultragoal "turn this launch into durable Codex goals"
Launch Modes
# Default: auto-managed tmux on macOS/Linux interactive terminals
omx --madmax --high
# Direct mode (no OMX tmux/HUD management)
omx --direct --yolo
# Set persistent preference via environment
export OMX_LAUNCH_POLICY=direct # or tmux, detached-tmux, auto
omx --yolo
# CLI flags override environment (last flag wins)
OMX_LAUNCH_POLICY=direct omx --tmux --yolo # Uses tmux
Canonical Skills
$deep-interview
Clarify intent, boundaries, and non-goals when the request is vague.
$deep-interview "clarify requirements for the new API endpoint"
$deep-interview "understand the performance bottleneck before planning fixes"
$ralplan
Turn clarified scope into an approved architecture and implementation plan.
$ralplan "approve the implementation plan and review tradeoffs"
$ralplan "verify the migration strategy is safe"
$ralph
Persistent completion loop - one owner keeps pushing until done.
$ralph "carry the approved plan to completion"
$ralph "implement the auth changes with verification"
$team
Coordinated parallel execution with tmux-backed worktrees.
# Launch team with N agents of role:type
$team 3:executor "execute the approved plan in parallel"
$team 2:architect "design the new service architecture"
# Team management (CLI, not in-session)
omx team status <team-name>
omx team resume <team-name>
omx team shutdown <team-name>
$ultragoal
Convert a launch session into durable Codex goals for multi-session work.
$ultragoal "turn this migration into sequential Codex goals"
Project Structure
OMX creates and manages these directories:
.omx/
├── plans/ # Approved implementation plans from $ralplan
├── logs/ # Execution logs from $ralph and $team
├── memory/ # Persistent agent memory
├── ultragoal/ # Durable multi-goal artifacts
└── teams/ # Team runtime state and worktrees
.codex/
├── config.toml # Codex configuration (OMX seeds defaults)
├── hooks.json # Native Codex hooks (OMX-managed wrappers)
└── prompts/ # OMX-installed role and skill prompts
AGENTS.md # Project-specific agent guidance (optional)
Configuration
Model and Environment Routing
Edit .omx-config.json for model/env routing (only use keys supported by your OMX version):
{
"model": "gpt-5.5",
"provider": "openai",
"baseURL": "https://api.openai.com/v1",
"env": {
"OPENAI_API_KEY": "${OPENAI_API_KEY}"
}
}
See model/env routing reference for details.
Codex Config Seeding
OMX seeds .codex/config.toml with recommended defaults for gpt-5.5:
[gpt-5.5]
model_name = "gpt-5.5"
model_context_window = 250000
model_auto_compact_token_limit = 200000
AGENTS.md Merge
Preserve existing project guidance while adding OMX sections:
# Merge mode: inserts between <!-- OMX:AGENTS:START --> / END -->
omx setup --merge-agents
# Default: skips existing AGENTS.md in non-interactive mode
omx setup
Common Patterns
Standard Workflow
// TypeScript example: typical OMX workflow pattern
async function standardWorkflow() {
// 1. Clarify scope
// Run: $deep-interview "understand the feature requirements"
// 2. Create plan
// Run: $ralplan "approve the implementation approach"
// 3. Execute
// Option A - single persistent owner:
// Run: $ralph "implement with verification"
// Option B - parallel team:
// Run: $team 3:executor "execute in parallel"
// 4. Convert to goals for multi-session work
// Run: $ultragoal "create durable goals for remaining work"
}
Team Execution
# Launch team from CLI
omx team 3:executor "migrate database schema with verification"
# Check team status
omx team status migration-team
# Resume paused team
omx team resume migration-team
# Clean shutdown
omx team shutdown migration-team
Direct Codex Exec
// Use omx exec for one-off Codex calls outside a session
import { execSync } from 'child_process';
const result = execSync(
'omx exec --skip-git-repo-check -C . "List all TypeScript files in src/"',
{ encoding: 'utf-8' }
);
console.log(result);
Custom Skill Creation
# Skills are stored in .codex/prompts/skills/
# Create a new skill file:
# .codex/prompts/skills/my-custom-skill.md
# Content structure:
# ---
# name: my-custom-skill
# triggers:
# - do custom thing
# ---
# # Skill instructions
# When invoked, this skill should...
CLI Commands
Setup and Verification
omx setup # Install prompts, skills, hooks, scaffolding
omx setup --merge-agents # Preserve existing AGENTS.md while adding OMX sections
omx setup --force # Force overwrite existing files
omx doctor # Verify installation integrity
omx update # Check npm, install latest, refresh setup
omx uninstall # Remove OMX-managed hooks (keep user hooks)
Launch
omx --madmax --high # Recommended default
omx --yolo # Quick launch, less safety
omx --direct --yolo # No OMX tmux management
omx --tmux # Force tmux mode
Execution
omx exec [options] "prompt" # Direct Codex execution
omx exec --skip-git-repo-check -C . "prompt" # Skip git repo requirement
Team Runtime
omx team N:role "task" # Launch N agents of role:type
omx team status <name> # Check team status
omx team resume <name> # Resume paused team
omx team shutdown <name> # Clean shutdown
omx team list # List active teams
Monitoring
omx hud --watch # Launch monitoring HUD (operator surface)
Environment Variables
# Launch policy preference
export OMX_LAUNCH_POLICY=direct # direct, tmux, detached-tmux, auto
# Codex home (affects plugin cache location)
export CODEX_HOME=~/.codex
# API keys (referenced in .omx-config.json)
export OPENAI_API_KEY=your_key_here
export ANTHROPIC_API_KEY=your_key_here
Troubleshooting
Installation Issues
# Verify setup
omx doctor
# Check Codex auth
codex login status
# Smoke test actual execution
omx exec --skip-git-repo-check -C . "Reply with exactly OMX-EXEC-OK"
# Refresh setup after version bump
omx setup
# Or use update to check npm first
omx update
Team Runtime Issues
# Verify tmux is installed
which tmux
# Check team status
omx team status <team-name>
# Review team logs
cat .omx/teams/<team-name>/logs/*
# Clean shutdown if stuck
omx team shutdown <team-name>
Hook Issues
# Verify hooks are registered
cat .codex/hooks.json
# Refresh OMX-managed hooks (preserves user hooks)
omx setup
# Check hook execution logs
cat .omx/logs/hooks/*
Model/Provider Issues
# Verify .omx-config.json routing
cat .omx-config.json
# Check Codex config
cat .codex/config.toml
# Test with direct exec
omx exec --skip-git-repo-check -C . "test prompt"
# Verify env vars are set
echo $OPENAI_API_KEY
Common Errors
Error: Codex not found
npm install -g @openai/codex
Error: Auth failed
codex login
codex login status
Error: tmux not found (team runtime)
# macOS
brew install tmux
# Linux
sudo apt-get install tmux # or yum, dnf, etc.
Error: Setup refresh skips AGENTS.md
# Use merge mode to preserve existing content
omx setup --merge-agents
# Or force overwrite
omx setup --force
Advanced Usage
Plugin Mode vs Setup Mode
OMX ships both as npm package (setup mode) and Codex plugin (plugin mode):
Setup mode (recommended):
npm install -g oh-my-codex
omx setup
- Installs native agents and prompts
- Manages
.codex/hooks.jsonwrappers - Full runtime integration
Plugin mode:
- Install via Codex plugin marketplace
- Bundles skills in plugin manifest
- Optional MCP compatibility (disabled by default)
- Removes legacy OMX-managed prompts to avoid shadowing
- Native/runtime hooks still setup-owned
- Not a replacement for full OMX setup
Custom Agent Roles
Create custom roles in .codex/prompts/agents/:
---
name: security-reviewer
role: Security Review Specialist
---
# Security Reviewer Agent
You are a security review specialist. When assigned a task:
1. Review code for security vulnerabilities
2. Check for OWASP top 10 issues
3. Validate input sanitization
4. Review authentication/authorization
5. Document findings with severity levels
Integration with Other Tools
# Use OMX in CI/CD
omx exec --skip-git-repo-check -C . "Run security audit on changed files"
# Integrate with git hooks
# .git/hooks/pre-commit
#!/bin/bash
omx exec -C . "Review staged changes for issues"
Best Practices
- Start with clarification: Use
$deep-interviewwhen scope is unclear - Approve plans explicitly: Always run
$ralplanbefore execution - Choose the right execution mode:
$ralphfor persistent loops,$teamfor parallel work - Use durable goals: Run
$ultragoalfor multi-session work - Review
.omx/artifacts: Check plans and logs for context - Keep AGENTS.md updated: Maintain project-specific guidance
- Verify with
omx doctor: Run after setup or when issues arise - Test with
omx exec: Smoke test auth and execution before workflows
Resources
- Website: https://oh-my-codex.dev
- GitHub: https://github.com/Yeachan-Heo/oh-my-codex
- Discord: https://discord.gg/PUwSMR9XNk
- Documentation:
FAQ
What does the oh-my-codex-workflow skill do?
Expert in Oh My Codex (OMX) - workflow layer for OpenAI Codex CLI with agents, skills, and team coordination
How do I install oh-my-codex-workflow?
Run npx skills add https://github.com/reason-machines/codex-skills --skill oh-my-codex-workflow in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/oh-my-codex-workflow/ (personal) or .claude/skills/oh-my-codex-workflow/ (project).
Which AI agents can use oh-my-codex-workflow?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is oh-my-codex-workflow safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains oh-my-codex-workflow?
It is published by reason-machines in reason-machines/codex-skills. It has 272 recorded installs.
More from reason-machines/codex-skills
academic-research-skills-codex
reason-machines/codex-skills
Open the skill to read its SKILL.md instructions.
codexplusplus-launcher
reason-machines/codex-skills
Enhanced launcher for Codex App that unlocks plugins, enables session deletion, exports conversations, and syncs provider sessions via CDP injection
awesome-codex-subagents
reason-machines/codex-skills
A curated collection of 136+ specialized Codex subagents for development tasks across 10 categories
codex-plugin-claude-code
reason-machines/codex-skills
Open the skill to read its SKILL.md instructions.
awesome-codex-skills-curator
reason-machines/codex-skills
Open the skill to read its SKILL.md instructions.
codex-plusplus-tweak-system
reason-machines/codex-skills
Open the skill to read its SKILL.md instructions.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。