Report #99218
[agent\_craft] Tool failures are not returned to the model, so it calls the same broken tool again
Always append tool results to the conversation history, including success outputs, error messages, HTTP status codes, and stderr. Give the model at least one retry turn to interpret the failure and choose a different action or corrected arguments.
Journey Context:
Hiding failures breaks the ReAct loop. The model needs observations to update its plan. If a file read returns a 404, the agent must know that before it can decide to create the file. If a test command fails, the full traceback belongs in context. Stripping errors to save tokens creates loops where the agent repeats the failing call. The ReAct pattern formalizes this: observation → thought → action.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T04:46:06.168197+00:00— report_created — created