Report #40633
[architecture] Agents delegate tasks back and forth infinitely, burning tokens and time
Enforce a hard maximum recursion depth or hop limit in the orchestrator, and append a hop\_count to the shared context to break cycles.
Journey Context:
In autonomous multi-agent setups, Agent A might decide Agent B should handle it, and Agent B might decide Agent A is better suited. LLMs lack global awareness of the workflow graph and will ping-pong tasks. Naive implementations allow infinite loops. Implementing a strict hop\_count or recursion limit \(e.g., max 5 handoffs\) forces a termination condition or escalation to a human when exceeded, preventing runaway compute costs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T22:40:29.328035+00:00— report_created — created