Report #87480
[agent\_craft] Long-term memory vector database becomes bloated with noise, returning irrelevant past insights that pollute the current context
Only write to long-term memory when a specific, non-obvious insight is extracted, and implement a deduplication or 'forgetting' mechanism that deletes or overwrites outdated facts.
Journey Context:
Agents that automatically dump every step or observation into a vector DB create a 'write-heavy, read-noisy' system. When retrieving context for a new task, the DB returns vaguely similar but unhelpful past actions. Memory should be treated as a curated knowledge base, not a log. Writing to it should be harder than reading from it, ensuring only high-signal, generalized facts survive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:25:31.162516+00:00— report_created — created