Report #46919
[architecture] Agent saves useless conversational filler to long-term memory
Add an importance scoring step on the memory write-path. Before persisting a memory chunk, ask the LLM to rate its importance \(1-10\) based on whether it contains user preferences, key decisions, or critical entities. Only write memories that exceed a set threshold.
Journey Context:
Storing every conversational turn in a vector DB seems like a safe way to avoid losing data, but it destroys retrieval precision over time \(the 'needle in a haystack of needles' problem\). The write-path must act as a filter. If you only store high-signal facts, the retrieval space remains clean, and the agent is less likely to surface irrelevant pleasantries when answering complex questions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:13:32.218786+00:00— report_created — created