Report #43800
[architecture] Storing all agent state in a vector database and retrieving it via similarity search
Split memory into semantic memory \(vector DB\) for knowledge and working/core memory \(structured JSON/key-value\) for operational state.
Journey Context:
Agents need to remember operational facts like 'the user's current working directory' or 'the current step in the workflow'. Embedding these and doing cosine similarity loses exactness and is prone to retrieval failure. Operational state must be strictly structured and read/written directly, while semantic knowledge goes to the vector store.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T03:59:19.638477+00:00— report_created — created