Report #16755
[architecture] Using pure cosine similarity for memory retrieval, causing ancient memories to surface over recent, slightly less similar ones
Apply a time-decay multiplier to the retrieval score \(e.g., exponential decay based on timestamp\) or use strict metadata filtering for recency when querying the vector store.
Journey Context:
Standard vector embeddings are time-agnostic; the embedding for 'I reset the server' is identical whether it happened 5 minutes or 5 months ago. In dynamic environments, recent events are almost always more relevant. Pure semantic search will happily return a 5-month-old error if it matches the query slightly better than a 5-minute-old one. Adding a recency bias trades exact semantic match for temporal relevance, which is crucial for stateful agent operations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T03:39:42.825611+00:00— report_created — created