Oh My Claude Code (OMC)

Problem it solves

Single-agent Claude Code hits a ceiling on complex tasks. You have a fullstack feature touching 15 files. Claude Code works sequentially: file 1… file 5… by file 8 it’s forgotten decisions from file 1. You re-explain. It acknowledges. File 11 — forgotten again.

You end up babysitting: splitting tasks manually, running multiple terminal sessions, merging outputs, catching conflicts. YOU become the orchestrator, and it’s exhausting.

OMC adds the missing layer. It decomposes your task, delegates to specialized agents (architect, executor, reviewer, designer), runs them in parallel or sequence, and coordinates the results. You go from “developer babysitting AI” to “tech lead directing an AI team.”

How to install

Prerequisites: Claude Code CLI installed, Claude Max/Pro subscription or Anthropic API key, tmux (for Team mode and rate-limit detection).

Step 1 — Install via plugin marketplace:

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

Step 2 — Run setup:

/omc-setup

To update later:

/plugin marketplace update omc
/omc-setup

Note: the npm package name is oh-my-claude-sisyphus (differs from the project branding). If you need the CLI tools globally: npm i -g oh-my-claude-sisyphus@latest.

Verify it’s working: type /oh-my-claudecode: to see OMC slash commands. The HUD statusline at the bottom of your terminal confirms active mode and agent count.

The execution modes — a decision framework

This is the core of OMC. Don’t think of these as “features” — think of them as the right tool for each job type.

Autopilot — Full auto, sequential

Use for clear single tasks with well-defined scope. Autopilot handles planning, execution, testing, and validation autonomously.

autopilot: Build a login page following our auth patterns

When NOT to use: Multi-file features where speed matters (too sequential), or vague requirements (it will go in circles).

Team — Staged pipeline with verification

The canonical multi-agent orchestrator since v4.1.7. Runs a structured pipeline: plan → PRD → execute → verify → fix loop. Specialized agents are routed per stage.

/team 3:executor "Build the dashboard feature — API, components, and tests"

When NOT to use: Simple tasks where the staged pipeline overhead isn’t justified.

Ultrapilot — Parallel, up to 5 workers

Parallel autopilot with file ownership partitioning. Each worker gets non-overlapping files so they don’t conflict.

ultrapilot: Build toolkit feature — schema, overview page, detail page, seed content

When NOT to use: Tasks with heavy interdependencies between files (agents will step on each other).

Ralph — Persistence until verified done

Ralph doesn’t stop until the Architect agent verifies completion. Includes ultrawork for parallelism. The name comes from Sisyphus — “the boulder never stops.”

ralph: Refactor the auth middleware — all tests must pass, zero type errors

When NOT to use: Vague scope without clear done criteria. Ralph will loop indefinitely improving things that don’t need improving.

Pipeline — Sequential chain, output flows forward

Each stage’s output becomes the next stage’s input. Built-in presets for common workflows.

pipeline: explore → architect → executor → qa-tester

When NOT to use: When stages aren’t clearly separable or when you need parallelism.

Ecomode — Cost-optimized parallel execution

Routes tasks to the cheapest capable model: simple lookups → Haiku, standard work → Sonnet, complex reasoning → Opus.

eco: Write docs for these 10 functions

When NOT to use: When quality is more important than cost.

Magic keywords quick reference

Execution modes

Utility commands

Agent shortcuts

Just use these words naturally in your prompt — OMC detects them and activates the right mode.

How to use — real examples

Here are practical workflows from daily usage. Each example shows the exact prompt and what OMC does with it.

Example 1: Build a feature from scratch

autopilot: Add a newsletter subscription form to the landing page.
Use ConvertKit API, validate email client-side, show success toast.

OMC activates autopilot: analyst extracts requirements → architect designs the component structure → executor implements the form, API call, and toast → verifier confirms it works. You get a working feature without managing any of the steps.

Example 2: Fix multiple bugs in parallel

/team 3:executor "Fix these 3 bugs:
1. Dark mode toggle doesn't persist across page reload
2. Mobile nav menu doesn't close after clicking a link
3. Search results show draft posts"

OMC spawns 3 executor agents, each claims one bug, works independently, and results get verified. Three bugs fixed in the time it takes to fix one.

Example 3: Refactor with guaranteed quality

ralph: Migrate all API routes from Express to Hono.
Done criteria: all tests pass, zero type errors, no Express imports remain.

Ralph keeps iterating — migrating routes, fixing type errors, running tests — until the architect verifies all three criteria are met. No partial migrations.

Example 4: Plan before building

plan: We need to add multi-tenancy to the app.
Each tenant gets isolated data, custom subdomain, and separate billing.

OMC starts a planning interview: asks about database strategy (shared vs separate), auth flow, billing integration. Produces a plan document before any code is written. Then you can run autopilot or ralph on the plan.

Example 5: Review code for quality and security

/code-review
/security-review

Run both in sequence on your current changes. Code review checks for logic defects, anti-patterns, naming. Security review scans for OWASP top 10, exposed secrets, auth bypasses. Both produce actionable findings with severity ratings.

Pro tips from daily usage

Tip 1: CLAUDE.md is your multiplier. Multi-agent without shared context = chaos. A solid CLAUDE.md becomes the “team agreement” all agents follow. Without it, two agents will name things differently, use different patterns, contradict each other. Write your CLAUDE.md before going multi-agent.

Tip 2: Plan before complex features. Spending 5 minutes in a planning interview saves 30 minutes of rework. Use plan before any feature that touches 5+ files. The planner + architect + critic consensus produces a solid implementation plan.

Tip 3: Ralph needs a finish line. Always give ralph a clear definition of done: “All tests pass”, “No TypeScript errors”, “Lint clean.” Without it, ralph loops indefinitely polishing things that are already fine.

Tip 4: Start with autopilot, graduate to team. Learn how OMC thinks with autopilot (predictable, sequential) before going parallel. Debugging 5 parallel agents is hard if you don’t understand what 1 agent does.

Tip 5: Ecomode for content tasks. Writing docs, generating test data, creating markdown files — these don’t need Opus. Ecomode routes them to Haiku/Sonnet, saving significant tokens.

When NOT to use OMC

• Small tasks (1-2 files): Vanilla Claude Code is faster. OMC overhead > benefit.
• Security-critical code: Multi-agent means less control per agent. Review security-sensitive changes manually.
• Repos without CLAUDE.md: Agents have no shared context. Set up CLAUDE.md first.
• Ralph + vague scope: Ralph loops forever. Define done criteria or don’t use ralph.
• Tight token budget + ultrapilot: Parallel agents multiply token usage. Use ecomode instead.

Related tools

• Custom Slash Commands — pair with OMC for reusable prompt templates that agents can reference
• Course: Multi-Agent Architecture — deep dive into how multi-agent orchestration works under the hood

Links

• GitHub: Yeachan-Heo/oh-my-claudecode — 9.9k stars, v4.8.2 (as of March 2026)
• Official docs