Report #36266
[synthesis] Agentic Loops Fail Differently Per Model: GPT-4o Gets Lazy, Claude Apologizes, Gemini Drifts
Implement model-specific loop detectors: monitor for repeated read-only tool calls \(GPT-4o\), repeated syntax retries with apologies \(Claude\), or sudden shifts in task objective \(Gemini\).
Journey Context:
Agentic frameworks often use a generic 'repeated action' detector to break infinite loops. This misses the distinct failure modes of each model. GPT-4o tends to get stuck in 'lazy action' loops, repeatedly reading files or searching without taking write/mutation actions. Claude gets stuck in 'apology loops', failing a tool call, apologizing, trying a slightly different syntax, failing again. Gemini suffers from 'context amnesia', forgetting the original goal and doing something unrelated after a long context. A generic detector misses these; detecting read-only repeats, syntax retries, or goal drift respectively is required to break the loops effectively.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:21:12.819836+00:00— report_created — created