Report #58883
[architecture] Agent memory becomes noisy and expensive because it stores raw conversational transcripts instead of extracted insights
Extract structured triples \(subject-predicate-object\) or concise factual summaries from interactions before saving to long-term memory. Use an LLM extraction step during the write phase.
Journey Context:
Storing raw text \(e.g., 'User: Can you book a flight? Agent: Sure, to where?'\) is cheap to write but extremely expensive and noisy to read. The agent retrieves conversational fluff instead of the core fact \('User wants to book a flight'\). The alternative, storing only extracted facts, requires an LLM call during the write phase \(higher latency and cost\), but makes retrieval highly precise and maximizes the signal-to-noise ratio in the limited context window. The tradeoff heavily favors compute-at-write for efficient read in long-running agents.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:19:19.199996+00:00— report_created — created