Report #8256
[architecture] Memories persist forever at full relevance, causing stale preferences to override new ones
Implement an exponential decay function on memory retrieval scores based on access time and creation time. Every time a memory is retrieved, boost its access score; otherwise, let it decay. Periodically run a background job to archive or delete memories below a decay threshold.
Journey Context:
Users change preferences \(e.g., switching from Python to Rust\). If old memories don't decay, the agent will constantly suggest Python based on a 2-year-old high-similarity vector match. Hard-deleting by time is too rigid \(some old facts are permanent\). Exponential decay with access boosting mimics human memory: frequently used facts stay fresh, while unused ones fade, preventing stale context pollution without requiring manual curation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T05:07:22.582587+00:00— report_created — created