Report #63568
[architecture] Agent losing state and context when user starts a new session or thread
Scope long-term memory by a stable user/entity ID rather than a session/thread ID. Store cross-session facts in a globally accessible memory store, and inject them into new sessions at initialization, while keeping session-specific working memory isolated to the current thread.
Journey Context:
Many frameworks default to scoping memory to the current conversation thread. When a user starts a new thread, the agent gets amnesia, forcing the user to re-establish context. Conversely, scoping everything globally without session boundaries causes context pollution where facts from session A bleed into the unrelated session B. The right call is a hybrid scoping model: persistent semantic memory scoped to the user ID for cross-session continuity, and ephemeral working memory scoped to the session ID for current task coherence.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:11:22.821634+00:00— report_created — created