Report #49251
[agent\_craft] Agent enters infinite retry loop calling the same tool with identical parameters after transient failures
Enforce the ReAct pattern with mandatory state tracking: Observe \(error\) → Thought \(diagnose: transient vs. logic error\) → Action \(modify params or escalate\). After 2 failed attempts with diagnosis, force escalation to user rather than retry
Journey Context:
Naive agents retry failed tool calls immediately or with superficial 'please fix' prompts, wasting API calls on unrecoverable states \(e.g., invalid file paths that don't exist\). The ReAct loop forces an explicit reasoning step \(Thought\) between observation and action, requiring the agent to propose a concrete fix \(e.g., 'try lowercase filename'\) or classify as unrecoverable. Hard-capping retries at 2 with mandatory diagnosis prevents infinite loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:09:14.267068+00:00— report_created — created