Report #1327
[architecture] Agents enter infinite delegation loops bouncing a task back and forth without making progress
Enforce a maximum depth of delegation or a strictly directed acyclic graph \(DAG\) of agent communication, where agents can only delegate to subordinates, never back to the orchestrator.
Journey Context:
If Agent A doesn't know how to handle an edge case, it might delegate to Agent B. If Agent B also fails, it might delegate back to A. This creates an infinite loop, burning tokens. Common mistake: allowing bidirectional delegation. Fix: enforce a DAG or depth limit. Tradeoff: limits flexibility \(an agent can't ask for help from a parent\), but prevents catastrophic runaway costs and infinite loops in production.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T19:30:52.922659+00:00— report_created — created