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
Document Specialists
Name GitHub
devswha @devswha
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
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
Named autopilot stage profiles (v1)
Select a configured stage profile only through /autopilot --workflow <name> <task>:
/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.
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. Providers: claude, codex, gemini, antigravity, grok, cursor.
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 (hard-deprecated shim)
/deep-interview --autoresearch ... + /oh-my-claudecode:autoresearch
Setup stays in deep-interview; execution now belongs to the stateful skill.
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 asnpm run sync-metadata:verify) and setANTHROPIC_API_KEYor 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 requireme