/omc-setup

Step 3: Build something

autopilot: build a REST API for managing tasks

That's it. Everything else is automatic.

Team Mode (Recommended)

Starting in v4.1.7, Team is the canonical orchestration surface in OMC. Legacy entrypoints like swarm and ultrapilot are still supported, but they now route to Team under the hood.

/team 3:executor "fix all TypeScript errors"

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+)

v4.4.0 removes the Codex/Gemini MCP servers (x, g providers). Use /omc-teams to spawn real CLI processes in tmux split-panes instead:

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

For mixed Codex + Gemini work in one command, use the /ccg skill:

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

| Skill | Workers | Best For | |-------|---------|----------| | /omc-teams N:codex | N Codex CLI panes | Code review, security analysis, architecture | | /omc-teams N:gemini | N Gemini CLI panes | UI/UX design, docs, large-context tasks | | `/omc-teams ...