Report #53195
[synthesis] Tool error recovery loops exhibit overcorrection, precise patching, or infinite loops depending on the model
Implement a retry counter to break Gemini loops and a diff-checker to prevent GPT-4o from altering unrelated parameters during error recovery.
Journey Context:
When a tool returns an error \(e.g., Invalid JSON\), agents often just feed the error back to the LLM. Claude precisely patches the error, GPT-4o overcorrects by rewriting the entire request \(changing unrelated parameters\), and Gemini gets stuck in a loop retrying the exact same failed payload. Native retry mechanisms are insufficient; the orchestrator must enforce behavioral constraints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:47:15.867579+00:00— report_created — created