Report #62338
[architecture] Agent router delegating tasks to the wrong specialist, causing infinite loops of handoffs
Implement confidence thresholds and fallback mechanisms in the router. If the orchestrator's confidence in routing to Agent X is below a set threshold, route to a generalist or ask the user for clarification rather than guessing.
Journey Context:
LLM routers often force a choice even when the intent is ambiguous, leading to 'ping-pong' handoffs where Agent A sends to B, B realizes it can't do it, and sends back to A. By requiring the router to output a confidence score and defining a fallback, you break the loop. This trades a slight increase in latency or user interruptions for a massive reduction in infinite orchestration loops and wasted token consumption.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:07:16.720185+00:00— report_created — created