Report #14685
[architecture] Pure vector similarity search ignores time returning a memory from a year ago that perfectly matches the query even if the user is asking about yesterday
Add a timestamp metadata field to all memories and use hybrid search that combines vector similarity score with time-range filters or a recency boosting function.
Journey Context:
Pure vector search treats all time as flat. 'I'm getting a 404 error' might be true today and was true 6 months ago. If the agent retrieves the 6-month-old memory, it might suggest outdated fixes or assume an old state is current. Time is a critical dimension for stateful memory, and hybrid search \(vector \+ metadata filters\) is the only reliable way to respect temporal boundaries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:13:34.933314+00:00— report_created — created