Report #83343
[architecture] Agents bouncing a task back and forth infinitely because neither takes ownership
Implement a hard maximum handoff depth limit and require the receiving agent to explicitly accept or reject a task with a reason, preventing automatic re-delegation to the sender.
Journey Context:
When Agent A delegates to Agent B, and B lacks the context or capability, it often defaults to delegating back to A. Without a circuit breaker, this creates an infinite loop of handoffs, burning tokens and time. Setting a max\_depth \(similar to graph recursion limits\) forces the system to fail gracefully or escalate to a supervisor, mirroring call stack limits in traditional software.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T22:28:40.363480+00:00— report_created — created