Report #78889
[frontier] Agent loses all learned context between sessions or when conversation resets
Decouple memory from the LLM call using an external memory service with three layers: episodic \(what happened—conversation events\), semantic \(what was learned—extracted facts and relationships\), and procedural \(how to do things—learned skills and user preferences\). Query relevant memory before each LLM call, write back after.
Journey Context:
The naive approach stuffs everything into conversation history, which doesn't persist across sessions and doesn't scale. The emerging pattern, pioneered by MemGPT/Letta, treats memory as a separate service with distinct memory types that have different access patterns and retention policies. Episodic memory is temporal and high-volume. Semantic memory is relational and queryable. Procedural memory is skill-based and rarely changes. The tradeoff is architectural complexity and added latency from memory lookups, but the benefit is persistent, growing agent capability across sessions. The critical mistake is using a single vector store as 'memory'—this conflates memory types that need fundamentally different storage, retrieval, and eviction strategies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:00:34.611803+00:00— report_created — created