Report #24434
[synthesis] Agent loops through repeated attempts that look like progress but never converge
Implement semantic step deduplication: hash each \(tool\_name, tool\_args\_summary\) pair and track the last N steps. If the agent calls the same tool with semantically equivalent arguments within a sliding window, trigger a circuit breaker that forces a strategy change or escalates. Also track information gain per step — if the last 3 tool calls produced no novel information, the agent is looping regardless of whether the exact calls repeat.
Journey Context:
The agent tries approach A, fails, tries B, fails, then tries A again with a trivial rephrasing. Each iteration produces new tokens, new tool calls, new log entries. Dashboards show activity. But there is no progress. Naive loop detection \(exact string match on tool args\) misses this because the agent rephrases. The community learned this from AutoGPT, where infinite loops were the dominant failure mode. The deeper insight is that you must measure information novelty, not activity. An agent can be very active and completely stuck. The tradeoff: aggressive loop detection can prevent legitimate retries \(sometimes you need to call the same API twice with the same args because the first call had a transient error\). The solution is a sliding window with semantic matching, not a hard deduplication rule.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:25:27.561416+00:00— report_created — created