Problem: omc not found after install (or /omc-setup didn't produce a working CLI) —— Trove problem library

What you will run into

After install, omc reports command not found; or after /omc-setup the CLI is still unusable. Installed but the command can't be found — three common causes, check in the order below.

Why this happens

"Command not found" is essentially a shell resolution chain problem: you type omc, the shell searches the PATH env var for an executable, and if none of the paths match, it reports command not found.

The three common causes map to three different break points: wrong install form — OMC has two forms (Claude Code plugin vs npm CLI); the plugin form doesn't create an omc command at all, only /omc-setup generates the CLI entry (break point: the command simply doesn't exist);

installed somewhere else — the npm global bin dir ($(npm prefix -g)/bin) isn't on PATH, so the command exists but the shell can't find it (break point: the search path);

half-finished install — the install failed midway and the bin link was never created (break point: install completeness).

The diagnostic order is fixed: npm ls -g first (is the package there? rules out "never installed") -> rerun setup or reinstall (fill in the missing piece) -> command -v omc last (confirm the resolution chain).

Pass all three layers and the command must be there.

Step by step

1. Confirm the install — Required

npm ls -g oh-my-claude-sisyphus

2. Rerun /omc-setup (plugin form) or reinstall the CLI — Required

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

Domestically add --registry=https://registry.npmmirror.com.

3. Check PATH — Required

command -v omc

With a custom npm prefix, add $(npm prefix -g)/bin to PATH.

How to confirm it works

Command surface in place (measured output shape):

command -v omc
→ /usr/local/bin/omc (measured under isolated HOME)

omc --version prints the version normally.

Other environments

Symptom

After install, omc reports command not found; or the CLI is still unusable after /omc-setup.

Cause

1. npm global bin dir is not on PATH (custom npm prefix scenario);
2. Installed the Claude Code plugin form without running /omc-setup to generate the CLI entry;
3. Install failed mid-way (network/deps).

Solution

1. Confirm the install: npm ls -g oh-my-claude-sisyphus.
2. Re-run /omc-setup (Claude Code plugin form); or reinstall the CLI: npm i -g oh-my-claude-sisyphus@5.0.0 (add --registry=https://registry.npmmirror.com in China).
3. PATH check: command -v omc; with a custom npm prefix add $(npm prefix -g)/bin to PATH.