Data analysis and research execution specialist
Security vulnerability detection specialist (OWASP Top 10, secrets, unsafe patterns)
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows
Evidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendations
Verification strategy, evidence-based completion checks, test adequacy
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
Full autonomous execution from idea to working code
Cancel any active OMC mode (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team)
Claude-Codex-Gemini tri-model orchestration via /ask codex + /ask gemini, then Claude synthesizes results
Matches all tools
Hooks run on every tool call, not just specific ones
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Executes bash commands
Executes bash commands
Hook triggers when Bash tool is used
Hook triggers when Bash tool is used
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
English | 한국어 | 中文 | 日本語 | Español | Tiếng Việt | Português
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
| Role | Name | GitHub |
|---|---|---|
| Creator & Lead | Yeachan Heo | @Yeachan-Heo |
| Name | GitHub |
|---|---|
| Sigrid Jin | @sigridjineth |
| Name | GitHub | Commits |
|---|---|---|
| JunghwanNA | @shaun0927 | 65 |
| riftzen-bit | @riftzen-bit | 52 |
| Seunggwan Song | @Nathan-Song | 20 |
| BLUE | @blue-int | 20 |
| Junho Yeo | @junhoyeo | 15 |
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.
OMC exposes two different surfaces:
omc ... from your shell after installing the npm/runtime path (npm i -g oh-my-claude-sisyphus@latest) or from a local checkout./... 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. |
If you're uncertain about requirements, have a vague idea, or want to micromanage the design:
npx claudepluginhub hakilee/oh-my-claudecodeAutomated design system construction from repository analysis to production-ready implementation.
v9.52.0 - Reliability wave: tangle contextual review correction loop with hard round ceiling, progress-supervised review rounds (per-agent stall watch, descendant-tree kills), council diversity and agy pin fixes, marketplace generator source-of-truth fix, provider troubleshooting runbook and cost-expectations docs. Run /octo:setup.
Evidence-gated AI coding workflow: scan → analyze → plan → TDD → execute → fix → verify → review, powered by Codebase Memory MCP >= 0.9.0 with optional Serena LSP intelligence. Includes blast-radius planning, test/cycle gates, independent review, and Windows Git Bash hook auto-resolution.
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows