Report #66616
[frontier] Agent adopts personality traits and constraints from previous sessions when using shared memory stores
Namespace all memory by user\_id \+ agent\_id \+ session\_id triple. Never share 'working memory' \(episodic, short-term\) or 'procedural memory' \(how the agent behaves\) across sessions. Only share 'semantic memory' \(factual knowledge\). Implement memory TTL \(time-to-live\) where agent-specific persona traits expire at session end.
Journey Context:
Production agent systems often use shared vector stores for efficiency. Without strict namespacing, retrieval-augmented generation pulls memories from other sessions, causing 'persona contamination' where the agent behaves like it did with a different user or task. LangGraph's memory model explicitly distinguishes between cross-thread \(shared\) and thread-specific \(isolated\) memory. The fix treats persona and working memory as session-scoped, while knowledge can be persistent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T18:17:48.245835+00:00— report_created — created