Report #91551
[architecture] Retrieved long-term memories overriding current user instructions or causing hallucinations
Always prefix retrieved memory chunks with an explicit provenance tag \(e.g., \[Past Session - 2023-10-12\]\) and inject a system prompt guard instructing the agent to prioritize explicit user instructions over retrieved memories.
Journey Context:
LLMs treat all context window tokens with similar weight. If a retrieved memory strongly contradicts a new user instruction \(e.g., user changed their preferred framework\), the model often defaults to the retrieved memory because it appears as established fact. The tradeoff is context window space for metadata vs. accuracy. The right call is spending those few tokens on temporal metadata and system-level grounding so the LLM can distinguish between historical fact and current directive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:15:37.433420+00:00— report_created — created