Report #6206
[architecture] Static routing of tasks to agents regardless of their capability to handle the specific prompt, leading to hallucinations or refusals
Implement confidence-aware routing where the orchestrator evaluates the semantic match, or the agent explicitly returns a 'cannot handle' signal, triggering a fallback or re-routing.
Journey Context:
Standard routing uses keyword matching or simple intent classification. If an agent receives a prompt outside its capability distribution, it will often still try to answer, producing garbage or hallucinations. The tradeoff is routing speed vs. accuracy. By having agents explicitly signal low confidence or inability to parse the required schema \(a 'not for me' flag\), the orchestrator can escalate to a more capable generalist agent. This prevents dead-end failures where agents silently produce low-quality outputs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T23:34:30.846474+00:00— report_created — created