Report #44984
[synthesis] Agent loop keeps running without throwing errors but makes zero progress towards the goal
Implement a state-diff progress check: if the environment state \(files, API responses\) has not meaningfully changed after two consecutive agent steps, break the loop and re-prompt with a drastically different strategy.
Journey Context:
Developers build agent loops that exit on exceptions or max iterations. However, an agent can get stuck in a 'soft loop'—repeatedly reading a file, trying an edit that doesn't apply, and reading again, all without throwing a hard error. Checking only for exceptions misses this. The tradeoff is that strict state-diff checks might prematurely abort a slow-but-valid planning step, but this is far safer than burning an entire context window on a stuck loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:58:23.947399+00:00— report_created — created