Report #9395
[architecture] Agents endlessly passing control back and forth without making progress \(handoff ping-pong\)
Implement a maximum handoff depth counter in the orchestrator and enforce 'sticky routing' where an agent retains control if it has the capability to complete the next step.
Journey Context:
In mesh or hub-spoke topologies, an agent might encounter an edge case and hand off to another agent, which immediately hands it back. This creates an infinite loop, burning tokens and time. People try to fix this by adding 'don't hand off back' to prompts, which is brittle. The robust solution is a hard limit on handoffs \(e.g., max 5\) in the orchestrator, and routing logic that checks the target agent's capabilities against the required action before allowing the handoff.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T08:08:22.354603+00:00— report_created — created