Our take
- Activity
- 90
- Community
- 62
- Issues
- 92
- Pull requests
- 82
+951 stars in the last 29 days
- Releases more often than 93% of the projects we track
- Merges more pull requests than 92% of the projects we track
- Closes issues faster than 81% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
40,588Forks
3,634Change since Nov 4, 2026: +42 stars·+4 forks
Overview
oh-my-claudecode (OMC) is a TypeScript toolkit for coordinating agents around Claude Code tasks. It addresses the overhead of manually splitting complex work, delegating it, and checking whether the result is complete by offering staged team workflows, autonomous execution modes, and verification loops.
It is most useful when a task benefits from parallel specialist work or persistent follow-through. OMC has distinct interfaces: slash-command skills run within a Claude Code session, while its terminal CLI can launch provider workers in tmux. It complements Claude Code rather than replacing it.
Key Features
- Team mode coordinates work through planning, execution, verification, and fix stages.
- Autopilot, Execute, and Verify provide different approaches to autonomous or repeat-until-verified work.
- Terminal
omc teamcan launch workers for supported provider CLIs in tmux panes. /askandomc askroute questions to supported local provider CLIs and save a Markdown artifact.- Specialized agents and model routing support delegation across task types.
- HUD, session summaries, replay logs, and cost tracking provide operational visibility.
- Custom skills can store reusable project- or user-level problem-solving guidance.
Use Cases
- A Claude Code user wants to split a feature across coordinated agents and verify the result before considering it done.
- A developer wants Codex, Gemini, Antigravity, Grok, Cursor, or Claude CLI workers to review or implement work through terminal-launched tmux sessions.
- A team wants reusable project-specific skills and shared orchestration conventions.
- An engineer wants to clarify an underspecified task before implementation using the deep interview workflow.
Getting Started
Install through the Claude Code plugin marketplace:
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode
/plugin install oh-my-claudecode
Then run /omc-setup in a Claude Code session. See the README for the npm installation path, configuration, and workflow details.
Alternatives
- CLI Agent Orchestrator: CAO runs multiple coding CLIs in isolated tmux sessions through a local server, rather than focusing on Claude Code skills and workers.
- Orkas: Orkas is a local-first desktop app for directing specialist agents and coding CLIs, rather than a Claude Code-centered orchestration toolkit.
- Clowder AI: Clowder emphasizes cross-model collaboration, persistent identity, and shared memory, rather than orchestrating work within Claude Code.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| oh-my-claudecode | TypeScript | MIT | 39.6k | Not checked yet |
| cli-agent-orchestrator | Python | Apache-2.0 | 1.4k | Active |
| Orkas | JavaScript | MIT | 2.1k | New |
| clowder-ai | TypeScript | MIT | 3.6k | Active |
Considerations
- Claude Code and a Claude Max/Pro subscription or Anthropic API key are required.
- Terminal team workers and rate-limit detection require tmux, plus the relevant provider CLI installed and authenticated.
- External AI providers are optional, but their workers depend on their own CLI and authentication setup.
- In-session skills require an active Claude Code session and are not a substitute for deterministic CLI commands in CI.
- Named autopilot stage profiles currently require Linux and the
flockutility. - OMC offers several orchestration modes and configuration options, so users seeking a minimal single-agent setup may find it more than they need.
Found this useful?
Share it with someone who would like oh-my-claudecode.