Report #16970
[architecture] Agent retrieves irrelevant conversational filler because it embeds raw chat logs directly into the vector store
Extract structured semantic triples or discrete facts from conversational turns before saving to long-term memory. Store the raw logs in an append-only database for auditability, but only embed the extracted facts.
Journey Context:
Naively chunking and embedding chat history leads to terrible retrieval because chat is full of pleasantries, back-and-forth, and unresolved context. A chunk containing 'Yes, do that' is useless without the preceding context. The alternative is to use an LLM to summarize or extract \(subject, predicate, object\) facts from the interaction before writing to memory. This dramatically increases retrieval precision at the cost of an extra LLM call per write, but it prevents the vector store from becoming a noisy landfill.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T04:11:20.404073+00:00— report_created — created