### Install and Initialize OMX

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Standard commands for installing the package and performing initial setup or diagnostics.

```bash
1
2
3
4
5
6npm install -g oh-my-codex
omx
omx setup
omx doctor
omx resume
omx --xhigh --madmax
```

--------------------------------

### Setup and Verify Installation

Source: https://yeachan-heo.github.io/oh-my-codex-website

Runs the setup script and then verifies the installation by running the doctor command. Ensure this is run after installing the package.

```bash
omx setup && omx doctor
```

--------------------------------

### Install oh-my-codex via npm

Source: https://yeachan-heo.github.io/oh-my-codex-website

Installs the oh-my-codex package globally using npm. This is the first step to get started with the tool.

```bash
npm install -g oh-my-codex
```

--------------------------------

### Configure notifications

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Export environment variables for notification platforms and run the setup command to generate the configuration file.

```bash
export OMX_TELEGRAM_BOT_TOKEN=xxx
export OMX_TELEGRAM_CHAT_ID=xxx
export OMX_DISCORD_WEBHOOK_URL=xxx
export OMX_SLACK_WEBHOOK_URL=xxx

omx setup
```

--------------------------------

### Team Worktree Lifecycle Examples

Source: https://yeachan-heo.github.io/oh-my-codex-website

Illustrates how team workers automatically get isolated git worktrees for parallel execution and how to configure mixed-provider teams.

```bash
# Workers get worktrees automatically — no flags needed
$ omx team 3:executor "refactor auth module"
Team started: refactor-auth-module
workers: 3 (worktrees: automatic, detached)

$ omx team status refactor-auth-module
worker-1: worktree=.omx/team/.../worker-1  status=in_progress
worker-2: worktree=.omx/team/.../worker-2  status=completed
worker-3: worktree=.omx/team/.../worker-3  status=completed
tasks: completed=2 in_progress=1
integration: merged=2 conflicts=0
```

```bash
# Mixed providers with worktrees
$ OMX_TEAM_WORKER_CLI_MAP=codex,claude,gemini \
  omx team 3:executor "full-stack implementation"
```

--------------------------------

### Install and Verify Oh My Codex

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Standard installation procedure using npm and verification via the doctor command.

```bash
# 1. Install globally
npm install -g oh-my-codex

# 2. Run setup
omx setup

# 3. Verify installation
omx doctor
```

--------------------------------

### Execute Quick Start Commands

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Usage of magic keywords and skill commands within the Codex CLI to initiate tasks and planning.

```bash
# Inside Codex CLI:
/prompts:architect "analyze current auth boundaries"
/prompts:executor "implement input validation in login"
$plan "ship OAuth callback safely"
$team 3:executor "fix all TypeScript errors"
```

--------------------------------

### Example OMX Agent Task Invocation

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Examples of how to invoke specific agent functionalities using natural language prompts within OMX. These demonstrate autonomous building, refactoring, parallel work, team coordination, and planning.

```bash
"autopilot build a React dashboard"
```

```bash
"ralph refactor the API"
```

```bash
"ulw fix all errors"
```

```bash
"team 5:executor refactor backend"
```

```bash
"plan the auth system"
```

--------------------------------

### Basic Command Surface Examples

Source: https://yeachan-heo.github.io/oh-my-codex-website

Demonstrates common commands for autonomous research, executing commands through the orchestration layer, and initiating team-based refactoring tasks.

```bash
$ omx autoresearch "how does the auth middleware work?"
```

```bash
$ omx exec npm test -- --coverage
```

```bash
$ omx team 3 "refactor auth module with full test coverage"
```

--------------------------------

### Configure Gemini-Powered Teams

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Examples for running teams with Gemini workers, including provider mapping, model selection, and launch arguments.

```bash
# 1. Start a mixed provider team
export OMX_TEAM_WORKER_CLI_MAP=codex,claude,gemini
omx team 3:executor "full-stack implementation"

# 2. Force all workers to Gemini
export OMX_TEAM_WORKER_CLI=gemini
omx team 2:architect "large-scale architectural review"

# 3. Pass explicit Gemini models
export OMX_TEAM_WORKER_LAUNCH_ARGS="--model gemini-2.0-flash-exp"
omx team 1:executor "experimental feature"
```

--------------------------------

### Query AI advisors

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Examples of using the omx ask command to query different AI models with specific prompts and agent roles.

```bash
# Simple queries
omx ask claude "review this diff"
omx ask gemini "brainstorm alternatives for the auth system"

# Role-specific queries
omx ask claude --agent-prompt executor "implement feature X with tests"
omx ask gemini --agent-prompt planner "draft a rollout plan for v0.9"

# Shorthand prompt flags
omx ask claude -p "summarize the recent changes"
omx ask gemini --prompt "check this regex for errors"
```

--------------------------------

### Terminal Commands for OMX Team Management

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Use these commands to manage and interact with OMX teams from the terminal. Commands include starting tasks, checking status, and shutting down teams.

```bash
omx team 4:executor "parallelize a multi-module refactor"
```

```bash
omx team status <team-name>
```

```bash
omx team shutdown <team-name>
```

--------------------------------

### Initialize and Execute Codex CLI Commands

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Basic commands for refreshing hook wiring, executing parallel tasks, and initiating deep interviews.

```bash
1
2
3omx setup          # refreshes native hook wiring
omx team 3:executor "parallel task"
omx deep-interview "feature idea"
```

--------------------------------

### Explore and Resume Sessions

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Commands for read-only repository exploration and resuming previous interactive work sessions.

```bash
1
2
3
4
5
6
7
8
9
10# Read-only repository exploration
omx explore --prompt "which files define team routing"
omx explore --prompt-file prompts/explore-task.md

# Resume interactive work
omx resume
```

--------------------------------

### OMX Configuration and Security

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Settings for hardening the MCP working directory and configuring project-level defaults.

```APIDOC
## Configuration and Security

### Description
Manage security constraints for MCP tools and project-level configuration.

### MCP Working Directory Policy
To constrain MCP state/memory/trace tools to specific roots, set the environment variable:
`export OMX_MCP_WORKDIR_ROOTS="/path/to/project:/path/to/another-root"`

### Setup Configuration
Run `omx setup` to configure defaults. Use `--scope user` or `--scope project` to control where files are installed.
```

--------------------------------

### Inspect sparkshell

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Commands for checking the version and inspecting sparkshell with tmux integration.

```bash
omx sparkshell git --version
omx sparkshell --tmux-pane %12 --tail-lines 400
```

--------------------------------

### OMX CLI Core Commands

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Reference for the primary commands used to launch, configure, and manage the OMX environment.

```APIDOC
## CLI Commands

### Description
Core commands for interacting with the OMX CLI, including setup, diagnostics, and session management.

### Commands
- **omx** - Launch Codex CLI (HUD auto-attaches in tmux)
- **omx setup** - Install skills, prompts, MCP servers, and AGENTS.md. Supports `--scope user|project`.
- **omx agents-init .** - Bootstrap lightweight AGENTS.md files for a repository or subtree.
- **omx doctor** - Check installation health. Use `--team` for worker diagnostics.
- **omx ask <provider>** - Directly query advisor (claude|gemini). Supports `--agent-prompt <name>`.
- **omx resume** - Resume a previous interactive Codex session from the terminal.
- **omx explore** - Default read-only exploration surface for shell-native repository inspection.
- **omx sparkshell** - Explicit shell-native inspection command with adaptive summaries.
- **omx team** - Spawn/status/resume/shutdown parallel worker panes in tmux.
- **omx ralph** - Launch Codex with ralph persistence mode active.
- **omx status** - Show active modes and execution state.
- **omx cancel** - Cancel active execution modes.
- **omx hud** - Inspect runtime HUD state.
- **omx reasoning [mode]** - Show or set model reasoning effort (low|medium|high|xhigh).
```

--------------------------------

### Notepad Tools in MCP

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Tools for interacting with the OMX notepad, a dedicated workspace for long-running sessions. Supports prioritized, working, and manual writes.

```bash
notepad_read
```

```bash
notepad_write_priority
```

```bash
notepad_write_working
```

```bash
notepad_write_manual
```

--------------------------------

### Manage Team Worktrees

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Commands for initiating team tasks, checking status, and configuring mixed-provider teams using worktrees.

```bash
# Worktrees are automatic — no flags needed
omx team 3:executor "implement feature X"

# Check worker worktree status
omx team status <team-name>
# Output includes: worktree_path, worktree_branch, worktree_detached per worker

# Mixed providers — all get worktrees
OMX_TEAM_WORKER_CLI_MAP=codex,claude,gemini omx team 3:executor "full-stack work"
```

--------------------------------

### Configure Custom Webhook and CLI Commands

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Advanced JSON configuration for custom webhook endpoints and CLI command execution based on specific events.

```json
{
  "notifications": {
    "custom_webhook_command": {
      "enabled": true,
      "url": "https://api.example.com/hooks",
      "method": "POST",
      "headers": { "X-Api-Key": "my-secret-key" },
      "events": ["session-end", "ask-user-question"]
    },
    "custom_cli_command": {
      "enabled": true,
      "command": "notify-send \"OMX: {{event}}\" \"{{message}}\"",
      "events": ["session-start", "session-end"]
    }
  }
}
```

--------------------------------

### Interact with Team CLI API

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Perform programmatic task management using JSON-based state transitions for stable coordination.

```bash
# Create a task programmatically
omx team api create-task --input '{"team_name":"my-team","subject":"Fix bug","description":"..."}' --json

# Claim a task with versioned safety
omx team api claim-task --input '{"team_name":"my-team","task_id":"1","worker":"worker-1"}' --json

# Transition terminal task status after claiming
omx team api transition-task-status --input '{"team_name":"my-team","task_id":"1","from":"in_progress","to":"completed","claim_token":""}' --json
```

--------------------------------

### OMX Team Pipeline Stages

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Illustrates the staged pipeline for teams in OMX, showing the transition between planning, production, execution, verification, and fixing stages. Each transition has specific trigger conditions.

```markdown
1
team-plan
→
2
team-prd
→
3
team-exec
→
4
team-verify
→
5
team-fix
```

--------------------------------

### Configure Advanced Team Workflows

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Bash commands for managing team worker configurations, including provider mapping, model selection, and dynamic scaling.

```bash
# Mix different AI providers in one team
export OMX_TEAM_WORKER_CLI_MAP=codex,claude,gemini
omx team 3:executor "parallel refactoring"

# Force all workers to Gemini CLI
export OMX_TEAM_WORKER_CLI=gemini
omx team 2:executor "sync docs and report"

# Force a specific model for workers
export OMX_TEAM_WORKER_LAUNCH_ARGS="--model gpt-5.3-codex-spark"
omx team 2:architect "design the system"

# Enable dynamic scaling
export OMX_TEAM_SCALING_ENABLED=1
omx team 2:executor "task"
```

--------------------------------

### State Management Tools in MCP

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

These tools are used for managing the execution state of OMX. They allow reading, writing, and clearing the state, which is crucial for resumable execution.

```bash
state_read
```

```bash
state_write
```

```bash
state_clear
```

--------------------------------

### AST Grep Tools for Refactoring

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Tools for structural refactoring using Abstract Syntax Tree (AST) matching. Supports searching and replacing code based on its structure.

```bash
ast_grep_search
```

```bash
ast_grep_replace
```

--------------------------------

### Configure Native Codex Notifications

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Standard TOML configuration for enabling notifications and setting up Telegram and Slack integrations.

```toml
[notifications]
enabled = true
verbosity = "session"

[notifications.telegram]
enabled = true
botToken = "123456:ABC-DEF"
chatId = "-100123456789"

[notifications.slack]
enabled = true
webhookUrl = "https://hooks.slack.com/services/xxx"
mention = "@U12345"
```

--------------------------------

### LSP Tools for Code Intelligence

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Language Server Protocol (LSP) tools provide code intelligence features like hover information, go to definition, finding references, diagnostics, and renaming.

```bash
lsp_hover
```

```bash
lsp_goto_definition
```

```bash
lsp_find_references
```

```bash
lsp_diagnostics
```

```bash
lsp_rename
```

--------------------------------

### Configure MCP Working Directory Roots

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Set an allowlist of roots to constrain the working directory for MCP tools.

```bash
export OMX_MCP_WORKDIR_ROOTS="/path/to/project:/path/to/another-root"
```

--------------------------------

### Configure Mixed AI Worker Teams

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Define a team using multiple AI providers by mapping them to the worker CLI environment variable.

```bash
# Mix Codex, Gemini, and Claude workers in one team
export OMX_TEAM_WORKER_CLI_MAP=codex,gemini,claude
omx team 3:executor "refactor the shared runtime docs"
```

--------------------------------

### Configure OpenClaw Notification Profile

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Defines the OpenClaw notification profile in JSON, including gateway settings and event hooks for session management.

```json
{
  "notifications": {
    "verbosity": "verbose",
    "openclaw": {
      "enabled": true,
      "gateways": {
        "local": {
          "type": "http",
          "url": "http://127.0.0.1:18789/hooks/agent",
          "headers": { "Authorization": "Bearer ${HOOKS_TOKEN}" }
        }
      },
      "hooks": {
        "session-start": {
          "enabled": true,
          "gateway": "local",
          "instruction": "[session-start|exec] project={{projectName}} session={{sessionId}}"
        },
        "ask-user-question": {
          "enabled": true,
          "gateway": "local",
          "instruction": "[ask-user-question|exec] session={{sessionId}} question={{question}}"
        }
      }
    }
  }
}
```

--------------------------------

### Launch Teams in Isolated Worktrees

Source: https://yeachan-heo.github.io/oh-my-codex-website/docs.html

Prevent file conflicts during parallel execution by isolating team operations within specific git worktrees.

```bash
# Launch in a new worktree
omx team 4:executor "feature work" --worktree=feature-branch
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.