August 27, 2026 · By YasKad
Yeachan-Heo/oh-my-claudecode

oh-my-claudecode: teams-first multi-agent orchestration for Claude Code, installed as an official plugin

Yeachan-Heo/oh-my-claudecode · 39,354★ · 3,514 forks

oh-my-claudecode (OMC) installs a “teams-first” orchestration layer on top of Claude Code: it turns a single agent session into a team of specialized agents that plans, executes, verifies, and fixes, without the user having to learn new commands. It installs from Claude Code’s own plugin system or from npm, is MIT-licensed, and as of August 22, 2026 has accumulated over 38,000 stars.


Origin

The repository was created on January 9, 2026 by Yeachan Heo (Yeachan-Heo), an algorithmic trader and leader of the Korean quant community Quant.start(), linked to Layoff-Labs and based in Seoul. OMC is by far his largest repository: it tops a list of 67 public repositories with 4,731 followers.

The creation date matters for context: that same day, January 9, 2026, Hacker News discussed Anthropic blocking third-party use of Claude Code subscriptions (a thread with 625 points). OMC was born right after that restriction, explicitly building on oh-my-opencode as its cited inspiration. The author’s companion website describes itself with the phrase “They banned us. We came back.” The consistent reading across recovered sources is that OMC reframes “inside the official system” a tradition of orchestration that used to live in third-party clients: instead of working around Claude Code, it installs on top of it via its own plugin system.

A detail the README clarifies: the project is branded oh-my-claudecode (repository, plugin, and commands), but the npm package is published as oh-my-claude-sisyphus; installing or updating via npm requires that second name.

A striking, impactful hero image for a tech article about oh-my-claudecode: a dark command-line terminal floating in a cyberpunk developer workspace, its screen displaying an abstract multi-agent orchestration pipeline. Five glowing nodes labeled with minimal glyphs for plan, PRD, execute, verify, and fix are connected by neon circuit traces, with a circular feedback loop from fix back to verify. At the center, a translucent orchestrator hologram coordinates a team of specialized agent avatars—planner, critic, executor, verifier, and fixer—each rendered as a sleek geometric robot silhouette with distinct neon colors: cyan, magenta, amber, violet, and green. The background is a deep charcoal dark-mode interface with subtle grid lines, floating GitHub star icons, terminal glyphs, and a faint Seoul skyline in the distance. Include a small neon badge reading "OMC" and "38K stars". Ultra-detailed, cinematic lighting, cyberpunk tech aesthetic, neon accents, dark mode, 8K resolution.

Philosophy and principles

The README’s tagline is “Multi-agent orchestration for Claude Code. Zero learning curve” and “Don’t learn Claude Code. Just use OMC.” The principles verifiable in the documentation:

  • Zero configuration: smart defaults; the user describes what they want in natural language.
  • Teams-first orchestration: the Team mode is the canonical multi-agent surface; the legacy swarm keyword was removed as of v4.1.7.
  • Automatic parallelization: complex tasks are split across specialized agents.
  • Persistent execution: it doesn’t “give up” until the task is verified complete (Ralph mode).
  • Cost optimization: smart model routing (Haiku for simple tasks, Opus for complex reasoning); the README claims 30–50% token savings.
  • Learning from experience: extracts problem-solving patterns and reuses them as skills.
  • Real-time visibility: a status line (HUD) shows what’s happening underneath.

The core idea versus the competition: it’s not a single agent calling subagents “as tools,” but a pipeline stage where each role (planner, critic, executor, verifier) is an agent with its own context that validates the others.

A section image representing zero configuration and natural-language control: a user's spoken phrase appears as soft white sound waves entering a dark terminal, then transforming into a neatly organized team pipeline without any settings panels, sliders, or code. The pipeline shows specialized agents automatically assembling into a squad, with a small HUD status line at the bottom showing real-time activity in minimal neon text. The composition is clean, calm, and futuristic, emphasizing "don't learn Claude Code, just use OMC" through an abstract signboard with stylized glyphs. Dark mode, cyberpunk tech aesthetic, neon mint and electric blue accents, ultra-detailed, 8K resolution.

How it works

OMC exposes two surfaces: terminal CLI commands (omc ...), after installing the npm/runtime package, and in-session skills (/...), inside a Claude Code session after the plugin/setup flow.

The canonical Team pipeline is:

team-plan → team-prd → team-exec → team-verify → team-fix (loop)

A detailed infographic-style illustration of the canonical Team pipeline: five large hexagonal nodes arranged in a horizontal flow—team-plan, team-prd, team-exec, team-verify, team-fix—connected by bright neon arrows. The final node loops back to team-verify with a circular repair beam, suggesting persistent correction until completion. Each node contains an icon: blueprint, document, gears, shield-check, wrench. Surrounding the pipeline are small agent avatars with role badges, and a HUD strip displays live metrics such as "verified", "correcting", and "complete". The visual should feel like a high-end dark-mode dashboard. Dark mode, cyberpunk tech aesthetic, neon orange, cyan, and purple accents, ultra-detailed, 8K resolution.

Autopilot mode is a five-stage autonomous pipeline: (1) Expansion — the analyst and architect agents clarify requirements and produce a spec; (2) Planning — planner creates the plan and critic reviews it; (3) Execution — executor writes the code, in parallel when needed; (4) QA — verifies build and tests, fixes and re-verifies; (5) Validation — specialists review functionality, security, and quality.

A section image of Autopilot mode: a large central leader agent hologram guiding five sequential phases around a circular track. Phase 1 shows analyst and architect agents expanding requirements into a glowing specification sheet. Phase 2 shows planner and critic agents reviewing a blueprint. Phase 3 shows executor agents writing code in parallel streams. Phase 4 shows QA agents running build, test, lint, and typecheck checks with green checkmarks. Phase 5 shows specialist agents validating functionality, security, and quality with a final shield emblem. The scene is autonomous, smooth, and command-center-like, with a dark cockpit interface and subtle radar sweeps. Dark mode, cyberpunk tech aesthetic, neon teal and gold accents, ultra-detailed, 8K resolution.

The documented orchestration modes are: Team (canonical), omc team (CLI) (real tmux workers for claude/codex/gemini/antigravity/grok/cursor-agent), ccg (three-model advisors), Autopilot (single leader agent), Ultrawork (maximum non-team parallelization), Ralph (persistent verify/fix loops), UltraQA, Pipeline (sequential), and Ultrapilot (legacy).

The project documents 19 specialized agents in the README, while docs/REFERENCE.md counts them as “29 total” once level variants (LOW/Haiku, MEDIUM/Sonnet, HIGH/Opus) are included. Skills are counted as 38 in REFERENCE.md.

A section image showing specialized agents and intelligent model routing: a neon hierarchy of agent cards arranged by domain—analysis, execution, search, research, frontend, docs, visual, planning—and by model tier. Three glowing tiers are labeled abstractly as LOW, MEDIUM, and HIGH, represented by small Haiku-like sparks, balanced Sonnet-like beams, and powerful Opus-like reactor cores. A cost-optimization gauge shows a 30–50% token savings indicator, with simple tasks routed to lightweight models and complex reasoning routed to heavyweight models. Parallel task lanes split and merge into a verified output. Dark mode, cyberpunk tech aesthetic, neon violet, cyan, and lime accents, ultra-detailed, 8K resolution.

Magic keywords trigger skills without an explicit command: ralph, ulw (ultrawork), ralplan, deepsearch, ultrathink, and stopomc/cancelomc to stop. The README also documents /deep-interview (Socratic questions before writing code), custom skills under .omc/skills/, and a lifecycle-event hooks system.

A section image of magic keywords and hooks: floating neon sigils shaped like command tokens—"ralph", "ulw", "ralplan", "deepsearch", "ultrathink", "stopomc", "cancelomc"—hovering above a dark IDE. When a keyword is activated, it emits a pulse that triggers a specialized skill: a persistent loop, a parallel burst, a deep research scan, or a cancel shield. To the side, a Socratic interview panel shows question bubbles asking clarifying requirements before code generation, with a small ".omc/skills" folder and lifecycle hooks represented as glowing event pins. Dark mode, cyberpunk tech aesthetic, neon magenta, cyan, and yellow accents, ultra-detailed, 8K resolution.

The ecosystem

The author maintains an “oh-my-*” family and adjacent tooling. GitHub API figures, August 22, 2026: Yeachan-Heo/oh-my-codex — the same orchestration for the OpenAI Codex CLI, 32,800 stars; Yeachan-Heo/gajae-code — “Gajae Code MVP,” 2,551 stars; Yeachan-Heo/clawhip — a notification router, 929 stars; Yeachan-Heo/claw-code — 39 stars; Yeachan-Heo/rusty-claude-code — a Rust reimplementation, 26 stars.

Searching GitHub for “oh-my-claudecode” repositories returns about 91 results. The most notable non-mirror ones: witt3rd/oh-my-hermes — “Oh My Hermes (OMH),” multi-agent orchestration skills for Hermes Agent, “Inspired by oh-my-…”; 273 stars, the most visible unofficial port outside Claude/Codex; MeroZemory/oh-my-droid — orchestration for the Factory AI Droid CLI, 28 stars; dasomel/oh-my-cursor — orchestration rules for Cursor, 2 stars.

The README’s footer cites five inspirations: code-yeongyu/oh-my-opencode (today code-yeongyu/oh-my-openagent, 68,246 stars), affaan-m/everything-claude-code (today affaan-m/ECC, 242,166 stars), obra/superpowers (276,177 stars), jarrodwatts/claude-hud (27,560 stars), and Q00/ouroboros (5,623 stars). These are the author’s inspirations, not technical dependencies or affiliations.

A section image of the project ecosystem: a dark constellation map where the main repository is a bright central star labeled "OMC", connected to orbiting repository nodes such as "oh-my-codex", "gajae-code", "clawhip", "website", "rusty-claude-code", "zeroclaw", and "tokscale". Each node has a small glowing star-count badge, with the main star showing "38K" and the sibling "oh-my-codex" showing "32.8K". Branching satellites represent community ports to Hermes, Droid, Warp, and Cursor, drawn as smaller neon chips. The layout feels like a family tree of open-source tools. Dark mode, cyberpunk tech aesthetic, neon blue, pink, and amber accents, ultra-detailed, 8K resolution.

Official / semi-official status

OMC has no vendor backing in the recovered sources: there is no “standard” designation from Anthropic or any other provider. Its real status is:

  • A plugin distributed through Claude Code’s own plugin system, installed from a self-hosted marketplace in the repository itself. It’s installable from Anthropic’s official CLI plugin catalog, but the catalog is maintained by the project itself, not Anthropic.
  • A package published on npm (oh-my-claude-sisyphus), with automatic updates every 24 hours.
  • A de facto standard within a specific niche: teams-first multi-agent orchestration for Claude Code. How fast it grew (over 38,000 stars in ~7 months) and the appearance of ports to Hermes, Droid, Cursor, and Warp position it as the de facto reference for that pattern, though without any formal certification.

In practice, “official” here means installable from Claude Code’s plugin system, not endorsed by Anthropic.

Repo numbers

Measured: August 22, 2026, 23:59 UTC, GitHub API.

MetricValue
Stars38,737
Forks3,476
Real subscribers128
Open issues7
Commits (last pagination page)≈ 3,559
Primary languageTypeScript
LicenseMIT
CreatedJanuary 9, 2026
Last pushAugust 22, 2026
Latest releasev4.15.10, August 10, 2026
npm downloads (last month)23,867

watchers_count mirrors the star count, so subscribers_count (128) is reported separately as real viewers. Top contributors: Yeachan-Heo (2,619), shaun0927 (71), devseunggwan (22), hakilee (20), junhoyeo (15).

Quick-start guide

Installation and first run

Prerequisites: the Claude Code CLI installed and a Claude Max/Pro subscription or an Anthropic API key. Team workers also require tmux (macOS/Linux) or psmux (native Windows).

Via marketplace/plugin (recommended; the commands go one at a time):

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

Via npm:

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

Then setup: /setup, /omc-setup, or from the terminal omc setup.

Common workflows

  1. Build something end-to-end: /autopilot "build a REST API for managing tasks"; the 5-stage pipeline runs on its own.
  2. Vague requirement: /deep-interview "I want to build a task management app" launches the Socratic interrogation before writing code.
  3. Real parallel team: omc team 2:codex "review auth module for security issues" opens two tmux panes with Codex.
  4. Advice from another model: omc ask codex "review this patch" runs the provider’s local CLI and saves the artifact under .omc/artifacts/ask/.

Essential configuration

File / settingWhat it is
~/.config/claude-omc/config.jsoncUser (global) config, JSONC format
.claude/omc.jsoncProject config; takes priority over the user one
.omc/Runtime state root (sessions, plans, logs)
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSEnv var to enable native teams
OMC_STATE_DIRSo state survives worktree deletion

Common pitfalls and fixes

  • Installing both routes at once: the plugin and the npm CLI are separate paths; if you have both, update both.
  • MCP server name conflict (t): using --plugin-dir makes the plugin register its own t and collide; fix: {"disabledMcpjsonServers": ["t"]} in ~/.claude/settings.json.
  • swarm no longer exists: the keyword was removed; migrate old prompts to /team.
  • Native Windows: experimental; team workers need psmux or WSL2.

Integrations and migration

Optional external providers: Codex CLI, Gemini CLI, Antigravity (agy), Grok Build. Notifications via Telegram, Discord, Slack, and OpenClaw. docs/MIGRATION.md documents the v2.x → v3.0 and v3.x → v4.0 paths.

Contributing

CONTRIBUTING.md documents: prerequisites (Node.js ≥ 20, npm, git, Claude Code); forking and cloning with upstream; two main branches (dev for features, main for release); npm install && npm run build; linking the checkout as an active plugin via omc --plugin-dir "$PWD" setup --plugin-dir-mode; opening a PR with the template.

How the community received it

Hacker News — “Sisyphus Now Lives in Oh My Claude” (52 points, 38 comments, January 11, 2026) shows the full spectrum: gluszak asks whether these orchestrators “do anything besides burning more tokens”; CubsFan1060 says “the README seems more interested in being angry at Anthropic than telling me what this is”; John23832 warns against installing prompts from an account with no history and “silent auto-update”; LaurensBER points to a real speed advantage; undeveloper criticizes that “this removes the main advantage of opencode, easy access to many models.”

An independent article from ZHC Institute (April 1, 2026) reports that OMC reached 19,754 stars “in what looks like a week” and frames it as “the engineering arm of a Zero-Human Company,” noting that it doesn’t make business decisions or manage financial transactions.

oh-my-claudecode versus other proposals

ProjectVerifiable overlapVerifiable difference
code-yeongyu/oh-my-openagent (68,246 ★)Agent orchestration for a coding CLI; the directly cited inspiration.Aimed at OpenCode, not official Claude Code.
affaan-m/ECC (242,166 ★)A “harness” optimization system for Claude agents.Presents itself as performance optimization; OMC as teams-first multi-agent orchestration.
obra/superpowers (276,177 ★)A skills framework and development methodology for coding agents.Superpowers imposes a process; OMC orchestrates several agents in parallel with roles.
jarrodwatts/claude-hud (27,560 ★)Shows what’s happening in the statusbar.It’s just the HUD; OMC integrates that kind of visualization and adds full orchestration.
Yeachan-Heo/oh-my-codex (32,800 ★)Same orchestration, same author.For the OpenAI Codex CLI; OMC is the equivalent for Claude Code.

The most useful comparison isn’t by popularity: OMC stands out when you want teams-first multi-agent orchestration over official Claude Code, without deeply learning the CLI.

Use cases and who this repository can help

  • Developers already using Claude Code who want multi-agent orchestration without learning the CLI: the plugin + /autopilot flow gives a plan → prd → exec → verify → fix pipeline with a single command.
  • Teams wanting real parallelization with several models: omc team 2:codex ... + omc team 1:claude ... mixes Codex and Claude at once.
  • People with vague requirements: /deep-interview forces a Socratic interrogation before coding.
  • Multi-provider users: the same author offers oh-my-codex for Codex; tmux workers let you mix Claude, Codex, Gemini, Antigravity, Grok, and Cursor in a single team command.
  • Integration with broader agent pipelines: the OpenClaw integration positions it as “the engineering arm” inside a system coordinated by a higher-level agent.

Resources


Note: this article combines oh-my-claudecode’s README and official documentation, the GitHub API, the npm registry, repository searches, and Hacker News discussions, consulted on August 22, 2026. Figures change over time.

Comments