Report #3686
[architecture] Central orchestrator agent processing every message between workers creating a latency and token-cost bottleneck
Use an orchestrator only for task delegation and final aggregation; allow peer-to-peer handoffs for intermediate steps using direct function-call returns, bypassing the orchestrator.
Journey Context:
Centralized orchestration is easy to reason about but scales poorly. The orchestrator spends 90% of its tokens just reading and forwarding intermediate messages. Decentralized handoffs are harder to debug but scale linearly. The right call is a hybrid: central routing, peer execution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:03:02.147984+00:00— report_created — created