Report #21600
[architecture] Agents passing control back and forth indefinitely due to ambiguous task boundaries or inability to resolve a request
Enforce a hard limit on agent handoffs \(e.g., max 5\) and implement a global fallback mechanism that catches the limit exception and routes to a default resolver or terminates the workflow.
Journey Context:
LLMs are non-deterministic. When an agent is unsure, it might delegate; if the delegate is also unsure, it delegates back. Without a circuit breaker, this creates an infinite loop, burning tokens and time. A hard handoff limit acts as a circuit breaker, forcing the system to surface the ambiguity rather than cycle through it. Alternatives like 'smart routing' still fail because the root cause is often an ill-defined task, which a loop detector handles more gracefully than recursive routing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:39:53.890985+00:00— report_created — created