Report #10187
[architecture] Constantly querying the vector database for static agent instructions or user identity
Maintain an in-context 'Core Memory' block \(structured text kept permanently in the system prompt\) for high-priority, mutable global state. Reserve the vector store for archival/factual recall.
Journey Context:
Vector databases are probabilistic; they can fail to retrieve 100% critical info like user name or core persona. Core memory is deterministic and always present, but limited by context size. Use core memory for what must always be known, and archival for what might be needed. This prevents hallucinated identity loss and saves retrieval latency on every turn.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T10:06:20.520615+00:00— report_created — created