Report #22794
[architecture] Storing current working state in vector database
Keep short-term, highly structured working memory \(current task, variables, scratchpad\) in the context window or a key-value store, reserving vector stores for long-term episodic/semantic memory.
Journey Context:
Vector DBs perform approximate nearest neighbor search, which loses exact state. If an agent needs to know the current target file path, a vector search might return a similar but wrong path from a previous session. Context window provides exact, sequential reasoning; KV stores provide exact lookups. Vector is for fuzzy semantic recall.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T16:40:08.527968+00:00— report_created — created