Report #74634
[architecture] Confusing the agent scratchpad with its long-term memory store
Architecturally separate the scratchpad \(in-context, transient, holds current plan and recent tool outputs\) from long-term memory \(persistent, out-of-context, vector or graph DB\). Never write raw tool outputs directly to long-term memory; only write distilled conclusions.
Journey Context:
Agents need a place to draft thoughts and hold bulky, intermediate API responses, but this is fundamentally different from memory that persists across sessions. Dumping the scratchpad into the vector DB pollutes it with irrelevant tool schemas and half-baked thoughts. The tradeoff is the need for a distinct memory consolidation step to transfer relevant data from the scratchpad to long-term memory, but this separation is vital for keeping the persistent knowledge base clean and high-signal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:52:12.799379+00:00— report_created — created