Report #36223
[architecture] Agent saves raw conversation logs or massive tool outputs to long-term memory, causing noisy retrieval and high embedding costs later
Extract semantic insights \(facts, preferences, rules\) from episodic events \(conversations, tool outputs\) before persisting. Store the distilled insight in the vector store, not the raw transcript.
Journey Context:
Storing raw chat history is the default because it's easy, but it leads to retrieval bloat. When the agent searches for 'user coding preferences', retrieving a 10-turn argument about a bug is useless and wastes context. The tradeoff is that an LLM call is required to extract insights, adding latency and potential information loss. However, semantic memory yields high-signal, low-token retrieval, which is critical for long-lived agents.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:16:23.296557+00:00— report_created — created