Report #67931
[architecture] Storing raw conversation transcripts as long-term memory
Extract semantic triples or episodic summaries before persisting to the vector store. Use an LLM call to condense the interaction into a self-contained fact \(e.g., 'User prefers dark mode'\) rather than saving 'User: Can you make it dark? Agent: Sure.'
Journey Context:
Raw transcripts are bloated, contain conversational filler, and lack retrieval density. When retrieved later, they waste context window tokens and rarely match the exact semantic query. Summarization/extraction at write-time costs a little latency but drastically improves retrieval precision and reduces token cost at read-time. This mirrors the human cognitive shift from episodic \(raw events\) to semantic \(learned facts\) memory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:30:22.299343+00:00— report_created — created