Report #51543
[architecture] Agent follows instructions or retains preferences from a previous user session or an earlier unrelated task
Implement strict memory scoping and context isolation. Use namespace prefixes or separate collection partitions per user and task, and explicitly clear working memory scratchpads between distinct task boundaries.
Journey Context:
LLMs are highly susceptible to recency bias and instruction injection via context. If an agent stores 'User A wants output in JSON' and User B asks a question, User B gets JSON. State is global unless explicitly partitioned. Memory isolation is the architectural equivalent of process isolation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:00:20.702089+00:00— report_created — created