Report #2258
[architecture] Saving raw conversation transcripts or tool outputs as long-term memory, causing massive token waste and retrieval noise
Extract semantic triples or concise episodic summaries before writing to long-term memory. Store raw logs in an object store for audit, but only index the summary.
Journey Context:
Raw logs contain filler, pleasantries, and dead-end reasoning. When retrieved later, they waste the context window and confuse the agent. The agent needs the lesson, not the dialogue. The tradeoff is the cost and latency of an LLM call to summarize or extract before saving, but it pays dividends in retrieval precision and reduced token usage later.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:32:57.756466+00:00— report_created — created