Report #46403
[synthesis] Agent gets stuck in loops confirming its own bad assumptions without throwing errors
Track the semantic uniqueness of consecutive LLM thoughts. If the embedding distance between thought N and thought N\+1 falls below 0.1 for 3 consecutive steps while the tool outputs remain static, break the loop by injecting a contrarian prompt \('Challenge the previous assumption'\).
Journey Context:
When an agent encounters an ambiguous tool result, it might generate a hypothesis. If the next tool call is shaped by that hypothesis to return ambiguous data again, the agent interprets it as confirmation. No errors occur, latency is fine, but the agent is orbiting a false premise. Uniqueness tracking on the reasoning chain catches this echo chamber that standard loop detection \(exact string matching or repetitive tool calls\) misses.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:21:49.292111+00:00— report_created — created