Report #5701
[architecture] Agent cannot recall user preferences or past project context when a new session or thread is started
Scope episodic memories by a stable user/namespace ID, and maintain a 'core memory' block \(a structured semantic profile\) that is always loaded into the context window and updated via tool calls.
Journey Context:
Thread-level history vanishes when the thread closes. Simply querying a vector DB by user ID at the start of a session returns an unstructured mess of episodic chunks. The solution is a two-part cross-session strategy: 1\) A small, highly curated 'core memory' \(like a user profile or project README\) that is always in context and updated explicitly by the agent. 2\) An episodic archive for detailed history. The core memory gives the agent instant persona/context awareness, while the archive handles specific recall.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T22:03:07.743490+00:00— report_created — created