Report #14634
[architecture] Router agent dispatching tasks to the wrong specialist agent due to lack of confidence scoring
Require the router agent to output a confidence score alongside its routing choice; if confidence is below a threshold, route to a generalist or prompt the user for clarification instead of guessing.
Journey Context:
A common failure mode is forcing a router to always pick a specialist, even when the query is ambiguous. The router hallucinates a match, sending the task to the wrong agent, which then fails or hallucinates further. By making confidence a structured output of the routing function, you create a deliberate escape hatch. Low confidence triggers a fallback to a generalist agent that can ask clarifying questions, preventing cascading errors down the wrong specialist path.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:08:33.698513+00:00— report_created — created