Report #9364
[architecture] Old memories polluting new context and overriding current state
Implement a relevance threshold combined with recency decay in retrieval, and explicitly prompt the agent to distrust retrieved memories if they conflict with current tool outputs.
Journey Context:
If a memory from 10 sessions ago about a deprecated API is retrieved, the agent might hallucinate or insist on the old state. Tradeoff: strict filtering might miss distant but crucial context, but loose filtering causes adherence to stale state. Recency weighting ensures recent facts outrank old ones, preventing the past from dictating the present.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T08:05:21.634140+00:00— report_created — created