Quick fix
# One-liner: use the npm package name for install/uninstall, omc for daily use
npm i -g oh-my-claude-sisyphus && omc --version
What you will run into
Searching npm for the plugin name "oh-my-claudecode" finds nothing; when uninstalling you don't know the package name. Names don't line up — can't install, and don't know what to uninstall.
Why this happens
Three names don't match:
| Name | Purpose |
|---|---|
oh-my-claude-sisyphus | npm package name (install/uninstall) |
oh-my-claudecode | Claude Code plugin name (plugin operations) |
omc | CLI command (day-to-day) |
This is not "messy naming" — it is one name per layer, each with its own constraints: the npm package name must be globally unique and not collide with existing packages, so the project picked the longer oh-my-claude-sisyphus (also reflecting its Sisyphus-workflow inspiration);
the Claude Code plugin name faces users in the plugin marketplace and is oh-my-claudecode; the CLI command name must be short to type, hence omc.
The three names serve three scenarios and there is no automatic mapping between them — npm only knows the package name, Claude Code only knows the plugin directory name, and the shell only knows the command name.
That is why searching npm for the plugin name naturally finds nothing: you searched the wrong layer. Mnemonic: install/uninstall = package name, plugin operations = plugin name, daily commands = omc.
Step by step
1. Use the npm package name to install/uninstall — Required
npm i -g oh-my-claude-sisyphus
Uninstall: npm rm -g oh-my-claude-sisyphus.
2. Use omc for daily commands — Required
omc --version
3. Use the plugin name inside Claude Code — Required
Plugin operations inside Claude Code use oh-my-claudecode.
How to confirm it works
Version command works (measured output shape):
omc --version
→ 5.0.0 (manifest closure log step 1)Other environments
| Environment | Notes |
|---|---|
| npm package name | oh-my-claude-sisyphus (recorded at L33) |
| Plugin name | oh-my-claudecode |
| CLI command | omc |
| Windows / macOS | Same name mapping |
Symptom
Searching npm for "oh-my-claudecode" finds nothing to install; the package name is unknown when uninstalling.
Cause
Three different names exist: npm package = oh-my-claude-sisyphus, Claude Code plugin = oh-my-claudecode, CLI command = omc.
Solution
- Install/uninstall using the npm package name:
npm i -g oh-my-claude-sisyphus/npm rm -g oh-my-claude-sisyphus. - Use the
omccommand for daily use; inside Claude Code useoh-my-claudecodefor plugin operations.
Verification Evidence
- L33 record: package name and plugin name differ (oh-my-claude-sisyphus vs omc).
- Verified in this marketplace: manifest install.cmd uses the npm package name +
omc --versionverification (closed-loop log step 1: 5.0.0).
Applicable tools (1)
This problem is linked from the tool pages below — reachable from either side.
oh-my-claudecodeSource & evidence
← Multi-Agent Orchestration domain | Problem Catalog Experience | Facing another issue? Go to the Helpdesk