multi-agent-orchestration

Topics in the source

• Multi-Agent Orchestration
• Quick Start
• When to Use
• Best Practices
• Orchestrator-Worker
• Routing & Handoffs
• Shared State
• Reliability

Coordinating multiple specialized agents into reliable systems. Tasks needing different specializations (research, code, review) Parallelizable independent subtasks Long workflows broken into reliable steps Complex domains a single agent handles poorly Orchestrator plans, delegates, and collects results Workers are single-purpose and stateless Define a clear task handoff contract Cap concurrent workers and total steps Route by task type, not by guesswork Use explicit handoff messages (intent + context) Validate worker outputs before handoff Fall back to a default worker on routing failure Use a shared store for facts and artifacts Avoid duplicated context; reference by ID Coordinate writes to avoid races Log the full execution trace Retry failed workers with backoff Set timeouts and budgets per worker Detect loops and deadlocks Aggregate partial results on failure 1. Split the domain into single-purpose worker roles. 2. Define the handoff contract (task, context, output format). 3. Build an orchestrator that plans and routes. 4. Add a shared state store for artifacts. 5. Run independent subtasks in parallel with limits. 6. Add retries, timeouts, and budgets. 7. Validate outputs at

This is an excerpt. Refer to the complete source and its current requirements.