oh-my-claudecode

English | 한국어 | 中文 | 日本語 | Español | Tiếng Việt | Português

Fork Notice: This repository is a maintained fork of oh-my-claudecode, focused on practical multi-agent orchestration for daily Claude Code workflows. Upstream credits remain intact, while this fork ships its own release cadence and custom integrations.

oh-my-claudecode

For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI.

Multi-agent orchestration for Claude Code. Zero learning curve.

Don't learn Claude Code. Just use OMC.

Get Started • Documentation • CLI Reference • Workflows • Migration Guide • Discord

---

Quick Start

Step 1: Install

Marketplace/plugin install (recommended for most Claude Code users):

/plugin marketplace add https://github.com/materialofair/oh-my-claudecode
/plugin install oh-my-claudecode

If you prefer the npm CLI/runtime path instead of the marketplace flow:

npm i -g claudecode-omc@latest

Step 2: Setup

/setup
/omc-setup

Step 3: Build something

autopilot: build a REST API for managing tasks

That's it. Everything else is automatic.

Not Sure Where to Start?

If you're uncertain about requirements, have a vague idea, or want to micromanage the design:

/deep-interview "I want to build a task management app"

The deep interview uses Socratic questioning to clarify your thinking before any code is written. It exposes hidden assumptions and measures clarity across weighted dimensions, ensuring you know exactly what to build before execution begins.

Team Mode (Recommended)

Starting in v4.1.7, Team is the canonical orchestration surface in OMC. The legacy swarm keyword/skill has been removed; use team directly.

/team 3:executor "fix all TypeScript errors"

Team runs as a staged pipeline:

team-plan → team-prd → team-exec → team-verify → team-fix (loop)

Enable Claude Code native teams in ~/.claude/settings.json:

{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  }
}

If teams are disabled, OMC will warn you and fall back to non-team execution where possible.

tmux CLI Workers — Codex & Gemini (v4.4.0+)

v4.4.0 removes the Codex/Gemini MCP servers (x, g providers). Use the CLI-first Team runtime (omc team ...) to spawn real tmux worker panes:

omc team 2:codex "review auth module for security issues"
omc team 2:gemini "redesign UI components for accessibility"
omc team 1:claude "implement the payment flow"
omc team status auth-review
omc team shutdown auth-review

/omc-teams remains as a legacy compatibility skill and now routes to omc team ....

For mixed Codex + Gemini work in one command, use the /ccg skill (routes via /ask codex + /ask gemini, then Claude synthesizes):

/ccg Review this PR — architecture (Codex) and UI components (Gemini)

Surface	Workers	Best For
omc team N:codex "..."	N Codex CLI panes	Code review, security analysis, architecture
omc team N:gemini "..."	N Gemini CLI panes	UI/UX design, docs, large-context tasks
omc team N:claude "..."	N Claude CLI panes	General tasks via Claude CLI in tmux
/ccg	/ask codex + /ask gemini	Tri-model advisor synthesis

Workers spawn on-demand and die when their task completes — no idle resource usage. Requires codex / gemini CLIs installed and an active tmux session.