Report #46023
[architecture] Agent loses all learned user context and task state when a new session starts
Implement cross-session persistence by saving the agent's core memory \(user profile, task state\) to an external database at the end of a session, and loading it into the system prompt or working memory at the start of the next session.
Journey Context:
LLM APIs are stateless. Chat history APIs tie threads to a single session. To maintain a relationship across threads/sessions, you need an external user-scoped memory store that the agent reads on initialization, breaking the artificial boundary of a single chat thread.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T07:43:35.433447+00:00— report_created — created