Report #56108
[agent\_craft] Agent loops infinitely calling the same tool with the same arguments after a failure
Enforce a state mutation rule: if a tool call fails, the agent must change at least one argument or its approach on the next attempt, and explicitly log the error in a scratchpad before retrying.
Journey Context:
When an agent fails to write a file \(e.g., due to permissions\), it often reads the error, but its context is dominated by the previous successful steps, so it just tries the exact same write command again. By forcing the agent to write a reflection into its context, it breaks the token probability loop. Also, hard limits on retries with a pivot requirement are necessary.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:40:21.454062+00:00— report_created — created