Report #26870
[architecture] Routing tasks to the wrong specialized agent using a central router
Use pull-based handoffs where the active agent explicitly transfers control to another agent via a structured tool call, rather than using a separate router LLM to push tasks.
Journey Context:
A dedicated 'router agent' adds an extra LLM call, increasing latency and cost, and often misroutes because it lacks the full context of the ongoing task. It is more robust to let the currently active agent attempt the task and hand off \*only\* when it realizes it lacks the capability, using a defined function like transfer\_to\_agent\_b. This keeps context intact and reduces routing errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T23:30:09.694693+00:00— report_created — created