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.

> Liked OmC but found it a bit overkill? Try gajae-code. > Keeps Claude OAuth as-is while being faster, cheaper, simpler, and more powerful — with an SDK-based integration path built for OpenClaw, Hermes, Grokbot, and similar agent runtimes.

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 [email protected] during the CLI install. > This currently comes from the upstream better-sqlite3 native-addon dependency > (better-sqlite3 -> prebuild-install); [email protected] 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
/omc-setup

# From your terminal
omc setup

If you run OMC via omc --plugin-dir or claude --plugin-dir , 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

Named autopilot stage profiles (v1)

Select a configured stage profile only through /autopilot --workflow :

/autopilot --workflow plan-build-qa "build a REST API for managing tasks"

Profiles are configured under autopilot.workflows in .claude/omc.jsonc (project) or ~/.config/claude-omc/config.jsonc (user). A v1 profile contains only version: 1 and stages:

{
  "autopilot": {
    "workflows": {
      "plan-build-qa": {
        "version": 1,
        "stages": ["ralplan", "execution", "qa"]
      }
    }
  }
}

The admitted sequences are [ralplan, execution], [ralplan, execution, ralph], [ralplan, execution, qa], and [ralplan, execution, ralph, qa]. A project profile of the same name wholly replaces the user profile; different names coexist. Environment variables cannot define profiles. Profiles remain within autopilot's existing state, cancel, resume, Stop, and HUD lifecycle; legacy invocations without --workflow remain compatible.

Named profiles currently require Linux with the flock utility because their transcript evidence boundary uses Linux no-follow file-descriptor traversal and their recoverable mutation lock uses kernel advisory locking. Unsupported environments reject explicit --workflow invocation before creating or changing autopilot state; legacy autopilot remains available.

V1 intentionally excludes model fields or routing (stageModels), inline execution, dynamic commands/modes/state, arbitrary stages or plugins, and the separate custom-skill frontmatter parser mismatch. See Named Autopilot Stage Profiles ADR and Reference.