omc-teams

Orchestrate parallel claude, codex, or gemini CLI workers in tmux panes.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Leap0920/Clean-Portfolio --skill omc-teams-leap0920
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-teams
Source: https://github.com/Leap0920/Clean-Portfolio/tree/main/%25USERPROFILE%25/.openclaude/plugins/cache/omc/oh-my-claudecode/4.14.0/skills/omc-teams
Command: npx skills add https://github.com/Leap0920/Clean-Portfolio --skill omc-teams-leap0920

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OMC Teams solves the need to execute multiple AI-agent tasks in parallel without manually managing concurrent sessions, using tmux pane splitting for process-based worker concurrency.

Core Features & Use Cases

  • Parallel CLI workers: Spawn N workers in tmux panes for claude, codex, or gemini to run independent task subtasks concurrently.
  • Deterministic team execution flow: Validates agent type, decomposes work across workers, and coordinates monitoring and lifecycle via omc team ... commands.
  • Workspace-root handling for multi-repo plans: Helps select a shared working directory so all workers operate in the correct repo context when a plan and implementation live in different sibling repositories.
  • Lifecycle management: Supports task status, API-based introspection, and controlled shutdown (including forced cleanup for stale teams).
  • Clear requirements & error mapping: Explicitly checks tmux availability and gives targeted fixes for common runtime failures (CLI not installed, unsupported agent types, stale runtime state).

Quick Start

Tell your agent to run 3 parallel Claude workers using OMC Teams: /oh-my-claudecode:omc-teams 3:claude "implement auth module with tests".

Frequently Asked Questions about omc-teams

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Can I use Codex or Gemini CLI agents with tmux pane orchestration?

Yes, tmux pane orchestration supports strict agent-type validation for Codex and Gemini CLI workers, allowing you to spawn independent subtasks concurrently across any of these supported agent types.

How do I manage parallel AI agent tasks across multiple repositories?

To manage parallel AI agent tasks across multiple repositories, you must select a shared workspace root directory so all workers operate in the correct repo context when a plan and implementation live in different sibling repositories.

Do I need tmux installed to run parallel agent workers for task orchestration?

Yes, you need tmux installed to run parallel agent workers, as the orchestration explicitly checks tmux availability and gives targeted fixes for common runtime failures if the dependency is missing.

What is the best way to monitor and shut down parallel CLI worker teams?

The best way to monitor and shut down parallel CLI worker teams is using team lifecycle commands, which provide task status, API-based task listing introspection, and controlled shutdown including forced cleanup for stale runtime state.

Why does parallel task execution fail with unsupported agent types or stale runtime state?

Parallel task execution fails when strict agent-type validation encounters unsupported CLI workers or when stale runtime state is not cleared, requiring targeted error mapping and forced cleanup to restore the team lifecycle.