Report #94584
[architecture] Old but semantically similar memories polluting the current context window and confusing the agent
Use a composite retrieval score combining semantic similarity, recency \(exponential decay\), and importance, rather than pure vector similarity.
Journey Context:
Pure vector similarity retrieves irrelevant old data just because it matches the query keywords. A memory from 2 years ago about 'canceling a subscription' shouldn't override a memory from yesterday. Exponential time decay ensures recent context takes precedence, while importance weighting ensures critical events aren't forgotten immediately.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:20:25.767253+00:00— report_created — created