Practical overview
When it fits
Use it when a Claude Code project would benefit from team-based delegation, parallel execution or explicit planning-to-QA stages rather than a single-agent coding flow.
Who it is for
- Developers using Claude Code for software implementation.
- Teams or individual builders who want delegated, staged coding tasks.
- Engineers exploring multi-agent code review or parallel coding workflows.
Documented uses
- Coordinate multiple coding agents around one software project.
- Decompose and delegate implementation work.
- Run staged planning, execution and QA workflows through autopilot profiles.
- Create a structured foundation for parallel coding or review pipelines.
Requirements & limits
The repository is public and open source under the MIT license. The documented access paths are a Claude Code marketplace/plugin installation or an npm CLI/runtime installation.
- It is a framework/tool integrated with Claude Code, not a standalone hosted agent service.
- The implementation is TypeScript and the repository is published under the MIT license.
- Named autopilot profiles require Linux and the
flockutility. - The documented v1 profile sequences are limited to specific planning, execution, Ralph and QA combinations.
- Plugin-directory users need the documented setup mode or environment variable to avoid duplicating plugin-provided components.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and set up Oh My Claudecode
Install the Claude Code plugin or npm CLI path, then run the documented setup command.
Before you start
- Claude Code for the marketplace/plugin path.
- Node.js and npm for the npm CLI/runtime path.
- A project or user environment in which Claude Code and Oh My Claudecode can run.
Steps
In a Claude Code session, add the marketplace with
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode.Run
/plugin install oh-my-claudecodeas a separate command.Alternatively, install the npm CLI/runtime with the command below.
npm i -g oh-my-claude-sisyphus@latestRun
/omc-setupinside a Claude Code or OMC session, or runomc setupfrom a terminal.If using
--plugin-dir, apply the documented--plugin-dir-modesetup option or setOMC_PLUGIN_ROOTto avoid duplicating plugin-provided skills and agents.
Expected outcome
The documented Oh My Claudecode installation and setup stages are completed, leaving the environment ready for the next workflow step.
Guide limitations
- The npm installation may print a deprecated
prebuild-install@7.1.3warning from the upstreambetter-sqlite3dependency; the repository states that this warning does not by itself mean the installation failed. - This guide covers installation and setup, not a verified execution test.
Configure a named autopilot stage profile
Define a v1 autopilot profile for a documented planning, execution and QA sequence.
Before you start
- Oh My Claudecode installed and set up.
- A project
.claude/omc.jsoncor user~/.config/claude-omc/config.jsoncconfiguration file. - Linux with the
flockutility for named profile invocation.
Steps
Add a profile under
autopilot.workflowswithversion: 1and a supported stage sequence.Use one of the documented sequences:
ralplan, execution;ralplan, execution, ralph;ralplan, execution, qa; orralplan, execution, ralph, qa.Invoke the profile through
/autopilot --workflow.Use the project profile when the same name exists in both project and user configuration, because the project profile wholly replaces the user profile.
Expected outcome
A supported named autopilot workflow is configured for staged coding tasks.
Guide limitations
- Version 1 does not include model routing, inline execution, dynamic commands or arbitrary stages/plugins.
- Explicit named-profile invocation is rejected on unsupported environments before autopilot state is created or changed; legacy autopilot remains available.
- This guide documents configuration and invocation syntax rather than a completed workflow result.
Compare options for Agent orchestration
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Oh My Claudecode | Coordinate multiple coding agents around one software project. | CLI, Desktop | The repository is public and open source under the MIT license. The documented access paths are a Claude Code marketplace/plugin installation or an npm CLI/runtime installation. |
| Massgen | Run multiple AI agents against the same user task. | CLI | The repository documents installation through pip or uv and requires Python 3.11 or later. Setup can configure API keys for OpenAI, Anthropic, Google and xAI; credentials are needed for the selected model backends. |
| Langchain Multi Agents Boilerplate | Route incoming football questions to model and agent workflows according to task complexity. | Web | The repository is public and specifies an MIT license. Running the application requires OpenAI and Groq API keys and a Redis server. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- Yeachan-Heo/oh-my-claudecode · Official homepage title · retained in its source language

