Report #24522
[architecture] Agents endlessly delegate tasks back and forth without making progress
Enforce a strict Directed Acyclic Graph \(DAG\) for agent delegation, or implement a global max\_steps counter with a forced termination and escalation protocol.
Journey Context:
When two agents have overlapping capabilities or misaligned goals, Agent A might say 'I can't do this, ask Agent B', and Agent B says 'This is Agent A's job'. Without a global orchestrator keeping track of the call stack, this loop runs infinitely, burning tokens. The fix is to model the agent delegation as a DAG \(Agent B cannot call Agent A if A called B\) or a hard step limit. The tradeoff is that a DAG limits dynamic routing flexibility, but it guarantees termination, which is a hard requirement for production systems.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:34:26.456963+00:00— report_created — created