oh-my-claudecode: Teams, Terminal Workers and Verification Loops
Purpose, mechanisms, getting started and boundaries
Source: Yeachan-Heo/oh-my-claudecode · Yeachan-Heo
User Problem
Positioning and task fitoh-my-claudecode, or OMC, adds planning, delegation, execution and verification around Claude Code, with a separate terminal runtime. Similar-looking commands can invoke different mechanisms: in-session /team and terminal omc team are not the same runtime. Understanding those differences prevents command and deployment mistakes.
- Distribute separable work among executors
- Observe different model CLIs in terminal panes
- Establish repeated verification and repair
Product Mechanism
Capabilities and execution- Team is a staged pipelineThe main team path moves through planning, PRD, execution, verification and repair. Its value depends on divisible work and shared acceptance criteria. Source
- Terminal workers run separatelyomc team launches real CLI processes through tmux, while /team uses the in-session native workflow. Authentication, dependencies and observation differ. Source
- A loop needs one authorityDocumentation recommends one primary loop authority per session. Execute, Team, Verify and the host’s native goal each own different completion behavior; stacking them obscures state and stopping conditions. Source
- Preserve state and reusable knowledgeHUD, session analytics and skill learning support observation and reuse. Runtime state is not automatically team policy and should not be committed indiscriminately. Source
Workflow
Start with a small task- Choose plugin or CLIClaude Code users can start with the marketplace plugin. Add the npm runtime, tmux and provider CLIs when terminal workers are needed.
- Complete setupRun the appropriate setup and confirm command discovery. Enter plugin slash commands individually rather than as one shell command.
- Define separable workBegin with independent files or reports, define responsibilities and completion criteria, and order dependencies for shared modifications.
- Finish with verification evidenceInspect status, diffs, test output and unresolved issues. Use documented terminal commands in CI rather than assuming interactive skills run without a session.
The trial sequence and checks are editorial guidance. Entry commands follow official documentation; this project was not executed for the article. Source
Official entry example
omc team 2:codex "Review the test coverage of two independent modules and report findings"Complete the prerequisites above first. Examples contain no real credentials.
Limits and Boundaries
Constraints and selection| Boundary | Meaning | Suggested action |
|---|---|---|
| Command surfaces | The README explicitly says omc autopilot, omc ralph and omc execute are not CLI subcommands. Source | Invoke those capabilities as skills inside an active session. |
| Cost and completion claims | Routing and token-saving claims do not replace measurements on comparable tasks, and parallel work adds calls. Source | Track quality, total cost and human review time together. |
Scroll horizontally to view the full table
OMC fits intensive Claude Code use with explicit planning and verification. Simple questions remain easier to assess in one session.
How to Evaluate Adoption
Trial scenario and verificationPilot two workers reviewing coverage in independent modules, then combine their reports in the lead session. Verify file references and missing cases before attempting parallel edits. Report-only work exposes delegation quality with less merge interference.
Verify worker startup, collected output, source-grounded findings and shutdown. Multiple visible panes do not prove successful coordination.
Evidence: Pinned README · Current repository。
Source fetched (UTC): 2026-11-02T07:26:46.761Z；snapshot commit: 14cd0fe92fbe。The source date denotes the repository snapshot commit, not the project’s original launch.