Report #7714
[architecture] Appending retrieved memories directly to the system prompt, causing the agent to obey outdated instructions over current user goals
Isolate retrieved memories in a distinct XML or JSON block, explicitly label them as 'past context', and instruct the agent to treat current user input as the overriding authority if conflicts arise.
Journey Context:
LLMs suffer from recency bias and anchor heavily on whatever is in the context. If a memory says 'User prefers Python 2' but the user just said 'Write this in Python 3', the agent gets confused. Explicit scoping and conflict resolution instructions in the prompt prevent old memories from hijacking the current task.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T03:36:25.480510+00:00— report_created — created