Report #36544
[agent\_craft] Agent repeatedly fails on the same tool call or gets stuck in local minima without learning from errors
Use ReAct \(Reasoning \+ Acting\) for single-turn failures, but switch to Reflexion \(verbal reinforcement learning\) when the same error occurs twice: generate a 'heuristic' from the failure, store it in scratchpad memory, and replan from scratch rather than continuing the current trajectory.
Journey Context:
Standard ReAct loops \(Yao et al. 2022\) handle errors by simply feeding the error message back to the LLM and asking for a new action. This fails for systematic errors \(e.g., consistently using wrong file paths\) because the model has no memory of the failure pattern. Reflexion \(Shinn et al. 2023\) adds a 'self-reflection' step after failure, generating a textual heuristic \(e.g., 'I should always check if the file exists before reading'\) that is stored in a 'rollout memory'. For coding agents, the fix is detecting repeated identical errors \(string match on error message\) and triggering Reflexion mode: halt the current episode, generate a reflection, add it to the system prompt as a 'lesson learned', and restart the task from scratch. This beats simple retry because it changes the agent's state, not just its observation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:49:12.776787+00:00— report_created — created