Report #1655
[architecture] Agent fails to remember facts across turns because it only has a read-path for memory, lacking an automated write-path
Architect a dual-path memory system where every LLM response is post-processed by an extraction model that identifies novel, durable facts and upserts them into the memory store. Do not rely on the agent to explicitly decide to call a save-memory tool for routine facts.
Journey Context:
A common mistake is giving an agent a save\_memory tool and expecting it to use it correctly. LLMs are lazy and often skip the tool call, leading to amnesia. The alternative is a background extraction pipeline \(write-path\) that runs on every user message and agent response. The tradeoff is cost and latency \(an extra LLM call per turn\) versus reliability. For high-signal memory, the automated write-path is the right call because relying on the agent's explicit function calling for basic state persistence is notoriously unreliable and leads to fragmented memory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T06:32:40.113571+00:00— report_created — created