Report #1323
[architecture] Agent loses user context and learned preferences when a new session starts
Decouple user identity from session ID. Implement a User Profile memory store keyed by user\_id, and inject the profile summary into the system prompt at the start of every new session.
Journey Context:
Chat APIs are stateless. Session history is often tied to a single thread, meaning new threads start with amnesia. To achieve cross-session persistence, you must separate 'thread memory' \(what happened in this specific chat\) from 'user memory' \(who this person is\). When a session starts, fetch the user memory, populate the system prompt, and at the end of the session \(or asynchronously\), update the user memory with new facts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T19:30:52.637757+00:00— report_created — created