oh-my-claudecode

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

Role	Name	GitHub
Creator & Lead	Yeachan Heo	@Yeachan-Heo

Ambassadors

Name	GitHub
Sigrid Jin	@sigridjineth

Top Collaborators

Name	GitHub	Commits
JunghwanNA	@shaun0927	65
riftzen-bit	@riftzen-bit	52
Seunggwan Song	@Nathan-Song	20
BLUE	@blue-int	20
Junho Yeo	@junhoyeo	15

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

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.

Feature	Terminal CLI	In-session skill	Notes
Setup	omc setup	/setup or /omc-setup	Both are real entrypoints. /setup is the easiest plugin-first path.
Ask providers	omc ask codex "review this patch"	/ask codex "review this patch"	Both route through the same advisor flow.
Team orchestration	omc team 2:codex "review auth flow"	/team 3:executor "fix all TypeScript errors"	Both exist, but they are different runtimes: omc team launches tmux CLI workers; /team runs the in-session native team workflow.
Autopilot / Ralph / Ultrawork / Deep Interview	—	/autopilot ..., /ralph ..., /ultrawork ..., /deep-interview ...	These are in-session skills. There is no omc autopilot / omc ralph / omc ultrawork CLI subcommand in this repo.
Autoresearch	omc autoresearch ...	/deep-interview --autoresearch ...	omc autoresearch is the real CLI command. The in-session path is the setup/interview lane that helps you launch it.

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 (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: