Ohmg

oh-my-ag (ohmg) - Multi-Agent Orchestrator

When to use this skill

• Coordinating complex multi-domain projects
• Parallelizing tasks across multiple AI agents (PM, Frontend, Backend, etc.)
• Using Serena Memory for cross-agent state management
• Setting up real-time observability dashboards for agent workflows
• Integrating multi-CLI vendors (Gemini, Claude, Codex) in a single project

Quick Start

Scenario: Platform setup for a Unity3D project

# Step 1: Install oh-my-ag
bunx oh-my-ag
# Select "Unity3D" when prompted for project type

# Step 2: Verify system is ready
bunx oh-my-ag doctor

# Step 3: Launch the monitoring dashboard and spawn your first agent
bunx oh-my-ag dashboard &
oh-my-ag agent:spawn backend "Set up Unity3D build pipeline" session-unity-01

Instructions

1. Install oh-my-ag, then confirm doctor and dashboard checks pass in the Unity workspace.
2. Map each domain to the CLI that should own it before spawning long-lived agents.
3. Keep Serena Memory and monitoring enabled so multi-agent Unity work remains auditable.

Examples

/coordinate

oh-my-ag agent:spawn qa "triage failing Unity regression tests" session-unity-qa

1. Core Concepts

Specialized Agents

Serena Memory

Orchestrator writes structured state to .serena/memories/ for real-time monitoring and cross-agent coordination.

2. Installation & Setup

Prerequisites

• Bun (CLI and dashboards)
• uv (Serena setup)

Interactive Setup

bunx oh-my-ag

Select project type to install relevant skills to .agent/skills/.

Verification

bunx oh-my-ag doctor

3. Usage Patterns

Explicit Coordination

/coordinate

PM planning → agent spawning → QA review.

Spawning Agents via CLI

# Spawn backend agent for a specific task
oh-my-ag agent:spawn backend "Implement auth API" session-01

Dashboard Monitoring

• Terminal: bunx oh-my-ag dashboard
• Web: bunx oh-my-ag dashboard:web (http://localhost:9847)

4. MCP Connection & Bridging

SSE Mode (Shared Server)

If environment needs stdio-to-http bridging:

bunx oh-my-ag bridge http://localhost:12341/sse

5. Configuration

Configure per-agent CLI mapping in .agent/config/user-preferences.yaml:

agent_cli_mapping:
  frontend: gemini
  backend: codex
  pm: claude
  qa: claude

Quick Reference