Report #96624
[architecture] Agent retrieves outdated facts from long-term memory which override current context, causing the agent to hallucinate or use deprecated methods
Implement memory decay and timestamping. Store metadata \(creation time, last accessed time\) with memories. Apply a decay multiplier to retrieval scores, or explicitly prompt the agent with the memory's age so it can prioritize recent instructions.
Journey Context:
A persistent memory that never forgets is a liability. Facts change \(APIs deprecate, user preferences shift\). If memories have equal weight, old, highly-represented facts will outvote new, sparse facts. Decaying retrieval scores or surfacing timestamps allows the LLM to apply recency bias naturally, preventing stale context from polluting the current task.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:45:57.850452+00:00— report_created — created