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

/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode
/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:

omc team 2:codex "review auth module for security issues"
omc team 2:gemini "redesign UI components for accessibility"
omc team 1:claude "implement the payment flow"
omc team status auth-review
omc team shutdown auth-review

/omc-teams remains as a legacy compatibility skill and now routes to omc team ....

For mixed Codex + Gemini work in one command, use the /ccg skill (routes via /ask codex + /ask gemini, then Claude synthesizes):

/ccg Review this PR — architecture (Codex) and UI components (Gemini)

| Surface | Workers | Best For | | ------------------------- | ------------------ | -------------------------------------------- | | omc team N:codex "..." | N Codex CLI panes | Code review, security analysis, architecture | | omc team N:gemini "..." | N Gemini CLI panes | UI/UX design, docs, large-context tasks | | omc team N:claude "..." | N Claude CLI panes | General tasks via Claude CLI in tmux | | /ccg | /ask codex + /ask gemini | Tri-model advisor synthesis |

Workers spawn on-demand and die when their task completes — no idle resource usage. Requires codex / gemini CLIs installed and an active tmux session.

Note: Package naming — The project is branded as oh-my-claudecode (repo, plugin, commands), but the npm package is published as oh-my-claude-sisyphus. If you install or upgrade the CLI tools via npm/bun, use npm i -g oh-my-claude-sisyphus@latest.

Updating

If you installed OMC via npm, upgrade with the published package name:

npm i -g oh-my-claude-sisyphus@latest

Package naming note: the repo, plugin, and commands are branded oh-my-claudecode, but the published npm package name remains oh-my-claude-sisyphus.

If you installed OMC via the Claude Code marketplace/plugin flow, update with:

# 1. Update the marketplace clone
/plugin marketplace update omc

# 2. Re-run setup to refresh configuration
/setup

If you are developing from a local checkout or git worktree, update the checkout first, then re-run setup from that worktree so the active runtime matches the code you are testing.

Note: If marketplace auto-update is not enabled, you must manually run /plugin marketplace update omc to sync the latest version before running setup.

If you experience issues after updating, clear the old plugin cache:

/omc-doctor

Why oh-my-claudecode?

• Zero configuration required - Works out of the box with intelligent defaults
• Team-first orchestration - Team is the canonical multi-agent surface
• Natural language interface - No commands to memorize, just describe what you want
• Automatic parallelization - Complex tasks distributed across specialized agents
• Persistent execution - Won't give up until the job is verified complete
• Cost optimization - Smart model routing saves 30-50% on tokens
• Learn from experience - Automatically extracts and reuses problem-solving patterns
• Real-time visibility - HUD statusline shows what's happening under the hood

Features

Orchestration Modes

Multiple strategies for different use cases — from Team-backed orchestration to token-efficient refactoring. Learn more →

| Mode | What it is | Use For