Report #16190
[architecture] Orchestrator agent hallucinates a handoff to a wrong sub-agent because it guesses rather than admitting uncertainty
Implement a routing mechanism that explicitly evaluates confidence in the routing decision, defaulting to a generalist agent or asking the user for clarification if confidence is below a threshold.
Journey Context:
LLMs are eager pleasers and will confidently route a legal query to a coding agent if the coding agent's description is slightly ambiguous. By forcing a confidence check—or better, using a dedicated smaller classifier model instead of an LLM for routing—you prevent misrouted tasks. The tradeoff is added latency and token cost to the routing step, but it prevents cascading failures down the wrong agent path.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T02:09:19.563157+00:00— report_created — created