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

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

Core Maintainers

Ambassadors

Document Specialists

Top Collaborators

Quick Start

Step 1: Install

Marketplace/plugin install (recommended for most Claude Code users). These are Claude Code slash commands — enter them one at a time (pasting both lines at once will fail):

/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode

Then:

/plugin install oh-my-claudecode

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

npm i -g oh-my-claude-sisyphus@latest

Known npm warning: npm may print deprecated prebuild-install@7.1.3 during the CLI install. This currently comes from the upstream better-sqlite3 native-addon dependency (better-sqlite3 -> prebuild-install); prebuild-install@7.1.3 is still the latest published version, so there is no safe repo-side dependency bump or override to remove the warning yet. The warning is tracked in #2913 and does not by itself mean the OMC CLI install failed.

Step 2: Setup

# Inside a Claude Code / OMC session
/setup
/omc-setup

# From your terminal
omc setup

If you run OMC via omc --plugin-dir <path> or claude --plugin-dir <path>, add --plugin-dir-mode to omc setup (or export OMC_PLUGIN_ROOT before running it) so the installer doesn't duplicate skills/agents that the plugin already provides at runtime. See the Plugin directory flags section in REFERENCE.md for a complete decision matrix and all available flags.

Step 3: Build something

# Inside a Claude Code / OMC session
/autopilot "build a REST API for managing tasks"

# Natural-language in-session shortcut
autopilot: build a REST API for managing tasks

That's it. Everything else is automatic.

CLI Commands vs In-Session Skills

OMC exposes two different surfaces:

• Terminal CLI commands: run omc ... from your shell after installing the npm/runtime path (npm i -g oh-my-claude-sisyphus@latest) or from a local checkout.
• In-session skills: run /... inside a Claude Code session after installing the plugin/setup flow.

VS Code, Agent SDK, and automation scope

• VS Code / IDE extension: OMC does not ship a VS Code extension and does not document extension-specific install or automation flows. Use the Claude Code plugin or terminal CLI surfaces above; IDE integrations are only an optional way to access Claude Code itself.
• Agent SDK / programmatic usage: the npm package exports TypeScript helpers such as createOmcSession() and prompt expansion utilities for local Node.js programs using @anthropic-ai/claude-agent-sdk. This is a library surface, not a replacement for the Claude Code plugin UI.
• CI/CD and headless automation: prefer deterministic terminal commands (omc setup, omc ask, omc session search, repository scripts such as npm run sync-metadata:verify) and set ANTHROPIC_API_KEY or provider-specific CLI auth in the runner environment. Do not rely on interactive slash commands (/autopilot, /ralph, /team) in CI; they require an active Claude Code session.

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"

Use /team ... when you want Claude Code's in-session native team workflow. Use omc team ... when you want terminal-launched tmux CLI workers (claude / codex / gemini panes).

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 & Antigravity (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 2:antigravity "redesign UI components for accessibility"
omc team 1:claude "implement the payment flow"
omc team 1:cursor "implement the payment flow"
omc team status auth-review
omc team shutdown auth-review

/omc-teams remains as a legacy compatibility sk