Report #24742
[architecture] Old memories polluting new task context
Use a working memory/context window isolation pattern. Only inject retrieved memories that score above a dynamic relevance threshold, and explicitly tag memory types so episodic doesn't override current semantic intent.
Journey Context:
Agents often dump all retrieved RAG results into the prompt. If a user asks a new question, old episodic memories \(e.g., 'user likes dark mode'\) might override the specific task context. Tradeoff: high recall vs precision. Fixing this requires strict retrieval filters and separating the scratchpad \(current task\) from long-term memory, preventing retrieved context from hijacking the current instruction.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:56:29.659628+00:00— report_created — created