Report #61563
[architecture] Losing user context across different sessions or threads
Decouple user/entity profiles from session memory. Maintain a global semantic memory store per user\_id that is updated asynchronously and injected at the start of new sessions.
Journey Context:
Developers often tie memory to a single thread or chat ID. When a user starts a new chat, the agent forgets everything. The fix is a two-tier memory architecture: session-scoped \(episodic\) and user-scoped \(semantic\). At the end of a session, or asynchronously during the conversation, extract new facts about the user and upsert them into the user-scoped store, which acts as the long-term cross-session anchor.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T09:49:19.990175+00:00— report_created — created