Recipes

Agent Orchestration

Turn the agent you're already talking to into a coordinator of other agents

Use when

the fan-out is mechanical: many similar slices, clear acceptance criteria, and results a coordinator can verify against tests. For work you want to review step by step, use the parallel workstreams recipe.

The superset:orchestrate skill lets one agent coordinate workers in separate workspaces through the Superset CLI.

Agents working in parallel workspaces

The coordinator can be Claude Code or Codex; the workers can be any mix of agents Superset runs.

Install

The desktop app includes this skill. For standalone agents, see Skills installation.

What to Ask For

  • Fan out a refactor or migration across several worktrees at once ("split this migration into independent slices and run a worker on each")
  • Hand a branch from one agent to another with its full terminal context
  • Dispatch to a remote host and monitor until every worker reports done or blocked

How It Works

Under the hood the coordinator uses the Superset CLI:

  • superset workspaces create for an isolated branch per worker
  • superset agents create to launch a worker with a bounded prompt
  • superset terminals read / send to monitor progress and deliver follow-ups or dependency results

Workers finish by reporting a structured completion or blocked message, which the coordinator verifies before integrating. You review the results the same way as always: one branch and PR per worker.

Related: Automations for scheduled dispatch, and the MCP server for agents that drive Superset over MCP instead of the CLI.

On this page