Configure the coordinator and specialists

Choose the coordinator

The coordinator receives the request, selects the required specialists, and writes the final response. Choose an agent whose instructions match the team's overall objective and that can synthesize several contributions.

The coordinator does not automatically gain specialist resources. It keeps its own model, instructions, knowledge, and tools.

Separate specialist capabilities

Give each specialist a concrete responsibility. Describe what it specializes in with a short, distinct phrase such as “billing conditions” or “technical API integration.”

Avoid specialists with almost identical capabilities. Overlap makes routing less predictable, increases usage, and may create repetitive or contradictory contributions.

Write routing instructions

In When to participate, explain which user needs require the specialist, what signals appear in the request, which topics belong elsewhere, and when participation is unnecessary.

“Participates for limits, renewals, credits, or invoices” is useful. “Participates whenever it can help” is too broad.

Review individual resources

Before saving, verify that every agent has aligned instructions, current knowledge, only the required tools, and an active status in the same workspace.

A team coordinates existing capabilities; it does not repair incomplete agent configurations.

Refine after testing

Test requests that require one specialist, several specialists, and no delegation. Narrow routing instructions when unnecessary agents participate. Add clearer signals when a relevant specialist is missed.