Install oh-my-claudecode in Claude Code

oh-my-claudecode, or OMC for short, is an open-source plugin for Claude Code that, according to the provider, promises multi-agent orchestration with zero learning curve. The project is maintained by Yeachan Heo as creator and lead and is available in the Yeachan-Heo/oh-my-claudecode GitHub repository under the MIT license, complemented by a dedicated documentation website. The core idea is to extend Claude Code with specialized subagents, intelligent model routing, and reusable skills, so that, per the project description, users do not first have to learn how Claude Code works in detail but can simply use OMC.

Installing via marketplace or npm

For most users, the provider recommends installing through the Claude Code plugin marketplace: first the marketplace is added using the repository path as a slash command inside Claude Code, then the actual plugin is installed. Both lines must be entered individually according to the instructions, since pasting both commands at once fails. Alternatively, an npm package called oh-my-claude-sisyphus is available for global installation, offering a standalone CLI runtime path. The provider notes a known, harmless npm warning about a deprecated dependency of a native SQLite extension that currently cannot be fixed without risking the installation itself.

Setup and first steps

After installation, setup runs either as a slash command inside an active Claude Code session or as a standalone terminal command. If OMC is launched through a custom plugin path rather than the regular marketplace mechanism, a plugin-directory mode must additionally be enabled, or a corresponding environment variable set, so that setup does not accidentally duplicate skills and agents the plugin already provides at runtime. Initial tasks can then be kicked off through an autopilot command that accepts a natural-language task description and automatically breaks it into planning, execution, and quality-assurance phases, optionally using named workflow profiles stored in a configuration file.

Orchestration, agents, and model routing

According to the provider, OMC ships nineteen specialized agents with different tiers for architecture, research, design, testing, and data analysis, and automatically routes tasks to the appropriate underlying model, for example a smaller, faster model for simple tasks and a more capable model for complex reasoning. A HUD status line shows real-time metrics about the ongoing orchestration, and a skill-learning mechanism extracts reusable patterns from past sessions, which are then automatically surfaced in the future whenever they match the current context.

Project and user skills plus state management

Custom skills learned from sessions can be stored either at the project level in a hidden folder inside the repository or at the user level in the home directory, with project-level skills taking priority over user-level ones and being shareable with a team when committed to the repository. According to the documentation, OMC writes runtime state, session data, plans, logs, and research notes into its own hidden folder; this is excluded from version control by default, with the explicit exception of the skills subfolder, which is deliberately meant to remain shareable. For several independent repositories sharing a common parent working directory, a marker file can be used to set up a shared state root.

Practical value and limitations

The practical value is that complex, multi-step coding tasks no longer need to be manually broken down into individual prompts but are automatically coordinated through an orchestration layer with matching specialist agents and model selection, which can save time especially on larger refactors or feature builds. The limitation is that OMC is a third-party extension built on top of Claude Code and assumes its base behavior and API access; anyone who does not understand the orchestration logic risks automatically selected agents or models not fitting their actual task, which is why the compatibility matrix from the documentation is worth checking before production use.