







i can’t help but think we’re far from nailing memory systems this one here is extremely interesting. two LLMs at once, one just managing and surfacing memory for the other
Asa
I'm not a fan of the decoupled 'memory retrieval → task execution' loop, so my agent has a subconscious background thread that looks for relevant, unique memory context in its experiential database while it runs and injects it on top of the live context window.
May 17, 2026 at 11:20 AM
The rebel alliance
This blog is co-authored with Zoe Weinberg and Matt Hawes at ex/ante, and is a follow-up to our first blog post on the topic, 'You don't own your memory.' We need an open architecture that puts us in control of our memories while making their exploitation technically impossible. But how will this shift happen? In order to discover possible implementations, we must understand how our data informs LLMs. The three predominant context engineering techniques are prompt design, retrieval-augmented ...

MemGPT
Memory-GPT (MemGPT) - Towards LLMs as Operating Systems - Teach LLMs to manage their own memory for unbounded context!
Shlok Khemani on Twitter / X
Super interesting that eve doesn't ship with any long-term or cross-session memory (yet). The main context-management lever out of the box is conversation compaction. This is unlike OpenClaw and Hermes, each of which comes with a default opinionated memory implementation. https://t.co/DDIyc4rFtW— Shlok Khemani (@shloked) June 17, 2026
nanomem: An Extremely Simple, Inference-Time Memory Module
nanomem is an extremely simple, user-owned memory module that casts memory management as LLM calls / agent loops on a markdown file tree. You interact with the tree with natural language commands like nanomem add <fact>, nanomem retrieve <query>, and nanomem import <chatgpt>. As such, nanomem is by design interpretable, partitionable, portable, and versioned.
MemOS: An Operating System for Memory-Augmented Generation (MAG) in Large Language Models
Large Language Models (LLMs) have emerged as foundational infrastructure in the pursuit of Artificial General Intelligence (AGI). Despite their remarkable capabilities in language perception and generation, current LLMs fundamentally lack a unified and structured architecture for handling memory. They primarily rely on parametric memory (knowledge encoded in model weights) and ephemeral activation memory (context-limited runtime states). While emerging methods like Retrieval-Augmented Generation (RAG) incorporate plaintext memory, they lack lifecycle management and multi-modal integration, limiting their capacity for long-term knowledge evolution. To address this, we introduce MemOS, a memory operating system designed for LLMs that, for the first time, elevates memory to a first-class operational resource. It builds unified mechanisms for representation, organization, and governance across three core memory types: parametric, activation, and plaintext. At its core is the MemCube, a standardized memory abstraction that enables tracking, fusion, and migration of heterogeneous memory, while offering structured, traceable access across tasks and contexts. MemOS establishes a memory-centric execution framework with strong controllability, adaptability, and evolvability. It fills a critical gap in current LLM infrastructure and lays the groundwork for continual adaptation, personalized intelligence, and cross-platform coordination in next-generation intelligent systems.

Instant LLM Updates with Doc-to-LoRA and Text-to-LoRA
Recent LLM agents have shown impressive capabilities on complex computer use and long-horizon tasks. Yet, they still struggle with long-term memory and adaptation--two of the most important cognitive capabilities that still limit LLMs today. Without long-term memory, users have to provide LLMs with relevant content at the start of every new session, creating friction, discontinuity, and longer time-to-response. Additionally, due to the lack of adaptation, they do not learn from mistakes or user preferences from previous sessions, making each interaction as cumbersome as the first. Traditionally, these two problems are tackled by "updating" the model.
Compiling knowledge, not retrieving it: a hands-on deep dive into llm-wiki-compiler
The thesis of this piece is simple and uncomfortable: the problem of making an LLM “remember” what you’ve read isn’t solved with more…
The Memory Walled Garden
The gap between first and third party memory systems

Comparing the memory implementations of Claude and ChatGPT
Shlok Khemani has been doing excellent work reverse-engineering LLM systems and documenting his discoveries. Last week he wrote about ChatGPT memory. This week it's Claude. Claude's memory system has two …
Understanding memory management
Learn MemGPT memory management techniques for controlling LLM context windows with in-context and external storage.

Inference Time Memory Module | Research | Tiles
Simple inference-time memory module that treats memory management as a series of LLM calls and agent loops over a markdown-based file tree.
On the Way to LLM Personalization: Learning to Remember User Conversations
This paper was accepted at the Workshop on Large Language Model Memorization (L2M2) 2025. Large Language Models (LLMs) have quickly become…

mem-agent: Equipping LLM Agents with Memory Using RL
The insights and the technical report behind Mem-Agent, our 4B model for persistent memory in LLMs
something that has come up fairly recently with LLMs - for coding, specifically - is that it’s become a lot easier to burn stupefying amounts of tokens on stuff very fast, with agents running 24/7 or managing more agents (see: Yegge’s Gas Town) even with low inference costs that adds up in a hurry
Jesse Felder
‘While some cling to the promise of an AI “revolution,” the cost of adoption is proving a stubborn bottleneck. These developments also suggest that the economics of replacing human labor with AI may be more complicated than some early forecasts originally implied.’ fortune.com/2026/05/22/microsoft-ai-cost-…