omc-teams

Spawn N tmux-pane workers to run distributed tasks across claude, codex, or gemini CLI agents.

Updated May 20, 2026
One-click install
npx skills add https://github.com/xdkp/oh-my-claudecode --skill omc-teams-xdkp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-teams
Source: https://github.com/xdkp/oh-my-claudecode/tree/main/skills/omc-teams
Command: npx skills add https://github.com/xdkp/oh-my-claudecode --skill omc-teams-xdkp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the bottleneck of doing slow, sequential work by letting you spawn multiple CLI agent workers in parallel so you can distribute a task and speed up execution.

Core Features & Use Cases

  • Parallel worker execution in tmux: Starts N independent worker processes split into tmux panes.
  • Multi-agent support: Supports claude, codex, and gemini CLI workers using the same orchestration flow.
  • Workspace-aware launches: Helps you pick the correct shared working directory for multi-repo plans so workers can find plan artifacts and target paths.

Use case: You need to review and implement changes across a codebase by splitting a large request into N independent subtasks, then monitoring and shutting down the team cleanly.

Quick Start

Ask for two parallel Claude CLI workers to implement authentication with tests: /oh-my-claudecode:omc-teams 2: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
How do I run parallel Claude and Codex CLI workers in tmux?

You can run parallel Claude and Codex CLI workers in tmux by spawning N independent worker processes split into tmux panes. This orchestrator distributes a large decomposable task across multiple agents to speed up execution.

What is the best way to split a large development task across multiple agents?

The best way to split a large development task is using process-based parallel execution. You spawn multiple tmux-pane workers to distribute independent subtasks, monitor their status, and shut down the team cleanly upon completion.

Do I need tmux to orchestrate multi-repo workflows with Gemini CLI?

Yes, you need tmux availability to orchestrate multi-repo workflows with Gemini CLI. The orchestration engine requires tmux to spawn and manage the independent panes for each Gemini, Claude, or Codex worker process.

Can I use different agent types like Claude and Gemini in the same parallel workflow?

Yes, you can use different agent types in the same parallel workflow. The orchestration flow supports claude, codex, and gemini CLI workers, validating supported agent types before launching them via the team runtime API.

How do I manage the lifecycle of parallel CLI agent workers?

You manage the lifecycle of parallel CLI agent workers using the provided status, api, and shutdown controls. These commands let you monitor the distributed task progress and cleanly terminate the tmux worker panes when finished.

How do I handle shared workspace roots when running parallel workers?

To handle shared workspace roots when running parallel workers, you must pick the correct shared working directory for multi-repo plans. This ensures all spawned workers can successfully locate the shared plan artifacts and absolute target paths.