omx
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chineseomx (oh-my-codex) — Multi-Agent Orchestration for Codex CLI
omx (oh-my-codex) — 面向Codex CLI的多Agent编排工具
When to use this skill
何时使用该技能
- You want a stronger Codex CLI runtime with reusable role prompts and workflow skills
- You need coordinated parallel agents via tmux team workers
- Complex tasks requiring persistent execution () or consensus planning (
$ralph)$ralplan - You need repository exploration () or bounded shell inspection (
omx explore)omx sparkshell - Cross-model consultation with or
$ask-claude$ask-gemini
- 你需要功能更强大的Codex CLI运行时,支持可复用的角色提示词和工作流技能
- 你需要通过tmux团队工作器实现协同并行Agent调度
- 需要持久执行()或共识规划(
$ralph)的复杂任务$ralplan - 你需要仓库探索功能()或受限shell检查功能(
omx explore)omx sparkshell - 通过或
$ask-claude实现跨模型咨询$ask-gemini
1. Quick Start
1. 快速开始
bash
npm install -g @openai/codex oh-my-codex
omx setup
omx --madmax --highInside Codex:
text
/prompts:architect "analyze the authentication flow"
$plan "map the safest implementation path"Mental model: Codex does the agent work. OMX adds better prompts, reusable workflow skills, and a runtime layer around it. Start withand let the agent pull inomx --madmax --high,$team, or other workflows when the task needs them.$ralph
bash
npm install -g @openai/codex oh-my-codex
omx setup
omx --madmax --high在Codex内使用:
text
/prompts:architect "analyze the authentication flow"
$plan "map the safest implementation path"核心逻辑:Codex负责执行Agent任务,OMX为其提供更优质的提示词、可复用的工作流技能以及运行时层。推荐先使用启动,当任务需要时Agent会自动调用omx --madmax --high、$team或其他工作流。$ralph
2. Agent Roles (30+)
2. Agent角色(30+个)
| Tier | Agents |
|---|---|
| Core Development | |
| Quality Assurance | |
| Domain Experts | |
| Product Strategy | |
Invoke via:
/prompts:<agent-name> "task"| 层级 | 包含Agent |
|---|---|
| 核心开发 | |
| 质量保障 | |
| 领域专家 | |
| 产品策略 | |
调用方式:
/prompts:<agent-name> "task"3. Workflow Skills (35+)
3. 工作流技能(35+个)
| Skill | Trigger | Description |
|---|---|---|
| | Full autonomous pipeline — idea to working code |
| | Persistent execution loop until verified complete |
| | Maximum parallelism across parallel agents |
| | N coordinated agents with tmux/worktree isolation |
| | Strategic planning before implementation |
| | Consensus-based iterative planning |
| | Socratic clarification before planning or execution |
| | Codebase-focused deep search |
| | Evidence-driven causal analysis (trace methodology) |
| | Test-first development (red-green-refactor) |
| | Fix build errors, type errors, toolchain failures |
| | Comprehensive multi-dimension code review |
| | Security audit — vulnerabilities, trust boundaries |
| | Maximum parallelism QA pass |
| | UI/UX visual review with verdict |
| | Frontend UI/UX design and review |
| | Clean AI expression patterns from code/docs |
| | Cross-model consultation with Claude |
| | Cross-model consultation with Gemini |
| | Atomic commits, rebasing, history management |
| | Token-efficient execution mode |
| | Clone and adapt web pages or UI patterns |
| | Stop active execution modes |
| 技能 | 触发词 | 描述 |
|---|---|---|
| | 全自动化流水线 — 从想法到可运行代码 |
| | 持久执行循环,直到验证完成 |
| | 跨并行Agent的最大并发调度 |
| | N个协同Agent,支持tmux/worktree隔离 |
| | 开发前的战略规划 |
| | 基于共识的迭代规划 |
| | 规划或执行前的苏格拉底式澄清 |
| | 面向代码库的深度搜索 |
| | 基于证据的因果分析(跟踪方法论) |
| | 测试驱动开发(红-绿-重构) |
| | 修复构建错误、类型错误、工具链故障 |
| | 多维度综合代码评审 |
| | 安全审计 — 漏洞、信任边界检查 |
| | 最大并发QA测试 |
| | 带结论的UI/UX视觉评审 |
| | 前端UI/UX设计与评审 |
| | 清理代码/文档中的AI生成冗余表达 |
| | 调用Claude进行跨模型咨询 |
| | 调用Gemini进行跨模型咨询 |
| | 原子提交、变基、历史管理 |
| | Token高效执行模式 |
| | 克隆与适配网页或UI模式 |
| | 停止正在运行的执行模式 |
4. Team Runtime
4. 团队运行时
bash
undefinedbash
undefinedStart parallel team workers
启动并行团队工作器
omx team 3:executor "fix all TypeScript errors"
omx team 2:security-reviewer,1:architect "audit auth module"
omx team 3:executor "fix all TypeScript errors"
omx team 2:security-reviewer,1:architect "audit auth module"
Team management
团队管理
omx team status <team-name>
omx team resume <team-name>
omx team shutdown <team-name>
Inside Codex:
```text
$team 3:executor "parallelize this refactor"Requirements:
| Platform | Dependency |
|---|---|
| macOS | |
| Ubuntu/Debian | |
| Fedora | |
| Windows (native) | |
| Windows (WSL2) | |
omx team status <team-name>
omx team resume <team-name>
omx team shutdown <team-name>
在Codex内使用:
```text
$team 3:executor "parallelize this refactor"依赖要求:
| 平台 | 依赖 |
|---|---|
| macOS | |
| Ubuntu/Debian | |
| Fedora | |
| Windows (原生) | |
| Windows (WSL2) | |
5. CLI Commands
5. CLI命令
Core launch
核心启动命令
bash
omx # Launch Codex with OMX runtime
omx --madmax --high # Recommended default (bypass + high reasoning)
omx --xhigh # Extra-high reasoning effortbash
omx # 搭载OMX运行时启动Codex
omx --madmax --high # 推荐默认配置(绕过审批 + 高推理能力)
omx --xhigh # 超高推理能力模式Launch flags
启动参数
| Flag | Description |
|---|---|
| Fast execution, minimal verification |
| High reasoning effort |
| Extra-high reasoning effort |
| Bypass approvals/sandbox ( |
| Preview without execution |
| Verbose output |
| 参数 | 描述 |
|---|---|
| 快速执行,最小化验证 |
| 高推理算力模式 |
| 超高推理算力模式 |
| 绕过审批/沙箱(等价于 |
| 仅预览不执行 |
| 输出详细日志 |
Operator commands
操作命令
bash
omx setup # Install prompts, skills, config, AGENTS scaffolding
omx doctor # Verify installation
omx doctor --team # Team/swarm diagnostics
omx status # Show active modes
omx cancel # Cancel execution modes
omx hud --watch # Live HUD status monitor
omx reasoning <mode> # Set: low/medium/high/xhigh
omx help # Show helpbash
omx setup # 安装提示词、技能、配置、Agent脚手架
omx doctor # 验证安装是否正常
omx doctor --team # 团队/集群诊断
omx status # 展示当前激活的模式
omx cancel # 取消执行模式
omx hud --watch # 实时HUD状态监控
omx reasoning <mode> # 设置推理等级:low/medium/high/xhigh
omx help # 展示帮助信息Explore & inspect
探索与检查命令
bash
omx explore --prompt "find where team state is written" # Read-only repo lookup
omx sparkshell git status # Bounded shell inspection
omx sparkshell --tmux-pane %12 --tail-lines 400 # Tail tmux pane outputbash
omx explore --prompt "find where team state is written" # 只读仓库查询
omx sparkshell git status # 受限shell检查
omx sparkshell --tmux-pane %12 --tail-lines 400 # 跟踪tmux面板输出Instructions
使用说明
- Identify intent — match request to the best workflow skill (,
$plan,$ralph,$team)$deep-interview - Start with the recommended launch — for most sessions
omx --madmax --high - Use role prompts for analysis — before implementation
/prompts:architect "..." - Escalate when needed — let the agent pull in heavier workflows; don't force for simple tasks
$team - Use for vague requests — when intent, scope, or boundaries are unclear
$deep-interview - Point to references — link to the relevant references/ file for deep-dive details
- 明确需求 — 将请求匹配到最合适的工作流技能(、
$plan、$ralph、$team)$deep-interview - 使用推荐启动方式 — 大多数场景使用启动会话
omx --madmax --high - 使用角色提示词做分析 — 开发前先执行做架构分析
/prompts:architect "..." - 按需升级工作流 — 让Agent自动调用更重量级的工作流,简单任务不要强制使用
$team - 模糊请求使用— 当需求、范围或边界不明确时使用
$deep-interview - 提供参考信息 — 附上相关参考资料/文件路径方便深度调研
Examples
示例
Example 1: Standard session
示例1:标准会话
bash
omx --madmax --hightext
/prompts:architect "analyze the current auth flow"
$plan "implement OAuth safely"bash
omx --madmax --hightext
/prompts:architect "analyze the current auth flow"
$plan "implement OAuth safely"Example 2: Persistent execution
示例2:持久执行
text
$ralph "fix all failing tests and make them pass"Loop: execute → verify → fix, until all tests pass.
text
$ralph "fix all failing tests and make them pass"循环执行:执行 → 验证 → 修复,直到所有测试通过。
Example 3: Parallel team work
示例3:并行团队协作
bash
omx team 3:executor "refactor the API layer with proper tests"bash
omx team 3:executor "refactor the API layer with proper tests"Example 4: Clarify before coding
示例4:编码前澄清需求
text
$deep-interview "I want to add a payment system"One-question-at-a-time Socratic loop until intent is clear, then hands off to or .
$plan$ralphtext
$deep-interview "I want to add a payment system"采用单次提问的苏格拉底式循环直到需求明确,之后自动转交或执行。
$plan$ralphBest practices
最佳实践
- Codex-first — OMX is a workflow layer, not a replacement for Codex; start with
omx --madmax --high - Use before
$plan— plan first when scope is unclear; ralph for guaranteed execution$ralph - for consensus — use when multiple planning perspectives are needed before committing
$ralplan - gates execution — always use for vague greenfield or brownfield work
$deep-interview - Team mode is optional — only escalate to when the task genuinely needs parallel workers
$team - Cross-model consultation — and
$ask-claudefor second opinions on design or architecture$ask-gemini - for safe lookups — read-only; won't modify anything
omx explore - when stuck — diagnose installation issues before manual debugging
omx doctor
- 优先使用Codex能力 — OMX是工作流层,不是Codex的替代品,优先使用启动
omx --madmax --high - 执行前先调用
$ralph— 范围不明确时先做规划,ralph用于保障执行完成$plan - 需要共识规划时用— 当提交前需要多个规划视角时使用
$ralplan - 作为执行前置检查 — 所有模糊的新开发或存量改造工作都应该先使用
$deep-interview - 团队模式按需使用 — 只有任务确实需要并行工作器时才升级到模式
$team - 跨模型咨询 — 设计或架构需要第二意见时使用和
$ask-claude$ask-gemini - 安全查询使用— 只读模式,不会修改任何内容
omx explore - 遇到问题先执行— 手动调试前先诊断安装问题
omx doctor
Quick Reference
快速参考
| Command/Skill | Action |
|---|---|
| Recommended launch |
| Analysis and design review |
| Strategic planning |
| Clarify vague requests |
| Persistent loop until done |
| Consensus planning |
| Parallel coordinated agents |
| Maximum parallelism |
| Read-only repo exploration |
| Bounded shell inspection |
| Install/re-install OMX |
| Diagnose issues |
| Cancel active modes |
| 命令/技能 | 作用 |
|---|---|
| 推荐启动方式 |
| 分析与设计评审 |
| 战略规划 |
| 澄清模糊需求 |
| 持久循环直到完成 |
| 共识规划 |
| 并行协同Agent |
| 最大并发模式 |
| 只读仓库探索 |
| 受限shell检查 |
| 安装/重装OMX |
| 问题诊断 |
| 取消激活的模式 |
References
参考资料
| File | Contents |
|---|---|
| references/agents-catalog.md | All 30+ agent profiles and use cases |
| references/skills-reference.md | Full skill list with triggers and descriptions |
| references/cli-reference.md | Complete CLI: omx team/explore/sparkshell/reasoning |
| 文件 | 内容 |
|---|---|
| references/agents-catalog.md | 全部30+个Agent的介绍与使用场景 |
| references/skills-reference.md | 完整技能列表,包含触发词与描述 |
| references/cli-reference.md | 完整CLI文档:omx team/explore/sparkshell/reasoning |