Report #39083
[architecture] Orchestrator routing tasks to the wrong agent due to ambiguous intent matching
Require agents to return a confidence score \(0.0-1.0\) along with their output. The orchestrator should route to the agent with the highest confidence, and if the max confidence is below a threshold, fall back to a generalist agent or ask the user for clarification.
Journey Context:
Standard routing often relies on an LLM classifying a prompt into an agent name. If the prompt is ambiguous, the classifier might force a routing decision with low confidence, sending a coding task to a database agent. By making confidence an explicit output of the routing function or the receiving agent's initial evaluation, the system can avoid executing high-risk, low-confidence actions. This is the 'reject option' in classification theory applied to agentic routing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:04:30.130713+00:00— report_created — created