Repository: Yeachan-Heo/oh-my-claudecode

Stars: 29575

CLAUDE.md Copy Chapter

<!-- OMC:START -->
<!-- OMC:VERSION:4.9.1 -->

oh-my-claudecode - Intelligent Multi-Agent Orchestration

You are running with oh-my-claudecode (OMC), a multi-agent orchestration layer for Claude Code.
Coordinate specialized agents, tools, and skills so work is completed accurately and efficiently.

<operating_principles>
- Delegate specialized work to the most appropriate agent.
- Prefer evidence over assumptions: verify outcomes before final claims.
- Choose the lightest-weight path that preserves quality.
- Consult official docs before implementing with SDKs/frameworks/APIs.
</operating_principles>

<delegation_rules>
Delegate for: multi-file changes, refactors, debugging, reviews, planning, research, verification.
Work directly for: trivial ops, small clarifications, single commands.
Route code to executor (use model=opus for complex work). Uncertain SDK usage → document-specialist (repo docs first; Context Hub / chub when available, graceful web fallback otherwise).
</delegation_rules>

<model_routing>
haiku (quick lookups), sonnet (standard), opus (architecture, deep analysis).
Direct writes OK for: ~/.claude/, .omc/, .claude/, CLAUDE.md, AGENTS.md.
</model_routing>

<agent_catalog>
Prefix: oh-my-claudecode:. See agents/*.md for full prompts.

explore (haiku), analyst (opus), planner (opus), architect (opus), debugger (sonnet), executor (sonnet), verifier (sonnet), tracer (sonnet), security-reviewer (sonnet), code-reviewer (opus), test-engineer (sonnet), designer (sonnet), writer (haiku), qa-tester (sonnet), scientist (sonnet), document-specialist (sonnet), git-master (sonnet), code-simplifier (opus), critic (opus)
</agent_catalog>

<tools>
External AI: /team N:executor "task", omc team N:codex|gemini "...", omc ask <claude|codex|gemini>, /ccg
OMC State: state_read, state_write, state_clear, state_list_active, state_get_status
Teams: TeamCreate, TeamDelete, SendMessage, TaskCreate, TaskList, TaskGet, TaskUpdate
Notepad: notepad_read, notepad_write_priority, notepad_write_working, notepad_write_manual
Project Memory: project_memory_read, project_memory_write, project_memory_add_note, project_memory_add_directive
Code Intel: LSP (lsp_hover, lsp_goto_definition, lsp_find_references, lsp_diagnostics, etc.), AST (ast_grep_search, ast_grep_replace), python_repl
</tools>

<skills>
Invoke via /oh-my-claudecode:<name>. Trigger patterns auto-detect keywords.

Workflow: autopilot, ralph, ultrawork, team, ccg, ultraqa, omc-plan, ralplan, sciomc, external-context, deepinit, deep-interview, ai-slop-cleaner, self-improve
Keyword triggers: "autopilot"→autopilot, "ralph"→ralph, "ulw"→ultrawork, "ccg"→ccg, "ralplan"→ralplan, "deep interview"→deep-interview, "deslop"/"anti-slop"/cleanup+slop-smell→ai-slop-cleaner, "deep-analyze"→analysis mode, "tdd"→TDD mode, "deepsearch"→codebase search, "ultrathink"→deep reasoning, "cancelomc"→cancel. Team orchestration is explicit via /team.
Utilities: ask-codex, ask-gemini, cancel, note, learner, omc-setup, mcp-setup, hud, omc-doctor, omc-help, trace, release, project-session-manager, skill, writer-memory, ralph-init, configure-notifications, learn-about-omc (trace is the evidence-driven tracing lane)
Per-role /team routing: configure provider/model per canonical role (codex critic, gemini reviewer, etc.) in .claude/omc.jsonc under team.roleRouting — accepted aliases such as reviewer are normalized and applied at runtime. See skills/team/SKILL.md#per-role-provider--model-routing.
</skills>

<team_pipeline>
Stages: team-plan → team-prd → team-exec → team-verify → team-fix (loop).
Fix loop bounded by max attempts. team ralph links both modes.
</team_pipeline>

<verification>
Verify before claiming completion. Size appropriately: small→haiku, standard→sonnet, large/security→opus.
If verification fails, keep iterating.
</verification>

<execution_protocols>
Broad requests: explore first, then plan. 2+ independent tasks in parallel. run_in_background for builds/tests.
Keep authoring and review as separate passes: writer pass creates or revises content, reviewer/verifier pass evaluates it later in a separate lane.
Never self-approve in the same active context; use code-reviewer or verifier for the approval pass.
Before concluding: zero pending tasks, tests passing, verifier evidence collected.
</execution_protocols>

<commit_protocol>
Use git trailers to preserve decision context in every commit message.
Format: conventional commit subject line, optional body, then structured trailers.

Trailers (include when applicable — skip for trivial commits like typos or formatting):
- Constraint: active constraint that shaped this decision
- Rejected: alternative considered | reason for rejection
- Directive: warning or instruction for future modifiers of this code
- Confidence: high | medium | low
- Scope-risk: narrow | moderate | broad
- Not-tested: edge case or scenario not covered by tests

Example:

fix(auth): prevent silent session drops during long-running ops
Auth service returns inconsistent status codes on token expiry,
so the interceptor catches all 4xx and triggers inline refresh.
Constraint: Auth service does not support token introspection
Constraint: Must not add latency to non-expired-token paths
Rejected: Extend token TTL to 24h | security policy violation
Rejected: Background refresh on timer | race condition with concurrent requests
Confidence: high
Scope-risk: narrow
Directive: Error handling is intentionally broad (all 4xx) — do not narrow without verifying upstream behavior
Not-tested: Auth service cold-start latency >500ms

<hooks_and_context>
Hooks inject <system-reminder> tags. Key patterns: hook success: Success (proceed), [MAGIC KEYWORD: ...] (invoke skill), The boulder never stops (ralph/ultrawork active).
Persistence: <remember> (7 days), <remember priority> (permanent).
Kill switches: DISABLE_OMC, OMC_SKIP_HOOKS (comma-separated).
</hooks_and_context>

<cancellation>
/oh-my-claudecode:cancel ends execution modes. Cancel when done+verified or blocked. Don't cancel if work incomplete.
</cancellation>

<worktree_paths>
State: .omc/state/, .omc/state/sessions/{sessionId}/, .omc/notepad.md, .omc/project-memory.json, .omc/plans/, .omc/research/, .omc/logs/
</worktree_paths>

Setup Copy Chapter

Say "setup omc" or run /oh-my-claudecode:omc-setup.

<!-- OMC:END -->

README.md Copy Chapter

English | 한국어 | 中文 | 日本語 | Español | Tiếng Việt | Português

oh-my-claudecode


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

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

_Don't learn Claude Code. Just use OMC._

Get Started • Documentation • CLI Reference • Workflows • Migration Guide • Discord

---

Core Maintainers Copy Chapter

| Role | Name | GitHub |
| --- | --- | --- |
| Creator & Lead | Yeachan Heo | @Yeachan-Heo |

Ambassadors Copy Chapter

| Name | GitHub |
| --- | --- |
| Sigrid Jin | @sigridjineth |

Top Collaborators Copy Chapter

| Name | GitHub | Commits |
| --- | --- | --- |
| JunghwanNA | @shaun0927 | 65 |
| riftzen-bit | @riftzen-bit | 52 |
| Seunggwan Song | @Nathan-Song | 20 |
| BLUE | @blue-int | 20 |
| Junho Yeo | @junhoyeo | 15 |

Quick Start Copy Chapter

Step 1: Install

Marketplace/plugin install (recommended for most Claude Code users).
These are Claude Code slash commands — enter them one at a time (pasting both lines at once will fail):

/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode

Then:

/plugin install oh-my-claudecode

If you prefer the npm CLI/runtime path instead of the marketplace flow:

npm i -g oh-my-claude-sisyphus@latest

Step 2: Setup

Inside a Claude Code / OMC session

/setup
/omc-setup
From your terminal

omc setup

If you run OMC via omc --plugin-dir <path> or claude --plugin-dir <path>, add --plugin-dir-mode to omc setup (or export OMC_PLUGIN_ROOT before running it) so the installer doesn't duplicate skills/agents that the plugin already provides at runtime. See the Plugin directory flags section in REFERENCE.md for a complete decision matrix and all available flags.

Step 3: Build something

Inside a Claude Code / OMC session

/autopilot "build a REST API for managing tasks"
Natural-language in-session shortcut

autopilot: build a REST API for managing tasks

That's it. Everything else is automatic.

CLI Commands vs In-Session Skills Copy Section

OMC exposes two different surfaces:

- Terminal CLI commands: run omc ... from your shell after installing the npm/runtime path (npm i -g oh-my-claude-sisyphus@latest) or from a local checkout.
- In-session skills: run /... inside a Claude Code session after installing the plugin/setup flow.

| Feature | Terminal CLI | In-session skill | Notes |
| --- | --- | --- | --- |
| Setup | omc setup | /setup or /omc-setup | Both are real entrypoints. /setup is the easiest plugin-first path. |
| Ask providers | omc ask codex "review this patch" | /ask codex "review this patch" | Both route through the same advisor flow. |
| Team orchestration | omc team 2:codex "review auth flow" | /team 3:executor "fix all TypeScript errors" | Both exist, but they are different runtimes: omc team launches tmux CLI workers; /team runs the in-session native team workflow. |
| Autopilot / Ralph / Ultrawork / Deep Interview | — | /autopilot ..., /ralph ..., /ultrawork ..., /deep-interview ... | These are in-session skills. There is no omc autopilot / omc ralph / omc ultrawork CLI subcommand in this repo. |
| Autoresearch | omc autoresearch ... | /deep-interview --autoresearch ... | omc autoresearch is the real CLI command. The in-session path is the setup/interview lane that helps you launch it. |

Not Sure Where to Start? Copy Section

If you're uncertain about requirements, have a vague idea, or want to micromanage the design:

/deep-interview "I want to build a task management app"

The deep interview uses Socratic questioning to clarify your thinking before any code is written. It exposes hidden assumptions and measures clarity across weighted dimensions, ensuring you know exactly what to build before execution begins.

Team Mode (Recommended) Copy Chapter

Starting in v4.1.7, Team is the canonical orchestration surface in OMC. The legacy swarm keyword/skill has been removed; use team directly.

/team 3:executor "fix all TypeScript errors"

Use /team ... when you want Claude Code's in-session native team workflow. Use omc team ... when you want terminal-launched tmux CLI workers (claude / codex / gemini panes).

Team runs as a staged pipeline:

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

Enable Claude Code native teams in ~/.claude/settings.json:

{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  }
}

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

tmux CLI Workers — Codex & Gemini (v4.4.0+) Copy Section

v4.4.0 removes the Codex/Gemini MCP servers (x, g providers). Use the CLI-first Team runtime (omc team ...) to spawn real tmux worker panes:

omc team 2:codex "review auth module for security issues"
omc team 2:gemini "redesign UI components for accessibility"
omc team 1:claude "implement the payment flow"
omc team status auth-review
omc team shutdown auth-review

/omc-teams remains as a legacy compatibility skill and now routes to omc team ....

For mixed Codex + Gemini work in one command, use the /ccg skill (routes via /ask codex + /ask gemini, then Claude synthesizes):

/ccg Review this PR — architecture (Codex) and UI components (Gemini)

| Surface | Workers | Best For |
| ------------------------- | ------------------ | -------------------------------------------- |
| omc team N:codex "..." | N Codex CLI panes | Code review, security analysis, architecture |
| omc team N:gemini "..." | N Gemini CLI panes | UI/UX design, docs, large-context tasks |
| omc team N:claude "..." | N Claude CLI panes | General tasks via Claude CLI in tmux |
| /ccg | /ask codex + /ask gemini | Tri-model advisor synthesis |

Workers spawn on-demand and die when their task completes — no idle resource usage. Requires codex / gemini CLIs installed and an active tmux session.

Note: Package naming — The project is branded as oh-my-claudecode (repo, plugin, commands), but the npm package is published as oh-my-claude-sisyphus. If you install or upgrade the CLI tools via npm/bun, use npm i -g oh-my-claude-sisyphus@latest.

Updating Copy Section

If you installed OMC via npm, upgrade with the published package name:

npm i -g oh-my-claude-sisyphus@latest

Package naming note: the repo, plugin, and commands are branded oh-my-claudecode, but the published npm package name remains oh-my-claude-sisyphus.

If you installed OMC via the Claude Code marketplace/plugin flow, update with:

1. Update the marketplace clone

/plugin marketplace update omc
2. Re-run setup to refresh configuration

/setup

If you are developing from a local checkout or git worktree, update the checkout first, then re-run setup from that worktree so the active runtime matches the code you are testing.

Note: If marketplace auto-update is not enabled, you must manually run /plugin marketplace update omc to sync the latest version before running setup.

If you experience issues after updating, clear the old plugin cache:

/omc-doctor

<h1 align="center">Your Claude Just Have been Steroided.</h1>

<p align="center">
<img src="assets/omc-character.jpg" alt="oh-my-claudecode" width="400" />
</p>

---

Why oh-my-claudecode? Copy Chapter

- Zero configuration required - Works out of the box with intelligent defaults
- Team-first orchestration - Team is the canonical multi-agent surface
- Natural language interface - No commands to memorize, just describe what you want
- Automatic parallelization - Complex tasks distributed across specialized agents
- Persistent execution - Won't give up until the job is verified complete
- Cost optimization - Smart model routing saves 30-50% on tokens
- Learn from experience - Automatically extracts and reuses problem-solving patterns
- Real-time visibility - HUD statusline shows what's happening under the hood

---

Features Copy Chapter

Orchestration Modes Copy Section

Multiple strategies for different use cases — from Team-backed orchestration to token-efficient refactoring. Learn more →

| Mode | What it is | Use For |
| ----------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| Team (recommended) | Canonical staged pipeline (team-plan → team-prd → team-exec → team-verify → team-fix) | Coordinated Claude agents on a shared task list |
| omc team (CLI) | tmux CLI workers — real claude/codex/gemini processes in split-panes | Codex/Gemini CLI tasks; on-demand spawn, die when done |
| ccg | Tri-model advisors via /ask codex + /ask gemini, Claude synthesizes | Mixed backend+UI work needing both Codex and Gemini |
| Autopilot | Autonomous execution (single lead agent) | End-to-end feature work with minimal ceremony |
| Ultrawork | Maximum parallelism (non-team) | Burst parallel fixes/refactors where Team isn't needed |
| Ralph | Persistent mode with verify/fix loops | Tasks that must complete fully (no silent partials) |
| Pipeline | Sequential, staged processing | Multi-step transformations with strict ordering |
| Ultrapilot (legacy) | Deprecated compatibility mode (autopilot pipeline alias) | Existing workflows and older docs |

Intelligent Orchestration Copy Section

- 19 specialized agents (with tier variants) for architecture, research, design, testing, data science
- Smart model routing - Haiku for simple tasks, Opus for complex reasoning
- Automatic delegation - Right agent for the job, every time

Developer Experience Copy Section

- Magic keywords - ralph, ulw, ralplan; Team stays explicit via /team
- HUD statusline - Real-time orchestration metrics in your status bar
- If you launch Claude Code directly with claude --plugin-dir <path> (bypassing the omc shim), export OMC_PLUGIN_ROOT=<path> in your shell so the HUD bundle resolves to the same checkout as the plugin loader. See the Plugin directory flags section in REFERENCE.md for details.
- Skill learning - Extract reusable patterns from your sessions
- Analytics & cost tracking - Understand token usage across all sessions

Contributing Copy Section

Want to contribute to OMC? See CONTRIBUTING.md for the full developer guide, including how to fork, set up a local checkout, link it as your active plugin, run tests, and submit PRs.

Custom Skills Copy Section

Learn once, reuse forever. OMC extracts hard-won debugging knowledge into portable skill files that auto-inject when relevant.

| | Project Scope | User Scope |
|---|---|---|
| Path | .omc/skills/ | ~/.omc/skills/ |
| Shared with | Team (version-controlled) | All your projects |
| Priority | Higher (overrides user) | Lower (fallback) |

.omc/skills/fix-proxy-crash.md

---
name: Fix Proxy Crash
description: aiohttp proxy crashes on ClientDisconnectedError
triggers: ["proxy", "aiohttp", "disconnected"]
source: extracted
---
Wrap handler at server.py:42 in try/except ClientDisconnectedError...

Manage skills: /skill list | add | remove | edit | search
Auto-learn: /learner extracts reusable patterns with strict quality gates
Auto-inject: Matching skills load into context automatically — no manual recall needed

Full feature list →

---

In-session shortcuts Copy Chapter

These shortcuts run inside a Claude Code / OMC session, not as terminal CLI commands. For shell commands, use the omc ... forms shown above. Team mode is explicit: use /team ... in-session or omc team ... from your shell rather than expecting a bare team keyword trigger.

| In-session form | Kind | Effect | Example |
| ---------------------- | --------------------- | ----------------------------------- | ---------------------------------------------- |
| /team | Slash skill | Canonical Team orchestration | /team 3:executor "fix all TypeScript errors" |
| /ccg | Slash skill | /ask codex + /ask gemini synthesis | /ccg review this PR |
| /autopilot / autopilot | Skill / prompt trigger | Full autonomous execution | /autopilot "build a todo app" |
| /ralph / ralph | Skill / prompt trigger | Persistence mode | /ralph "refactor auth" |
| /ultrawork / ulw | Skill / prompt trigger | Maximum parallelism | /ultrawork "fix all errors" |
| /ralplan / ralplan | Skill / prompt trigger | Iterative planning consensus | /ralplan "plan this feature" |
| /deep-interview | Slash skill | Socratic requirements clarification | /deep-interview "vague idea" |
| deepsearch | Prompt trigger | Codebase-focused search routing | deepsearch for auth middleware |
| ultrathink | Prompt trigger | Deep reasoning mode | ultrathink about this architecture |
| cancelomc, stopomc | Prompt trigger | Stop active OMC modes | stopomc |

Notes:

- ralph includes ultrawork: when you activate ralph mode, it automatically includes ultrawork's parallel execution.
- swarm compatibility alias has been removed; migrate existing prompts to /team syntax.
- plan this / plan the keyword triggers were removed; use ralplan or explicit /oh-my-claudecode:omc-plan.

Utilities Copy Chapter

Provider Advisor (omc ask / /ask) omc ask / /ask)')" title="Copy section prompt for LLMs"> Copy Section

Run local provider CLIs and save a markdown artifact under .omc/artifacts/ask/.

Terminal CLI

omc ask claude "review this migration plan"
omc ask codex --prompt "identify architecture risks"
omc ask gemini --prompt "propose UI polish ideas"
omc ask claude --agent-prompt executor --prompt "draft implementation steps"
Inside a Claude Code / OMC session

/ask claude "review this migration plan"
/ask codex "identify architecture risks"

Canonical env vars:

- OMC_ASK_ADVISOR_SCRIPT
- OMC_ASK_ORIGINAL_TASK

Phase-1 aliases OMX_ASK_ADVISOR_SCRIPT and OMX_ASK_ORIGINAL_TASK are accepted with deprecation warnings.

Autoresearch (omc autoresearch) omc autoresearch)')" title="Copy section prompt for LLMs"> Copy Section

omc autoresearch is a real CLI command for the thin-supervisor autoresearch runtime:

omc autoresearch
omc autoresearch --mission "improve startup performance" --eval "npm test -- --run src/cli/__tests__/autoresearch.test.ts"
omc autoresearch init --topic "benchmark onboarding flow"

If you want Claude to help define the mission/evaluator first, start inside the session with:

/deep-interview --autoresearch improve startup performance

That in-session interview lane prepares and launches omc autoresearch ...; it is not a separate autoresearch slash skill.

Rate Limit Wait Copy Section

Auto-resume Claude Code sessions when rate limits reset.

omc wait          # Check status, get guidance
omc wait --start  # Enable auto-resume daemon
omc wait --stop   # Disable daemon

Requires: tmux (for session detection)

Monitoring & Observability Copy Section

Use the HUD for live observability and the current session/replay artifacts for post-session inspection:

- HUD preset: /oh-my-claudecode:hud setup then use a supported preset such as "omcHud": { "preset": "focused" }
- Session summaries: .omc/sessions/*.json
- Replay logs: .omc/state/agent-replay-*.jsonl
- Live HUD rendering: omc hud

Notification Tags (Telegram/Discord/Slack) Copy Section

You can configure who gets tagged when stop callbacks send session summaries.

Set/replace tag list

omc config-stop-callback telegram --enable --token <bot_token> --chat <chat_id> --tag-list "@alice,bob"
omc config-stop-callback discord --enable --webhook <url> --tag-list "@here,123456789012345678,role:987654321098765432"
omc config-stop-callback slack --enable --webhook <url> --tag-list "<!here>,<@U1234567890>"
Incremental updates

omc config-stop-callback telegram --add-tag charlie
omc config-stop-callback discord --remove-tag @here
omc config-stop-callback discord --clear-tags

Tag behavior:

- Telegram: alice becomes @alice
- Discord: supports @here, @everyone, numeric user IDs, and role:<id>
- Slack: supports <@MEMBER_ID>, <!channel>, <!here>, <!everyone>, <!subteam^GROUP_ID>
- file callbacks ignore tag options

OpenClaw Integration Copy Section

Forward Claude Code session events to an OpenClaw gateway to enable automated responses and workflows via your OpenClaw agent.

Quick setup (recommended):

/oh-my-claudecode:configure-notifications
→ When prompted, type "openclaw" → choose "OpenClaw Gateway"

Manual setup: create ~/.claude/omc_config.openclaw.json:

{
  "enabled": true,
  "gateways": {
    "my-gateway": {
      "url": "https://your-gateway.example.com/wake",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" },
      "method": "POST",
      "timeout": 10000
    }
  },
  "hooks": {
    "session-start": { "gateway": "my-gateway", "instruction": "Session started for {{projectName}}", "enabled": true },
    "stop":          { "gateway": "my-gateway", "instruction": "Session stopping for {{projectName}}", "enabled": true }
  }
}

Environment variables:

| Variable | Description |
|----------|-------------|
| OMC_OPENCLAW=1 | Enable OpenClaw |
| OMC_OPENCLAW_DEBUG=1 | Enable debug logging |
| OMC_OPENCLAW_CONFIG=/path/to/config.json | Override config file path |

Supported hook events (6 active in bridge.ts):

| Event | Trigger | Key template variables |
|-------|---------|----------------------|
| session-start | Session begins | {{sessionId}}, {{projectName}}, {{projectPath}} |
| stop | Claude response completes | {{sessionId}}, {{projectName}} |
| keyword-detector | Every prompt submission | {{prompt}}, {{sessionId}} |
| ask-user-question | Claude requests user input | {{question}}, {{sessionId}} |
| pre-tool-use | Before tool invocation (high frequency) | {{toolName}}, {{sessionId}} |
| post-tool-use | After tool invocation (high frequency) | {{toolName}}, {{sessionId}} |

Reply channel environment variables:

| Variable | Description |
|----------|-------------|
| OPENCLAW_REPLY_CHANNEL | Reply channel (e.g. discord) |
| OPENCLAW_REPLY_TARGET | Channel ID |
| OPENCLAW_REPLY_THREAD | Thread ID |

See scripts/openclaw-gateway-demo.mjs for a reference gateway that relays OpenClaw payloads to Discord via ClawdBot.

---

Documentation Copy Chapter

- Full Reference - Complete feature documentation
- CLI Reference - All omc commands, flags, and tools
- Notifications Guide - Discord, Telegram, Slack, and webhook setup
- Recommended Workflows - Battle-tested skill chains for common tasks
- Release Notes - What's new in each version
- Website - Interactive guides and examples
- Migration Guide - Upgrade from v2.x
- Architecture - How it works under the hood
- Performance Monitoring - Agent tracking, debugging, and optimization
- Security Guide - Enterprise deployment and hardening

---

Requirements Copy Chapter

- Claude Code CLI
- Claude Max/Pro subscription OR Anthropic API key

Platform & tmux Copy Section

OMC features like omc team and rate-limit detection require tmux:

| Platform | tmux provider | Install |
| -------------- | -------------------------------------------------------- | ---------------------- |
| macOS | tmux | brew install tmux |
| Ubuntu/Debian | tmux | sudo apt install tmux|
| Fedora | tmux | sudo dnf install tmux|
| Arch | tmux | sudo pacman -S tmux |
| Windows | psmux (native) | winget install psmux |
| Windows (WSL2) | tmux (inside WSL) | sudo apt install tmux|

Windows users: psmux provides a native tmux binary for Windows with 76 tmux-compatible commands. No WSL required.

Optional: Multi-AI Orchestration Copy Section

OMC can optionally orchestrate external AI providers for cross-validation and design consistency. These are not required — OMC works fully without them.

| Provider | Install | What it enables |
| --------------------------------------------------------- | ----------------------------------- | ------------------------------------------------ |
| Gemini CLI | npm install -g @google/gemini-cli | Design review, UI consistency (1M token context) |
| Codex CLI | npm install -g @openai/codex | Architecture validation, code review cross-check |

Cost: 3 Pro plans (Claude + Gemini + ChatGPT) cover everything for ~$60/month.

---

License Copy Chapter

MIT

---

<div align="center">

Inspired by: oh-my-opencode • claude-hud • Superpowers • everything-claude-code • Ouroboros

Zero learning curve. Maximum power.

</div>

<!-- OMC:FEATURED-CONTRIBUTORS:START -->

Featured by OmC Contributors Copy Chapter

Top personal non-fork, non-archived repos from all-time OMC contributors (100+ GitHub stars).

- @Yeachan-Heo — oh-my-claudecode (⭐ 28k)
- @junhoyeo — tokscale (⭐ 1.8k)
- @psmux — psmux (⭐ 1.2k)
- @BowTiedSwan — buildflow (⭐ 290)
- @alohays — awesome-visual-representation-learning-with-transformers (⭐ 269)
- @jcwleo — random-network-distillation-pytorch (⭐ 261)
- @emgeee — mean-tutorial (⭐ 200)
- @shaun0927 — openchrome (⭐ 177)
- @anduinnn — HiFiNi-Auto-CheckIn (⭐ 170)
- @Znuff — consolas-powerline (⭐ 146)
- @MeroZemory — ida-multi-mcp (⭐ 143)
- @HaD0Yun — Gopeak-godot-mcp (⭐ 122)

<!-- OMC:FEATURED-CONTRIBUTORS:END -->

Star History Copy Chapter


💖 Support This Project Copy Chapter

If Oh-My-ClaudeCode helps your workflow, consider sponsoring:


Why sponsor? Copy Section

- Keep development active
- Priority support for sponsors
- Influence roadmap & features
- Help maintain free & open source

Other ways to help Copy Section

- ⭐ Star the repo
- 🐛 Report bugs
- 💡 Suggest features
- 📝 Contribute code