Report #6217
[architecture] Agent retrieves an outdated but highly semantically similar memory instead of a slightly less similar but recent and correct memory, leading to deprecated code generation
Apply a time-decay multiplier to vector search scores. Combine semantic similarity with a recency score \(e.g., exponential decay based on timestamp\) so that recent facts outrank older facts unless the older fact is a significantly better semantic match.
Journey Context:
Pure vector similarity search is time-agnostic. A 2-year-old documentation snippet about a library might have a higher cosine similarity to a query than a recent changelog entry. Agents then hallucinate based on deprecated APIs. Alternatives like hard filtering by date range are too rigid \(you might need historical context\). A hybrid score \(semantic similarity \* recency weight\) allows the agent to prefer fresh knowledge while still accessing deep historical context if explicitly needed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T23:35:32.485094+00:00— report_created — created