oh-my-claudecode

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

oh-my-claudecode

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

Don't learn Claude Code. Just use OMC.

Get Started • Full Reference • Migration Guide • Architecture

---

Quick Start

Step 1: Install (from a local checkout)

This fork is run directly from a local checkout — there is no published npm package or marketplace listing.

# Clone this repo
git clone https://github.com/markrmiller/oh-my-claudecode.git
cd oh-my-claudecode

# Install dependencies and build the plugin + CLI
npm install
npm run build

# Expose the `omc` command from the checkout (ensure ~/.local/bin is on your PATH)
mkdir -p ~/.local/bin
ln -sf "$PWD/bridge/cli.cjs" ~/.local/bin/omc
omc --version

Step 2: Setup

Point Claude Code at your local checkout and run setup in one step:

# From the checkout directory
omc --plugin-dir "$PWD" setup --plugin-dir-mode

Then launch Claude Code normally — it will use your local checkout. Inside a session you can also re-run /setup or /omc-setup.

.mcp.json server conflict: with --plugin-dir, the repo's .mcp.json server named "t" collides with the plugin's own. Add { "disabledMcpjsonServers": ["t"] } to your ~/.claude/settings.json. See the Plugin directory flags section in REFERENCE.md and CONTRIBUTING.md for the full local-checkout flows.

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 using the omc symlink created from your local checkout (see Install above).
• 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, grok.
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.

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)