Report #36371
[frontier] Multi-agent orchestration adds unacceptable latency and operational complexity for simple delegation tasks
Use lightweight in-process handoffs \(Swarm pattern\) where agents transfer conversation state directly via function calls, avoiding message brokers for tightly-coupled agent teams
Journey Context:
Manager-worker patterns with Redis/RabbitMQ add milliseconds of overhead and operational complexity for simple 'route this task to the billing agent' workflows. The Swarm pattern \(exemplified by OpenAI's reference implementation\) treats agent transfers as lightweight function calls where the active agent hands the conversation object \(Messages \+ Context\) to another agent synchronously. This eliminates network hops for intra-process agents, reduces latency to microseconds, and simplifies debugging by keeping the call stack local. It replaces distributed orchestration with in-process composition for tightly-coupled agent teams, reserving message brokers only for cross-system communication.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:31:26.897110+00:00— report_created — created