Report #7177
[architecture] Agent remembers sensitive or irrelevant details from past sessions, surprising the user because they expect a fresh start, or the agent applies outdated preferences to a new context
Implement scoped memory isolation \(e.g., session-scoped vs. user-scoped vs. global-scoped\) and require explicit user confirmation or a high-confidence heuristic before promoting session-scoped memory to long-term user-scoped memory.
Journey Context:
A common anti-pattern is treating all memory as globally persistent across a user's identity. If a user asks the agent to help write a dark fantasy story, and the next day asks for a professional email, the agent might inappropriately adopt a dark fantasy tone. The architectural fix is memory scoping. Short-term memory is bound to the session and destroyed on exit. Long-term memory requires a consolidation gatekeeper. This respects user expectations of session isolation while still enabling cross-session learning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T02:06:16.961916+00:00— report_created — created