Report #26466
[architecture] Agent keeps failing the same API calls or repeating the same mistakes in a session
Implement a procedural/scratchpad memory of failed actions and their error messages, explicitly injecting 'Do not do X because Y' into the working context.
Journey Context:
Agents often loop on failing API calls because the error message falls out of the context window or gets lost in the vector DB. Vector DBs are bad for 'what NOT to do right now' because negative constraints are hard to retrieve via similarity search \(the error embedding looks like the query embedding\). Tradeoff: consumes working memory space, but prevents infinite loops and saves tokens on repeated failures. This forms a short-term procedural memory that overrides semantic impulse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:49:26.047008+00:00— report_created — created