omcx

omc-codex

Two AI models enter. Better code leaves.

Bridge between oh-my-claudecode and OpenAI Codex — each model handles what it's best at, with automatic cross-model fallback when either is unavailable.

Why omc-codex?

Claude and Codex each have distinct strengths. This plugin assigns each model to the role it excels at and automatically falls back when either is unavailable:

When Claude hits rate limits, quota, or any error → Codex takes over automatically. When Codex is unavailable → Claude agents cover all roles. Work never stalls.

# The complete forge: plan → blind TDD → build → stress harden → review → ship
/omcx:forge implement payment processing with refund support

# Quick feature with full cross-model pipeline
/omcx:pipeline implement user notification system with email and slack

# Claude grinds + Codex validates in a loop until both agree
/omcx:auto-ralph fix all TypeScript errors and make tests pass

# 3 Claude agents + 2 Codex agents build in parallel
/omcx:team 3:claude:executor,2:codex implement the entire auth subsystem

# Adversarial hardening: Codex attacks, Claude defends
/omcx:stress src/payment/processor.ts

Quick Start

One-liner install:

curl -fsSL https://raw.githubusercontent.com/jhcdev/omc-codex/main/install.sh | bash

This automatically:

• Clones the plugin to ~/.claude/plugins/marketplaces/omc-codex
• Configures ~/.claude/settings.json
• Checks Node.js, Codex CLI, and auth status
• Re-running updates to the latest version

Then in Claude Code:

# 1. Reload plugins
/reload-plugins

# 2. (Optional) Install & auth Codex CLI for full cross-model power
npm install -g @openai/codex && codex login

# 3. Run your first forge:
/omcx:forge add search feature to the API

# 1. Clone the plugin
git clone https://github.com/jhcdev/omc-codex.git ~/.claude/plugins/marketplaces/omc-codex

# 2. Add to ~/.claude/settings.json (see Configuration below)

# 3. Install Codex CLI & authenticate (optional)
npm install -g @openai/codex
codex login

# 4. Reload in Claude Code
/reload-plugins

What just happened?

🧠 Claude planned the search architecture
🧪 Codex wrote tests from spec (blind — never saw Claude's plan)
🔨 Claude built the feature from tests (blind — tests were the spec)
⚔️  Codex tried to break it with adversarial inputs
🛡️  Claude fixed every vulnerability Codex found
🔍 Codex gave a final structured review
📊 Result: battle-tested code verified by two AI model families

Configuration

Add to ~/.claude/settings.json:

{
  "enabledPlugins": {
    "omcx@omc-codex": true
  },
  "extraKnownMarketplaces": {
    "omc-codex": {
      "source": {
        "source": "url",
        "url": "https://raw.githubusercontent.com/jhcdev/omc-codex/main/.claude-plugin/marketplace.json"
      }
    }
  }
}

Prerequisites

Strength-Based Role Routing

Each model is assigned to phases where it performs best:

Claude Code Strengths → Builder & Thinker

• Planning: Handles ambiguous requirements, designs architecture with deep reasoning
• Complex implementation: Multi-file changes with full codebase context (ralph loop)
• Debugging: Reasoning chains for root-cause analysis
• Synthesis: Merges multiple review reports, prioritizes by real-world impact

Codex Strengths → Reviewer & Validator

• Structured review: Fast scan with consistent JSON output (severity/file/line)
• Adversarial review: Skeptical stance, finds edge cases and failure modes
• Quick fixes: Sandboxed, fast execution for well-scoped changes (1-2 files)
• Cross-model validation: Different perspective catches blind spots

Cross-Model Fallback

When one model is unavailable, the other covers all roles: