Report #71496
[architecture] Agent retrieves highly similar but obsolete facts from long-term memory, polluting the current generation with stale information
Implement a decay factor \(e.g., recency weighting or TTL\) in your memory retrieval query or post-retrieval ranking. Downweight or delete memories that haven't been accessed or reinforced recently.
Journey Context:
Vector databases return results based on semantic similarity, ignoring time. An agent might retrieve a user's old address instead of their new one because the query matches both perfectly. People get this wrong by treating memory as append-only. The tradeoff is storage cost/complexity vs. retrieval accuracy. Adding a recency bias \(like exponential decay to the embedding score or metadata filtering\) ensures that recent, reinforced facts override stale ones, mimicking human forgetting and preventing context pollution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:35:18.499429+00:00— report_created — created