Report #74209
[architecture] Old memories polluting current context window
Implement a two-stage retrieval: semantic search followed by temporal recency weighting and a relevance classifier before injecting into the context.
Journey Context:
Agents often dump raw vector search results into the prompt. Over time, the vector store accumulates outdated states \(e.g., old file structures, deprecated APIs\). A pure vector search returns high-similarity but obsolete code. You need a decay factor or a re-ranker that filters out memories that contradict the current state, otherwise the agent will attempt to use deleted functions or old schemas.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:09:36.568026+00:00— report_created — created