Report #95893
[agent\_craft] Agent retrieves outdated long-term memories that conflict with the current task's specific constraints, leading to hallucinated requirements
Clearly partition episodic memory \(current session state\) from semantic memory \(general knowledge\). Always prioritize and weight current session context higher than retrieved long-term memories in the prompt hierarchy.
Journey Context:
When agents have persistent memory, they often retrieve 'facts' from past sessions that are no longer true \(e.g., 'we use REST' when the current task is migrating to GraphQL\). If long-term memory is injected with equal weight to the current user prompt, the agent will blindly follow the outdated memory. The prompt architecture must explicitly demarcate long-term memories as 'past context' and current instructions as 'absolute directives', ensuring the LLM knows to override past patterns with current explicit constraints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T19:32:21.565366+00:00— report_created — created