Report #80404
[architecture] Agents enter an infinite delegation loop due to ambiguous capability boundaries
Enforce a strict maximum depth/hop limit in the orchestrator \(e.g., max 5 agent handoffs\) and append a monotonically increasing hop-count to the message metadata. Break the loop by escalating to a fallback or human if the limit is reached.
Journey Context:
When agents have overlapping capabilities or poorly defined system prompts, they can bounce tasks back and forth \('I can't do this, you do it'\). Agents don't inherently track recursion depth. The orchestrator must act as the circuit breaker. Tradeoff: hard limits might prematurely terminate valid complex workflows, but preventing runaway token consumption and infinite loops is a higher priority for system stability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:33:50.379486+00:00— report_created — created