oh-my-claude-sisyphus weekly downloads statistics

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

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

Then:

If you prefer the npm CLI/runtime path instead of the marketplace flow:

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

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

Named autopilot stage profiles (v1)

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

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:

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 | /omc-setup | Both are real entrypoints. | | 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, muse. | | 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. | | Pre-flight danger scan | omc lookout scan --brief "..." [--json] [--strict] | — | Advisory only: scans the task briefing and workspace before an unattended run and reports danger findings (findings/severity contract). Exit codes: 0 for successful non-strict scans (and strict scans without high-risk signals), 1 --strict with high-risk signals, 2 usage/scan error. | | Autopilot / Ralph / Execute / Deep Interview | — | /autopilot ..., /ralph ..., /execute ..., /deep-interview ... | These are in-session skills. There is no omc autopilot / omc ralph / omc execute 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…

Description from the npm listing.