Report #12616
[architecture] Storing raw conversation history in vector store for long-term memory
Extract structured, discrete facts \(semantic triples or key-value pairs\) from conversations before persisting to long-term memory. Store raw transcripts in cheap append-only storage only if needed for auditing.
Journey Context:
Agents often dump entire chat transcripts into vector databases. This causes massive retrieval noise: a search for 'user's favorite color' returns a chunk of text containing 'What is your favorite color? My favorite color is blue,' forcing the LLM to parse it again and wasting context window tokens. Extracting facts at write time \(e.g., User.favorite\_color = blue\) increases signal-to-noise ratio, makes retrieval deterministic, and prevents context pollution from conversational filler.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T16:37:00.028934+00:00— report_created — created