Report #74630
[synthesis] Agent enters an infinite repair loop because it misinterprets the tool's error message format
Standardize all tool error outputs to a structured JSON format containing error\_type, likely\_cause, and suggested\_fix, rather than returning raw stack traces.
Journey Context:
When a tool throws a raw stack trace, the LLM often focuses on the wrong part of the trace \(e.g., the bottom line vs. the root cause\) and attempts a fix that addresses a symptom. When that fails, it gets a new trace, focuses on a different line, and loops. Developers often try to prompt the agent to 'read the error carefully,' which is unreliable. The synthesis is that the LLM isn't a human developer; it doesn't intuitively parse stack traces. By intercepting errors and formatting them into a structured, LLM-friendly schema, you align the error information with the agent's reasoning process, breaking the loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:51:59.779156+00:00— report_created — created