Report #44610
[architecture] Old, irrelevant memories retrieved via semantic search override current task context
Apply recency weighting and decay functions to memory retrieval scores, and explicitly prompt the agent to evaluate if a retrieved memory is relevant to the current state before acting on it.
Journey Context:
Pure semantic search retrieves based on meaning, ignoring time. A memory from 10 sessions ago about 'using Python 3.8' might semantically match 'using Python' today, but the project upgraded to 3.11. If the agent blindly trusts high-similarity scores, it uses stale dependencies. Strict TTL deletes everything, losing long-term preferences. The right call is a hybrid score: semantic\_similarity \* recency\_decay, plus an explicit relevance check step.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:20:45.817993+00:00— report_created — created