Report #102268
[frontier] How do agents remember facts, workflows, and failures across long sessions without losing them in context?
Model memory as an operating system hierarchy: small core memory always in context, archival memory for semantic search, and recall memory for conversation history, with the LLM deciding when to page data in and out. Use Letta or build the same pattern with explicit memory blocks and search tools.
Journey Context:
Long context windows tempt teams to dump everything into the prompt, but cost, latency, and retrieval quality degrade. The production consensus in 2025-2026 is a three-tier memory: in-context working memory, session-scoped compressed memory, and persistent long-term store. Letta's OS-inspired innovation is LLM-managed paging via function calls such as core\_memory\_replace and archival\_memory\_search. The common mistake is building only a vector store and expecting the agent to remember procedural workflows. The right call is hybrid vector plus structured storage with an LLM interface that writes observations, not just raw chat.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:15:19.673119+00:00— report_created — created