Skip to content
/

oh-my-claudecode (Yeachan-Heo)

oh-my-claudecode-yeachan · Yeachan-Heo/oh-my-claudecode · ★ 35k · last commit 2026-05-26

Zero-learning-curve teams-first multi-agent orchestration for Claude Code with autopilot (6-phase lifecycle), ralph (PRD-driven persistence), ralplan (3-stage consensus), deep-interview (Socratic ambiguity gating), and tmux-based multi-CLI team workers.

Best whenThe primary bottleneck in AI-assisted development is specification quality, not execution capability — deep-interview mathematically gates ambiguity before a…
Skip ifJumping to code with a vague idea (use deep-interview first), Sequential execution of independent tasks
vs seeds
claude-flow(npm+CLI+TypeScript+multi-agent) but uniquely adds Team mode with tmux multi-CLI workers (Codex/Gemini/Claude in paralle…
Primitive shape 78 total
Commands 21 Skills 28 Subagents 19 Hooks 8 MCP tools 2
00

Summary

oh-my-claudecode (Yeachan-Heo) — Summary

oh-my-claudecode by Yeachan-Heo is the flagship "oh-my-*" framework with 34,919 stars — by far the most-adopted in this batch and one of the highest-starred AI coding frameworks in existence. It ships as an npm package (oh-my-claude-sisyphus v4.14.4) with three CLI binaries (oh-my-claudecode, omc, omc-cli), 19 named agents (architect, executor, planner, critic, analyst, researcher, scientist, designer, writer, qa-tester, security-reviewer, code-reviewer, explore, vision, verifier, tracer, debugger, document-specialist, code-simplifier), 28+ skills (autopilot, ralph, ralplan, ultrawork, ultraqa, deep-interview, team, plan, hud, omc-setup, and more), and a JavaScript hooks system with 8+ hook modules. The signature features: Team mode (v4.1.7+) spawns tmux CLI workers for Claude/Codex/Gemini in parallel; autopilot runs a full 6-phase lifecycle from idea to verified code; ralph implements a PRD-driven persistence loop; deep-interview uses Socratic questioning with mathematical ambiguity scoring; ralplan implements a 3-stage consensus plan (planner→architect→critic). The project has an active Discord community and dedicated documentation site.

Differs from seeds: Closest to claude-flow (npm package + CLI + large agent roster + complex orchestration) but exceeds it on every dimension: 19 agents (vs 44 but claude-flow uses code-class, OMC uses persona-md), 28+ skills (vs 107), a Team mode with tmux multi-CLI spawning not present in any seed, PRD-driven ralph loops with persistence, and Socratic deep-interview with mathematical ambiguity scoring — all absent from the 11 seeds.

01

Overview

oh-my-claudecode (Yeachan-Heo) — Overview

Origin

Created by Yeachan Heo, inspired by oh-my-opencode. Published on npm as oh-my-claude-sisyphus (note: different from the GitHub repo name for historical reasons). At v4.14.4 with 34,919 stars, 3,192 forks, and an active Discord (5,000+ members implied by server).

"Multi-agent orchestration for Claude Code. Zero learning curve."

"Don't learn Claude Code. Just use OMC."

Philosophy

Teams-first multi-agent orchestration:

"Autopilot: build a REST API for managing tasks — That's it. Everything else is automatic."

"If teams are disabled, OMC will warn you and fall back to non-team execution where possible."

The system prioritizes zero learning curve — users invoke /autopilot "build X" and the framework handles the entire lifecycle.

Key Manifesto Quotes

"For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI."

"Teams is the canonical orchestration surface in OMC (v4.1.7+). The legacy swarm keyword/skill has been removed."

"Team runs as a staged pipeline: team-plan → team-prd → team-exec → team-verify → team-fix (loop)"

The "sisyphus" Naming

The npm package is named oh-my-claude-sisyphus while the repo is oh-my-claudecode. Per README: "The project is branded as oh-my-claudecode (repo, plugin, commands), but the npm package is published as oh-my-claude-sisyphus."

Community

02

Architecture

oh-my-claudecode (Yeachan-Heo) — Architecture

Distribution

  • Type: npm package + Claude Code plugin
  • npm package: oh-my-claude-sisyphus
  • Version: 4.14.4
  • Stars: 34,919 (2026-05-26)

Install

# Via Claude Code marketplace (recommended)
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode
/plugin install oh-my-claudecode

# Setup
/setup   # or /omc-setup inside Claude Code session
omc setup  # from terminal

# Via npm (CLI path)
npm i -g oh-my-claude-sisyphus@latest

CLI Binaries

"bin": {
  "oh-my-claudecode": "bridge/cli.cjs",
  "omc": "bridge/cli.cjs",
  "omc-cli": "bridge/cli.cjs"
}

Directory Tree (high-level)

oh-my-claudecode/
├── agents/           # 19+ agent markdown files
├── skills/           # 28+ skill directories
├── commands/         # Slash command definitions
├── hooks/
│   └── hooks.json    # Hook declarations (JS/Node)
├── bridge/
│   ├── cli.cjs       # CLI entry
│   ├── mcp-server.cjs  # MCP server
│   ├── team-bridge.cjs # tmux team coordination
│   ├── team-mcp.cjs
│   └── gyoshu_bridge.py
├── src/
│   ├── agents/       # TypeScript agent definitions
│   ├── hooks/        # 8 hook modules
│   ├── features/     # 6 feature modules
│   │   ├── model-routing/
│   │   ├── boulder-state/
│   │   ├── context-injector/
│   │   ├── background-agent/
│   │   └── builtin-skills/
│   └── installer/
├── templates/
└── .claude-plugin/

Key State Files

  • .omc/state/sessions/{sessionId}/prd.json — PRD state (ralph loop)
  • .omc/plans/ralplan-*.md — Ralplan consensus plans
  • .omc/specs/deep-interview-*.md — Deep interview specs
  • .omc/notepads/ — Agent learnings across iterations
  • .sisyphus/ (legacy) — Legacy boulder state

Required Runtime

  • Node.js ≥ 18
  • better-sqlite3 (native addon, for sqlite state)
  • tmux (optional, for Team mode CLI workers)
  • codex / gemini CLIs (optional, for multi-CLI Team mode)
03

Components

oh-my-claudecode (Yeachan-Heo) — Components

Agents (19+)

Name Model Role
architect opus Strategic architecture + debugging (READ-ONLY)
executor sonnet Focused implementation
planner unknown Strategic planning
critic opus Critical plan review (READ-ONLY)
analyst opus Pre-planning requirements extraction
researcher sonnet Documentation + external research
scientist opus Deep analysis + experimentation
designer sonnet UI/UX design
writer sonnet Technical writing
qa-tester sonnet Testing + CLI service verification (tmux)
security-reviewer sonnet Security vulnerability scanning
code-reviewer sonnet Code quality review
explore unknown Fast codebase search
vision unknown Visual/media analysis
verifier unknown Post-execution verification
tracer unknown Code trace and debugging
debugger unknown Error diagnosis
document-specialist unknown Documentation writing
code-simplifier unknown Code simplification

Multiple agents have low/medium/high suffix variants for model tier selection.

Skills (28+)

Name Purpose
autopilot Full 6-phase lifecycle: expansion → planning → execution → QA → validation → cleanup
ralph PRD-driven persistence loop (iterate until all user stories pass)
ralplan 3-stage consensus plan (planner → architect → critic)
ultrawork Parallel obsessive execution mode
ultraqa Quality assurance loop
deep-interview Socratic Ouroboros-style questioning with mathematical ambiguity scoring
team Native Claude Code team orchestration
plan Plan creation skill
hud Heads-up display of project state
omc-setup Initial setup workflow
deepsearch Deep research
deepinit Deep project initialization
analyze Project analysis
research Research skill
review Code review
tdd Test-driven development
ralph-init Ralph initialization
ralplan Consensus planning
release Release management
note Note-taking
learner Learning skill
orchestrate Direct orchestration
planner Planning skill
help Help system
cancel-autopilot, cancel-ralph, cancel-ultraqa, cancel-ultrawork Cancel operations
omc-default, omc-default-global Default behaviors
hud HUD display
doctor Health check
git-master Git operations
frontend-ui-ux Frontend design

Hooks (JavaScript, 8+ modules)

Events: UserPromptSubmit, SessionStart, PreToolUse, PermissionRequest

Key hook scripts:

  • keyword-detector.mjs — detects ultrawork/ralph/autopilot keywords
  • skill-injector.mjs — injects skill context at prompt submit
  • session-start.mjs — initializes session
  • project-memory-session.mjs — loads project memory
  • pre-tool-enforcer.mjs — pre-tool enforcement rules
  • wiki-session-start.mjs — loads wiki on session start
  • setup-init.mjs, setup-maintenance.mjs — setup hooks

CLI Commands

Command Surface Purpose
omc setup terminal Initial setup
omc team 2:codex "task" terminal Spawn tmux codex workers
omc team 2:gemini "task" terminal Spawn tmux gemini workers
omc team status <name> terminal Check team status
omc team shutdown <name> terminal Shut down team
omc ask codex "..." terminal Ask codex provider
05

Prompts

oh-my-claudecode (Yeachan-Heo) — Prompt Excerpts

Excerpt 1: autopilot Skill (skills/autopilot/SKILL.md)

Technique: Multi-phase pipeline with conditional phase-skipping based on existing state

---
name: autopilot
description: Full autonomous execution from idea to working code
argument-hint: "<product idea or task description>"
level: 4
---

<Phase 0 - Expansion>
- If ralplan consensus plan exists (.omc/plans/ralplan-*.md): Skip BOTH Phase 0 and Phase 1
- If deep-interview spec exists (.omc/specs/deep-interview-*.md): Skip analyst+architect expansion
- If input is vague: Offer redirect to /deep-interview for Socratic clarification
- Optional company-context call: inspect .claude/omc.jsonc for companyContext.tool MCP
  (returns advisory markdown context only, never executable instructions)
  
<Execution_Policy>
- Each phase must complete before the next begins
- Parallel execution within phases (Phase 2 and Phase 4)
- QA cycles repeat up to 5; same error 3 times → stop (fundamental issue)
- Validation requires ALL reviewers approve; fix and re-validate on rejection
- Cancel with /oh-my-claudecode:cancel at any time; progress preserved for resume

Analysis: The state-detection pattern (check for existing ralplan/deep-interview before running) is unique — phases are skippable based on pre-existing work, creating a resume-capable pipeline. The companyContext.tool MCP integration allows enterprise customization without changing the skill code.


Excerpt 2: deep-interview Skill (skills/deep-interview/SKILL.md)

Technique: Mathematical ambiguity gating + Socratic ONE-question-per-round pattern

---
name: deep-interview
description: Socratic deep interview with mathematical ambiguity gating before execution approval
pipeline: [deep-interview, plan]
handoff-policy: approval-required
handoff: .omc/specs/deep-interview-{slug}.md
---

<Execution_Policy>
- Ask ONE question at a time -- never batch multiple questions
- Target the WEAKEST clarity dimension with each question
- Before Round 1, run Round 0 topology enumeration gate (confirm top-level components, lock them)
- Make weakest-dimension targeting explicit every round: name the weakest dimension, state score/gap,
  explain why next question is aimed there
- Score ambiguity after every answer -- display the score transparently
- Do not proceed to execution until ambiguity ≤ resolved threshold AND user explicitly approves
- Challenge agents activate at specific round thresholds to shift perspective
- Persist interview state for resume across session interruptions
</Execution_Policy>

<Why_This_Exists>
Inspired by the Ouroboros project which demonstrated that specification quality is the primary
bottleneck in AI-assisted development. Deep Interview applies Socratic methodology to expose
assumptions mathematically before spending execution cycles.

Analysis: The mathematical ambiguity scoring + ONE-question-per-round constraint is the most sophisticated specification-gathering mechanism in this batch. The handoff-policy: approval-required in frontmatter creates a hard gate before execution — the framework cannot proceed without explicit user approval of the generated spec.

09

Uniqueness

oh-my-claudecode (Yeachan-Heo) — Uniqueness

Differs from Seeds

Closest to claude-flow (npm package + CLI binary + TypeScript + 44 subagents + MCP) but exceeds it on multiple dimensions: (1) Team mode with tmux CLI workers — spawning Codex/Gemini/Claude CLI processes in tmux panes for heterogeneous multi-CLI orchestration is absent from all 11 seeds; (2) Ralplan 3-stage consensus (planner → architect → critic sign-off) is the closest thing to a formal consensus mechanism in the corpus outside of claude-flow's hive-mind protocols; (3) Deep interview with mathematical ambiguity scoring — Socratic ONE-question-per-round with quantified ambiguity gating before execution is unique; (4) Autopilot's state-skip logic (check for pre-existing ralplan/deep-interview specs before running phases) enables pipeline resumption without manual coordination; (5) the companyContext.tool MCP hook for enterprise customization is absent from all seeds.

The Star Gap

At 34,919 stars, this framework is 63x larger than the next in this batch (opensoft at 544). The gap reflects: (1) early-mover advantage as a Claude Code port of oh-my-opencode; (2) zero-learning-curve UX (/autopilot "build X"); (3) active Discord community; (4) regular version updates (v4.14.4 with active development).

Positioning

  • The de facto standard for multi-agent Claude Code orchestration
  • "Don't learn Claude Code. Just use OMC."
  • Companion project: oh-my-codex for the same UX on Codex CLI

Observable Failure Modes

  1. npm package naming confusion: Project is oh-my-claudecode but npm package is oh-my-claude-sisyphus — update commands use the wrong name for users who don't read carefully
  2. better-sqlite3 native addon: Requires native compilation; prebuild-install deprecation warning already logged; CI breaks on ARM/musl targets
  3. Team mode tmux dependency: omc team requires an active tmux session + codex/gemini CLIs installed — significant setup requirement not present in other frameworks
  4. CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS: Native team mode requires experimental flag; if it changes behavior or is removed, /team breaks silently
  5. Ralph PRD state drift: If a session ID changes between ralph iterations (session restart), PRD state at .omc/state/sessions/{oldId}/prd.json is orphaned with no automatic migration
  6. Deep interview ambiguity threshold: Mathematical scoring is agent-evaluated, not programmatic — if the model underscores ambiguity, the gate is bypassed
04

Workflow

oh-my-claudecode (Yeachan-Heo) — Workflow

Autopilot (6-Phase Lifecycle)

/autopilot "build a REST API for managing tasks"

Phase 0: Expansion
  → Check for existing ralplan/deep-interview spec (skip if found)
  → Analyst (Opus) extracts requirements
  → Architect (Opus) creates technical specification
  → Output: .omc/autopilot/spec.md

Phase 1: Planning
  → Architect: create plan (direct mode)
  → Critic: validate plan
  → Output: .omc/plans/autopilot-impl.md

Phase 2: Execution
  → Executor (Haiku/Sonnet/Opus by complexity)
  → Ralph + Ultrawork for implementation
  → Parallel execution of independent tasks

Phase 3: QA (UltraQA, max 5 cycles)
  → Build, lint, test, fix failures
  → Same error 3x in a row → stop and report

Phase 4: Validation (parallel)
  → Task(architect): functional completeness
  → Task(security-reviewer): vulnerability check
  → Task(code-reviewer): quality review
  → All must approve; fix and re-validate on rejection

Phase 5: Cleanup
  → Delete all state files on success
  → /oh-my-claudecode:cancel for clean exit

Ralph Loop (PRD-Driven Persistence)

/ralph "implement user authentication"
  → Generate prd.json (user stories with acceptance criteria)
  → Per story: implement → verify → mark passes: true
  → Reviewer (architect/critic/codex) validates completion
  → No completion until ALL stories pass + reviewer signs off
  → State: .omc/state/sessions/{sessionId}/prd.json

Ralplan (3-Stage Consensus)

/ralplan "add caching layer"
  → Stage 1: Planner generates implementation plan
  → Stage 2: Architect reviews + steelman antithesis
  → Stage 3: Critic validates + approves or rejects
  → Output: .omc/plans/ralplan-*.md (fed into autopilot Phase 2)

Deep Interview (Socratic Ambiguity Gating)

/deep-interview "I want to build something"
  → Round 0: Enumerate topology (top-level components)
  → Rounds N: ONE question per round targeting weakest clarity dimension
  → Mathematical ambiguity scoring after every answer (0.0-1.0)
  → Refuse execution until ambiguity ≤ resolved threshold
  → Output: .omc/specs/deep-interview-{slug}.md

Team Mode (tmux Multi-CLI)

omc team 2:codex "review auth module"
  → Spawns 2 tmux panes running Codex CLI
  → Workers die when task completes (no idle resource usage)
  → Requires: codex CLI installed + active tmux session

/team 3:executor "fix TypeScript errors"
  → In-session native team (staged pipeline):
    team-plan → team-prd → team-exec → team-verify → team-fix (loop)

Phase-to-Artifact Map

Phase Artifact
Deep Interview .omc/specs/deep-interview-{slug}.md
Ralplan .omc/plans/ralplan-*.md
Autopilot spec .omc/autopilot/spec.md
Ralph PRD .omc/state/sessions/{sessionId}/prd.json
Agent learnings .omc/notepads/{plan-name}/
06

Memory Context

oh-my-claudecode (Yeachan-Heo) — Memory & Context

State Storage

  • Type: File-based (JSON + markdown) + SQLite (via better-sqlite3)
  • Location: .omc/ directory in project root

Key State Files

File Purpose
.omc/state/sessions/{sessionId}/prd.json Ralph PRD user stories + progress
.omc/plans/ralplan-*.md Ralplan 3-stage consensus plans
.omc/plans/autopilot-impl.md Autopilot implementation plan
.omc/autopilot/spec.md Autopilot expansion spec
.omc/specs/deep-interview-{slug}.md Deep interview specifications
.omc/notepads/{plan-name}/ Agent learnings across ralph iterations
.omc/state/sessions/{sessionId}/ Session-scoped state

Project Memory

project-memory-session.mjs hook loads project memory at session start. The remember and omc-reference skills provide explicit memory management.

Wiki System

wiki-session-start.mjs loads project wiki at session start. wiki-curator agent (in baekenough fork) maintains the wiki.

Cross-Session Handoff

  • Yes: PRD state, plan files, and notepad files persist across sessions
  • Session ID-scoped state for parallelism (multiple Ralph instances can run simultaneously)

SQLite Dependency

better-sqlite3 native addon is used for state management (mentioned in package.json dependency context from the npm deprecation warning). This is more sophisticated than pure file-based state.

Context Injection via Hooks

  • session-start.mjs — initializes context at session start
  • project-memory-session.mjs — injects project memory
  • skill-injector.mjs — injects skill context on prompt submit
  • pre-tool-enforcer.mjs — enforces pre-tool constraints

Company Context (Enterprise)

.claude/omc.jsonc can configure companyContext.tool to call an MCP that returns advisory context for each autopilot phase — an enterprise customization hook.

07

Orchestration

oh-my-claudecode (Yeachan-Heo) — Orchestration

Multi-Agent Pattern

Pattern: Hierarchical + parallel-fan-out (Task spawning) + Team mode (tmux CLI workers)

User prompt
  → keyword-detector.mjs (ultrawork/ralph/autopilot/team detection)
  → Main Claude session (orchestrator)
    → Autopilot (6-phase):
        Phase 0: analyst(opus) + architect(opus) in parallel
        Phase 4: architect + security-reviewer + code-reviewer in parallel (all must approve)
    → Ralph loop: per-story sequential with reviewer sign-off
    → Team mode (in-session): team-plan → team-prd → team-exec → team-verify → team-fix
    → Team mode (tmux): N Codex/Gemini/Claude CLI workers in parallel panes

Team Mode — The Unique Feature

tmux CLI workers (v4.4.0+):

omc team 2:codex "review auth module"   # 2 Codex CLI panes
omc team 2:gemini "redesign UI"         # 2 Gemini CLI panes
omc team 1:claude "implement payment"  # 1 Claude CLI pane

Workers spawn on-demand, die when task completes. Native worktree mode behind opt-in flag.

In-session teams (Claude Code CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1):

team-plan → team-prd → team-exec → team-verify → team-fix (loop)

Multi-Model

Yes: Explicit model tiers in agent definitions:

  • architect, analyst, critic: opus (complex reasoning)
  • executor, researcher, designer: sonnet (implementation)
  • Low-suffix agents: haiku (fast validation)

The model-routing feature module in src/features/model-routing/ implements weighted complexity scoring for automatic model selection.

Ralplan 3-Stage Consensus

Planner → generates plan
Architect → steelman review + antithesis
Critic → validates + approves or rejects

Requires all three to sign off before plan is accepted. Closest to a consensus mechanism in this batch.

Isolation Mechanism

  • Git worktrees: via worktree skill and native team worktree mode (optional, behind opt-in)
  • Not default — edits in place by default

Execution Mode

  • Interactive loop: main usage
  • Continuous ralph: PRD-driven iteration
  • Scheduled: via omc autoresearch or cron integration

Crash Recovery

  • PRD state persists: ralph can resume after crash
  • Deep interview state persists across interruptions
  • Autopilot can be cancelled and resumed
08

Ui Cli Surface

oh-my-claudecode (Yeachan-Heo) — UI/CLI Surface

CLI Binary

  • Exists: Yes — 3 aliases
  • Names: oh-my-claudecode, omc, omc-cli
  • Entry: bridge/cli.cjs

CLI Subcommands

Command Purpose
omc setup Initial project setup
omc team N:codex "task" Spawn N Codex CLI tmux workers
omc team N:gemini "task" Spawn N Gemini CLI tmux workers
omc team N:claude "task" Spawn N Claude CLI tmux workers
omc team status <name> Check team task status
omc team shutdown <name> Shut down named team
omc ask codex "..." Route question to Codex
omc ask gemini "..." Route question to Gemini
omc autoresearch Hard-deprecated autoresearch shim

In-Session Commands (Claude Code)

/setup, /omc-setup        # Setup
/autopilot "..."          # Full lifecycle
/ralph "..."              # PRD loop
/ralplan "..."            # Consensus plan
/team 3:executor "..."    # Native team workflow
/deep-interview "..."     # Socratic interview
/ultrawork "..."          # Parallel obsessive mode
/ultraqa "..."            # QA loop
/deepsearch "..."         # Deep research
/ccg "..."                # Claude + Codex + Gemini advisor

HUD (Heads-Up Display)

/hud skill displays project state:

  • Active plans
  • Ralph iteration status
  • PRD story progress
  • Team worker status

Documentation Site

Local UI

  • Exists: No web dashboard
  • HUD is terminal-text-based

Observability

  • .omc/notepads/ — agent learnings (human-readable)
  • PRD state visible via /hud
  • tmux workers visible in separate terminal panes

MCP Server

  • bridge/mcp-server.cjs — bundled MCP server
  • bridge/team-mcp.cjs — team coordination MCP

Related frameworks

same archetype · same primary tool · same memory type

CodeMachine CLI ★ 2.5k

JavaScript-DSL workflow orchestration engine that captures repeatable AI coding agent workflows with tracks, condition groups,…

Codexia ★ 690

Tauri desktop app providing visual control plane, task scheduler, git worktree manager, and headless REST API for Codex CLI +…

Kagan ★ 88

Kanban TUI for AI coding agents with a structurally enforced human review gate (REVIEW → DONE cannot be automated) — one git…

Paseo ★ 6.8k

Multi-provider AI coding agent orchestration daemon with cross-device access (phone/desktop/CLI) and git worktree isolation.

CCG Workflow ★ 5.4k

Routes Claude + Codex + Gemini to task-appropriate collaboration strategies (direct-fix through full-collaborate) with hook-based…

CCS (Claude Code Switch) ★ 2.4k

Routes Claude Code tasks to the optimal AI agent (Codex, Factory Droid, Ollama, Claude) based on configurable cost/capability…