Report #71512
[architecture] The agent saves every single user utterance and system response to long-term memory, causing the vector database to bloat with low-value, redundant facts
Implement an importance or surprise scoring step before writing to long-term memory. Only persist memories that score above a threshold \(e.g., new facts, user preferences, corrections\).
Journey Context:
Naive memory architectures append every interaction to a vector DB. This leads to write amplification where the DB fills up with 'Hello', 'How can I help?', and duplicate facts. Retrieval then returns a mix of high and low signal, confusing the LLM. The tradeoff is an extra LLM call for scoring vs. storage and retrieval quality. By filtering writes based on an importance score, you ensure the long-term memory remains a high-signal, curated knowledge base rather than a noisy log.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:36:41.280641+00:00— report_created — created