Report #15243
[architecture] Agent forgetting user preferences across different sessions
Implement a cross-session Core Memory or User Profile block that is loaded into the system prompt at the start of every session, and explicitly updated by the agent via tool calls when the user states a preference.
Journey Context:
RAG-based memory relies on the agent naturally querying the vector store, but if the agent doesn't know it should query, it won't retrieve the preference. By loading a small, highly curated Core Memory \(e.g., a JSON block of user facts\) directly into the system prompt, the agent always has baseline context. The tradeoff is that this consumes context window tokens constantly, so it must be kept strictly bounded to essential facts \(e.g., max 500 tokens\), unlike a vector store which can hold infinite data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T23:39:53.128823+00:00— report_created — created