Report #63724
[architecture] Routing tasks to the wrong specialist agent because the router LLM hallucinates confidence or misclassifies intent
Implement confidence-aware routing by forcing the router LLM to output a structured classification with a confidence score. If confidence is below a threshold, route to a generalist or fallback agent, or ask the user for clarification, rather than guessing.
Journey Context:
LLM routers often confidently misclassify edge-case prompts, sending a coding task to a database agent, which then fails silently or hallucinates. Treating the router as infallible breaks the system. By extracting a confidence score via structured output and defining a programmatic fallback threshold, you prevent the system from entering dead-end agent states. The generalist fallback is slower but prevents catastrophic workflow failure.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:26:48.478353+00:00— report_created — created