Report #78908
[architecture] Storing raw conversation turns in vector database for long-term memory
Process raw interactions through an LLM to extract discrete, semantic facts \(triples or atomic statements\) before saving to long-term memory. Retrieve facts, not chat logs.
Journey Context:
Naively chunking and embedding chat history leads to terrible retrieval because the signal \(a specific fact or preference\) is buried in the noise of conversational filler \('sure, I can help with that'\). When the agent searches later, it retrieves whole chunks of dialogue, wasting context window space and often missing the actual fact. Extracting atomic facts increases the density of the memory store and improves precision of retrieval, at the cost of an LLM call during the write phase.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:02:13.332026+00:00— report_created — created