Team-first multi-Agent orchestration tool (Claude Code ecosystem plugin form)

You do multi-agent collaboration inside Claude Code: one goal needs a plan, automatic execution, and several agents working in parallel — hand-writing prompts gets messy and tiring. omc (oh-my-claudecode) is an orchestration layer on top of Claude Code: /plan produces an execution plan, /autopilot executes a goal automatically, /team orchestrates a team. There are two install paths: the npm CLI (method B, verified in this environment) and the Claude Code plugin (method A, officially recommended but needs a logged-in environment, not verified here) — decide which one you want first, so you do not install the wrong form.

When to use it:

• You want plan/autopilot/team-style orchestration inside Claude Code sessions;
• You want the CLI management surface (launch/interop/ask/config);
• You want team-style multi-agent workflows.

When not to use it: single session, single task, no orchestration layer needed; or your environment is not Claude Code-based (in-session skills depend on method A plugin).

Boundary with adjacent tools: CLI form verified coexisting with agt/deepcode (local repro log); the Claude plugin form shares the .claude/ registration surface with ruflo (not tested, judged possible-conflict).

note: Method B npm CLI (verified here); must use the npmmirror registry on mainland networks

# Source: Trove detailed guide · verified 2026-08-28
npm i -g oh-my-claude-sisyphus@5.0.0 --no-audit --no-fund --registry=https://registry.npmmirror.com
omc --version

Expected output: 5.0.0

CLI form, three-step smoke:

# Source: Trove detailed guide · verified 2026-08-28
omc --version

Expected output: 5.0.0

# Source: Trove detailed guide · verified 2026-08-28
omc --help

Expected output: starts with Usage: omc [options] [command], includes launch/interop/ask/config

# Source: Trove detailed guide · verified 2026-08-28
omc config

Expected output: current config (JSON or init prompt)

• CLI installed: version/help/config all run (verified 2026-08-27);
• Plugin form (method A): /plugin list shows oh-my-claudecode, /plan can be invoked (needs a logged-in environment, not tested).

Two forms, different mechanisms:

• Method B (npm CLI): global command omc (verified here), command surface launch / interop / ask / config — pure CLI management;
• Method A (Claude Code plugin): officially recommended; after /plugin install you get in-session skills /plan, /autopilot, /team — orchestration lives in the session, mounted through the Claude Code plugin registration surface (~/.claude.json etc.).

Key concepts:

• /plan: goal → execution plan;
• /autopilot: goal → automatic execution;
• /team: team orchestration mode.

Where it writes: method B writes the npm global directory; method A writes the Claude Code plugin registration surface (~/.claude.json etc.).

Measured command = npm global install (npmmirror, verified in this environment 2026-08-27); outside China / with direct connectivity you can drop the --registry parameter (see the region branch in the guide install section); the Claude Code plugin path is in guide method A

Step 1: Install the CLI (method B)

Why: global npm install of oh-my-claude-sisyphus (command name omc). Mainland npm official registry times out on direct connections; the verified command carries the npmmirror registry; on overseas direct networks drop the registry parameter.

# Source: Trove detailed guide · verified 2026-08-28
npm i -g oh-my-claude-sisyphus@5.0.0 --no-audit --no-fund --registry=https://registry.npmmirror.com
omc --version

Expected output: 5.0.0

Overseas / direct-network branch:

# Source: Trove detailed guide · verified 2026-08-28
npm i -g oh-my-claude-sisyphus@5.0.0 --no-audit --no-fund
omc --version

Expected output: 5.0.0

After install, confirm:

• omc --version prints 5.0.0;
• omc --help shows launch/interop/ask/config commands.

Stuck? How to recover:

• npm slow/timeout → make sure the command has --registry=https://registry.npmmirror.com;
• node version → confirm >= 20;
• command not found → check that the npm global bin is on PATH.

Step 2: Check config (CLI surface)

Why: omc config shows the current config (JSON or an init prompt). Get the CLI surface working first; install in-session skills (method A) later as needed.

# Source: Trove detailed guide · verified 2026-08-28
omc config

Expected output: current config (JSON or init prompt)

After install, confirm:

• config output or init prompt appears with no error.

Stuck? How to recover:

• config error → follow the init prompt, or check the environment.

Step 3: In-session orchestration skills (method A, officially recommended)

Why: method A installs the Claude Code plugin for in-session /plan /autopilot /team. Commands from the official docs; not verified in this environment (Claude Code not logged in).

# Source: Trove detailed guide · verified 2026-08-28
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode
/plugin install oh-my-claudecode
/omc-setup

Expected output: oh-my-claudecode appears in the plugin list; omc-setup completes initialization

After install, confirm:

• oh-my-claudecode appears in the plugin list;
• /plan and friends can be invoked.

Stuck? How to recover:

• plugin won't install → confirm Claude Code login and plugin marketplace reachability.

Same source as the tool-page matrix — 19 pairs total (1 measured compatible / 12 inferred possibly compatible / 6 inferred possibly conflicting); full pairs, states and evidence: Conflict pairs (co-install matrix).

• Symptom: command not found (omc: command not found)
• Symptom: hooks not executing (hook not triggered / Windows hook error)
• Symptom: agents not auto-delegated (tasks not distributed)
• Symptom: update/config anomalies (omc-doctor diagnostics)
• Symptom: package name / plugin name / command name mismatch
• Symptom: Claude Code environment errors (OOM / Homebrew conflict / PowerShell execution policy)

Full four-section text (symptom→cause→fix→verification evidence): site docs

# Source: Trove detailed guide · verified 2026-08-28
npm rm -g oh-my-claude-sisyphus || true

note: Match install exactly: method B uninstalls via npm; method A runs /plugin remove inside Claude Code; the last line verifies zero residue

# Source: Trove detailed guide · verified 2026-08-28
npm rm -g oh-my-claude-sisyphus || true
command -v omc >/dev/null 2>&1 && echo "omc 仍存在（方式 A 安装请执行 /plugin remove oh-my-claudecode）" || echo "omc removed: OK"

Expected output: omc removed: OK

• Runtime preflight (needs node >= 20; pass = output contains the system architecture and node version)
• Pick either of two real install paths (B = npm CLI, measured passing here; A = Claude Code plugin marketplace, officially recommended but not measured here); the last step is the verification command
• Each operation = one command block + expected output; in-session skills need method A installed to be usable
• Uninstall matches install: B uninstall with npm; A uninstall with /plugin remove inside Claude Code; the last line verifies zero residue

• Q: omc command not found after install? A: check node >= 20 and the npm global bin path; on mainland networks use the method B domestic branch command from the install section.
• Q: Any residue after uninstall? A: after npm uninstall, if the verification command prints "omc removed: OK" there is zero residue; the Claude Code plugin form additionally needs /plugin remove.
• Q: In-session skills (/plan etc.) unavailable? A: in-session skills need method A (Claude Code plugin); the CLI form does not carry in-session skills.
• Q: Where to report problems? A: install/uninstall issues on this marketplace go through the entry feedback channel (usage-report template); project issues go to the author's repository.

• Version: [5.0.0, 5.0.0] locked (verified at collection).
• Environment: Node >= 20 (CLI form); method A needs a logged-in Claude Code environment.
• Network: npm official registry times out on direct connections (verified); must use the npmmirror registry.
• Write surface: method B npm global; method A Claude Code plugin registration surface.
• Co-install: CLI form verified coexisting with agt/deepcode (local repro log); plugin form with ruflo shares .claude/ and ~/.claude/CLAUDE.md, not tested, judged possible-conflict.

• Verified: local repro log (2026-08-27, npm install + version/help/config smoke); local repro log (coexistence with agt/deepcode at CLI layer).
• Not tested: method A Claude Code plugin and in-session skills (not logged in) — commands from the official docs, marked accordingly.