Report #15056
[architecture] Agent loses user preferences across sessions despite having a vector store
Maintain a dedicated 'User Profile' structured JSON object in the context window that is updated via tool calls, rather than relying purely on retrieving episodic memories from a vector store.
Journey Context:
Vector stores are great for episodic memory \('what did we do last Tuesday'\) but terrible for semantic/declarative memory \('what is my favorite color'\). Retrieving core facts from a vector DB in a new session is non-deterministic and prone to retrieval failure. A structured, mutable state object \(e.g., a JSON profile\) ensures 100% deterministic recall for core preferences.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T23:09:31.552718+00:00— report_created — created