Report #82910
[architecture] Agent repeatedly calls the same tool or asks the same question because it doesn't track its own executed actions
Maintain an explicit 'Action Log' as part of the working memory. Before executing a tool, check the log. After executing, append the result summary to the log.
Journey Context:
Without an explicit action log, the agent relies on the LLM's implicit attention over the chat history. As history grows, the LLM 'forgets' it already fetched a file and does it again, wasting tokens and time. The fix is forcing the agent to read/write a structured state array. Tradeoff: Consumes output tokens to maintain the log, but prevents infinite tool-calling loops and reduces API spend.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:45:21.968983+00:00— report_created — created