Thematic explorer
Agentic Memory Systems
151 papers · 9 themes
← All collections151 papers shown
Procedural & Skills
Procedural Memory & Skill Libraries for LLM Agents (Voyager-style skill libraries, agent workflow memory, skill induction/evolution, case-based procedural reuse for coding/tool-use/GUI agents)
Key threads
- Two representations of procedural memory compete: executable code-skill libraries (Voyager, SkillClaw, Skill1, SkillDroid) versus natural-language workflows/manuals/rules (Agent Workflow Memory, AutoManual). Benchmarks must evaluate both, and they differ in how they fail (compilation/composition errors vs ambiguous-instruction drift).
- The field is shifting from episodic, single-task scoring toward longitudinal evaluation of accumulation and reuse across trajectories (SEA-Eval, SkillEvolBench, AWM's widening train-test-gap protocol). The acquisition-then-frozen-deployment split is emerging as the standard methodological pattern.
- Library maintenance is itself the hard problem: selection, utilization, and distillation must be co-managed or the library accrues episode-specific drift, clutter, and cap saturation (Skill1, SkillEvolBench, MUSE-Autoskill). Library health (size, growth rate, high-frequency-skill coverage) is becoming a measured quantity, not just a side effect.
- A credibility crisis around attribution: updating a skill/harness is routinely conflated with benefiting from it (Harness Updating Is Not Harness Benefit), and raw-trajectory reuse frequently beats distilled skills (SkillEvolBench). Controlled, ablated eval design is required to attribute gains to procedural memory rather than to base capability or mere activity.
- Generalization axes are proliferating beyond in-distribution reuse: cross-task, cross-website/domain (AWM), cross-domain transfer in coding agents (Memory Transfer Learning), and adversarial/compositional deployment shifts (SkillEvolBench). Procedural-memory benchmarks increasingly define explicit distribution-shift conditions.
- Reuse value is multi-objective: success rate plus inference/compute cost (SkillDroid's compile-once reuse, Skill1's wall-clock and library-size analyses, ClawTrace's per-step cost tracing). Efficiency is becoming a co-equal eval metric alongside task success.
Open gaps
- No standardized, shared procedural-memory benchmark with frozen held-out deployment splits is established - SkillEvolBench and SEA-Eval are brand-new (2026, ~0 citations) and not yet consolidated; this work could define the canonical harness rather than adopt one.
- Attribution methodology is immature: most systems report only end-task success and conflate harness/skill updates with capability gains (per Harness Updating Is Not Harness Benefit). There is no widely adopted control protocol (no-skill, raw-trajectory, curated-prior baselines) for isolating procedural-memory contribution.
- Synthetic-data pipelines for procedural memory are nearly absent: role-conditioned task families with known shared latent procedures (SkillEvolBench builds 180 by hand) are not generated at scale, leaving no programmatic way to control procedure overlap, distractor skills, or compositional depth in eval sets.
- Library-health and anti-erosion metrics are ad hoc: drift, clutter, interference, and cap saturation are observed but not standardized into reusable diagnostics, so cross-system comparison of library quality is not possible.
- Procedural memory is benchmarked in silos (web nav, GUI, coding, embodied) with little cross-domain transfer evaluation; how a skill library acquired in one domain helps or harms in another (Memory Transfer Learning) lacks a multi-domain harness.
- The semantic/episodic/procedural memory split this work targets is rarely co-evaluated: procedural-skill benchmarks seldom test interaction with episodic recall or semantic facts within the same trajectory, so integrated multi-memory-type eval tasks are an open design space.
- SkillEvolBench: Benchmarking the Evolution from Episodic Experience to Procedural Skills
Synthesis
Plain-language abstract SkillEvolBench is a benchmark designed to test whether AI agents can turn their own task experience into reusable procedural skills — not just replay what they did once, but extract general instructions a future agent can follow on related tasks. It contains 180 tasks across six real-world work domains and evaluates ten large language model configurations under three agent frameworks, comparing skill-based conditions against baselines that use no skills or raw trajectory replay.
Motivation LLM agents accumulate detailed records of how they solved past tasks, but it is unclear whether that experience can be distilled into compact, reusable procedures rather than task-specific patches. Prior work either studied skill use (given curated skills) or experience reuse (replaying trajectories), leaving a gap: can agents themselves convert noisy one-off episodes into external skill artifacts that help on harder, related tasks they have not yet seen?
Methodology The benchmark organizes 180 tasks into six environments covering code modification, API orchestration, data processing, document transformation, research synthesis, and communication operations, with five task families per environment. Each family follows a six-role arc: three acquisition tasks (canonical, enriched, variant) used to build the skill library, and three frozen deployment tasks (context-shift, adversarial, composition) where no further skill updates are allowed. Agents operate in Self-Generated or Curated-Start settings; a separate Skill Author step uses compacted trajectories and structured verifier feedback to decide whether to write a new skill, revise an existing one, or leave the library unchanged. Controls include a No-Skill condition and a Raw-Trajectory condition that provides the original episode directly.
Results Across ten model configurations and three agent harnesses, current agents adapt locally but rarely form robust reusable skills. Raw-trajectory reuse frequently outperforms distilled skills, indicating that current abstraction procedures discard contextual and procedural cues that remain useful for future tasks. The always-update curated variant showed the strongest average gain (+0.78 percentage points in frozen evaluation success rate), but benefits were model-specific: GPT-5.4 improved by +6.7 percentage points and Opus 4.5 by +4.4 percentage points, while Gemini 2.5 Pro was harmed by most variants (average -3.70 percentage points). Adding more skills or larger resource libraries did not reliably help and often introduced episode-specific drift and procedural clutter without improving deployment success.
- Voyager: An Open-Ended Embodied Agent with Large Language Models
Synthesis
Plain-language abstract VOYAGER is an AI agent that plays Minecraft indefinitely on its own, continuously learning new skills without any human guidance or changes to its underlying model. It uses a large language model (GPT-4) to decide what to do next, write executable code to carry out actions, and build up a growing library of reusable skills — all through text prompting alone.
Motivation Prior AI agents using reinforcement learning or imitation learning struggle to explore open-ended environments systematically, generalize across tasks, or accumulate skills over time without forgetting earlier ones. There was no agent capable of lifelong, self-directed learning in a complex open-world setting without human intervention or model retraining.
Methodology VOYAGER has three components that work together: an automatic curriculum in which GPT-4 proposes progressively harder tasks based on the agent's current inventory and world state; an iterative prompting mechanism that feeds environment feedback, execution errors, and self-verification results back to GPT-4 to refine the generated action code; and a skill library that stores successful action programs indexed by text embeddings, enabling retrieval and composition of past skills for new situations. The agent interacts with GPT-4 purely through blackbox API queries, requiring no gradient-based fine-tuning.
Results VOYAGER obtains 3.3 times more unique items, travels 2.3 times longer distances, and unlocks key tech-tree milestones up to 15.3 times faster than the prior state of the art. It also demonstrates zero-shot generalization: after learning skills in one Minecraft world, it can transfer that skill library to a new world and solve novel tasks from scratch, while baseline methods fail to generalize.
- Agent Workflow Memory
Synthesis
Plain-language abstract This paper introduces Agent Workflow Memory (AWM), a method that teaches language model-based web agents to extract reusable task routines — called workflows — from past experience and apply them to guide future actions. Rather than treating each task in isolation, AWM lets agents build up a growing library of skills, from simple steps like finding a place by name to more complex multi-step procedures composed from earlier workflows.
Motivation Current language model agents struggle with long, complex web navigation tasks because they process each task independently and do not learn from past successes or failures. They lack the ability to extract and reuse common task patterns across similar contexts, making them brittle when the task environment changes even slightly.
Methodology AWM operates in two modes: offline, where it extracts workflows from annotated training trajectories before test time, and online, where it induces workflows on the fly from self-generated predictions judged correct by an evaluator. The method was evaluated on two major web navigation benchmarks — Mind2Web (1000+ tasks across 200+ domains) and WebArena (execution-based evaluation covering travel, shopping, social media, and other domains) — using language model agents that maintain and grow a memory of induced workflows over time.
Results AWM improved baseline success rates by 24.6% relative on Mind2Web and 51.1% relative on WebArena, while also reducing the number of steps needed to solve WebArena tasks. It outperformed methods that use human-expert-written workflows by 7.9% on WebArena. In cross-task, cross-website, and cross-domain generalization evaluations, online AWM surpassed baselines by 8.9 to 14.0 absolute percentage points, with the performance gap growing as the train-test distribution divergence increased — reaching as high as 22.5 points after rolling over only tens of examples.
- SEA-Eval: A Benchmark for Evaluating Self-Evolving Agents Beyond Episodic Assessment
Synthesis
Plain-language abstract This paper introduces SEA-Eval, the first benchmark designed to evaluate AI agents that improve themselves over repeated tasks. Most current benchmarks treat each task in isolation, resetting the agent's memory each time — which makes it impossible to measure whether an agent is genuinely learning from experience or just repeatedly solving problems from scratch. SEA-Eval is built around a new category of agent called a Self-Evolving Agent (SEA), which maintains persistent memory across tasks and uses past experience to get faster and cheaper over time.
Motivation Existing AI agent benchmarks evaluate each task as an isolated episode, resetting memory at every task boundary. This design structurally prevents them from detecting cross-task learning. Two agent frameworks can achieve identical success rates while differing dramatically in whether they are genuinely evolving — one accumulating efficient strategies, the other simply re-doing zero-shot reasoning every time. Current benchmarks produce a 'capability illusion' and cannot distinguish these fundamentally different behaviors.
Methodology The authors formalize the Self-Evolving Agent concept and its core architecture — the Evolutionary Flywheel, a closed loop of execution, experience distillation, and augmented re-execution. They construct a dataset of 32 atomic tasks across three difficulty tiers, composed into three types of sequential task streams (correlated, orthogonal, and implicit intent) under two noise conditions. Two primary metrics are used: success rate (SR) and token consumption (T), where the trajectory of T across sequential task repetitions is the key signal of genuine evolution. They then empirically evaluate two leading agent frameworks, OpenClaw and GenericAgent, using this benchmark.
Results Both frameworks achieved 100% task success rate in static evaluation, but their token consumption differed by roughly sevenfold in aggregate — OpenClaw consumed 27,364K tokens across all tasks while GenericAgent consumed only 3,918K tokens, with differences reaching up to 31.2x on individual tasks. In sequential task analysis, GenericAgent showed genuine evolution: token consumption for one academic database retrieval task fell monotonically from 520K to 117K tokens. OpenClaw showed pseudo-evolution: its token consumption fluctuated without converging and collapsed on certain sequential tasks. These results confirm that success rate alone is insufficient and that sequential convergence of token consumption is the necessary criterion for detecting real learning.
- Harness Updating Is Not Harness Benefit: Disentangling Evolution Capabilities in Self-Evolving LLM Agents
Synthesis
Plain-language abstract This paper studies self-evolving LLM agents — AI systems whose surrounding infrastructure (prompts, skills, memories, tools) is automatically updated based on experience, while the underlying model weights stay fixed. The authors separate two distinct capabilities: how well a model produces useful updates to that infrastructure, and how well a model actually benefits from those updates when solving tasks. They find these two capabilities are largely independent of each other and of a model's general task-solving ability.
Motivation Prior evaluations of self-evolving agents measure only end-to-end performance gains, making it impossible to tell whether improvements come from better infrastructure updates or from the agent using updated infrastructure more effectively. This conflation leaves open the practical questions of which models are worth investing in as updaters versus task-solvers, and which capability bottlenecks most limit weaker models.
Methodology The authors evaluated seven LLMs spanning open-source and closed-source families across capability tiers — including Claude Opus 4.6, Claude Sonnet 4.6, Claude Haiku 4.5, GPT-OSS-120B, Qwen3-235B, Qwen3-32B, and Qwen3.5-9B — on three agentic benchmarks: SWE-bench Verified (software engineering), MCP-Atlas (tool use over real MCP servers), and SkillsBench (skill-based execution). They systematically varied which model acted as the evolver (producing harness updates) and which acted as the task-solving agent, measuring harness-updating gain and harness-benefit gain independently.
Results Harness-updating capability is flat across model capability tiers: the best and worst evolver differ by at most 3.1 percentage points on any benchmark, and even the smallest evolver (Qwen3.5-9B) matches Claude Opus 4.6 in downstream gains. Harness-benefit is non-monotonic: mid-tier models such as GPT-OSS-120B and Qwen3-235B benefit most (up to 19.3 percentage points on SWE-bench), strong models gain little due to a ceiling effect, and weak models gain little for different reasons — they fail to invoke relevant harness artifacts (Qwen3-32B loads the harness only 25% of the time versus ~96% for strong models) or fail to follow the harness instructions faithfully over long tasks. The findings recommend allocating capability budget to the task-solving agent rather than the evolver, and treating harness invocation and long-horizon instruction following as first-class targets in agent training.
- Skill1: Unified Evolution of Skill-Augmented Agents via Reinforcement Learning
Synthesis
Plain-language abstract This paper introduces Skill1, a framework that trains a language model agent to simultaneously improve at three linked tasks: choosing a useful skill from a stored library, applying that skill to solve a new task, and distilling new skills from experience. Unlike prior work that handles these capabilities separately, Skill1 uses a single reinforcement learning signal to evolve all three together, building an agent that gets better at finding, using, and creating reusable strategies over time.
Motivation Language model agents trained with reinforcement learning absorb successful strategies only implicitly into their parameters and cannot explicitly reuse them across tasks. While skill-library approaches address this by storing reusable strategies, existing methods optimize skill selection, utilization, and distillation in isolation or with inconsistent reward sources, creating optimization bottlenecks where improving one stage does not benefit the others and conflicting signals prevent coherent improvement.
Methodology Skill1 trains a single policy using the GRPO reinforcement learning algorithm on the ALFWorld household-task benchmark and the WebShop online-shopping benchmark. For each task, the policy generates a natural-language query to retrieve candidate skills from the library via semantic similarity, re-ranks those candidates to select the best match, executes multi-turn environment interaction conditioned on the selected skill, and then distills a new skill from the resulting trajectory. All three stages are credited from a single binary task-outcome reward: the low-frequency moving average of outcomes over skills credits selection quality, and the deviation of each new outcome from that trend credits distillation quality.
Results Skill1 reaches 97.5% average success rate on ALFWorld, surpassing the prior best method (RetroAgent) by 2.6 percentage points and ranking first on five of six task types. It also achieves the best performance across all methods on WebShop. Compared to the strongest reinforcement-learning-only baseline (GiGPO), Skill1 improves by 6.7 points on ALFWorld. Ablation studies show that removing the skill library causes the largest single drop (to 80.9%), and removing any individual credit-assignment signal degrades all three capabilities, confirming mutual dependence among selection, utilization, and distillation.
- SkillClaw: Let Skills Evolve Collectively with Agentic Evolver
Synthesis
Plain-language abstract SkillClaw is a framework that lets AI agents improve their reusable skills automatically by pooling experience across many users. Rather than each user rediscovering the same solutions independently, the system collects interaction traces from all users, identifies recurring patterns, and updates a shared skill library that every agent benefits from—without requiring any extra effort from users.
Motivation LLM-based agents like OpenClaw rely on a fixed set of reusable skills that remain static after deployment. As a result, similar workflows, tool-usage patterns, and failure modes are repeatedly rediscovered across users, and no mechanism exists to convert heterogeneous cross-user experience into reliable skill improvements. A single user rarely produces enough signal to distinguish a generalizable fix from an idiosyncratic one, so aggregating evidence across users is necessary for stable evolution.
Methodology SkillClaw operates in a closed loop: independently deployed agents record full session trajectories—capturing prompts, tool calls, intermediate feedback, and final responses—and upload them to a shared evidence base. A centralized, autonomous evolver periodically processes these trajectories to identify recurring behavioral patterns, then refines existing skills or adds new capabilities to a shared skill repository. Updated skills are synchronized back to all agents, so improvements discovered in one context propagate system-wide. Experiments were conducted on WildClawBench, a real-world agent benchmark, using Qwen3-Max as the underlying model.
Results Experiments on WildClawBench demonstrate that SkillClaw yields substantial improvements across tasks with limited interaction and feedback, highlighting the effectiveness of multi-user driven collective evolution for building continuously improving agent systems in real-world environments.
- Test-Time Learning with an Evolving Library
Synthesis
Plain-language abstract This paper presents EvoLib, a system that lets large language models get better at solving problems over time — without retraining or human-provided feedback. As the model works through a stream of tasks, it builds up a shared library of reusable knowledge extracted from its own reasoning, and that library keeps improving with each new problem solved.
Motivation Large language models normally treat every problem in isolation: any strategy discovered while solving one problem is discarded before the next. Approaches that share memory across problems typically store raw past trajectories, which are noisy and hard to generalize from. The gap EvoLib addresses is the absence of a principled way for black-box models — where weights cannot be modified — to accumulate and refine knowledge across problems without any external supervision signal.
Methodology EvoLib maintains a weighted library of two kinds of knowledge abstractions extracted from the model's own outputs: modular skills (reusable functions or sub-task workflows) and reflective insights (natural-language lessons about common mistakes). For each new task, the system samples relevant abstractions from the library via embedding-based similarity, uses them to guide solution generation, then extracts new abstractions from the resulting solution. A credit-assignment mechanism based on Information Gain and Future Information Gain updates abstraction weights to jointly reward immediate usefulness and potential to spawn better future abstractions; a consolidation step merges similar abstractions into more general ones. The whole process is self-supervised — the model evaluates its own solutions with no ground-truth labels. Experiments used GPT-4o and o4-mini on five benchmarks: HMMT math competition problems, BigCodeBench Hard and LiveCodeBench v6 Hard for code generation, and ScienceWorld and PDDL planning tasks for multi-turn agentic settings.
Results EvoLib achieved the strongest average performance across all benchmarks compared to base sampling, best-of-N, Recursive Self-Aggregation, ExpRAG, and Dynamic Cheatsheet baselines. Over base sampling, it improved accuracy by 11–20%. On BigCodeBench Hard, GPT-4o with EvoLib reached a pass rate of 40.8%, surpassing the strongest model on the public leaderboard (Gemini-Exp-1206 at 40.5%). EvoLib also proved more token-efficient than test-time scaling baselines, yielding 6–16% larger gains under half the compute budget. In continual learning experiments on PDDL with mixed task orderings, EvoLib outperformed Dynamic Cheatsheet by up to 9 percentage points, showing less sensitivity to task order.
- MUSE-Autoskill: Self-Evolving Agents via Skill Creation, Memory, Management, and Evaluation
Synthesis
Plain-language abstract This paper introduces MUSE-Autoskill, a framework that lets AI agents build up a personal library of reusable "skills" — chunks of code or instructions that encapsulate how to do something — and continuously improve those skills over time without human intervention. Rather than treating each skill as a one-off artifact, the system manages a full lifecycle: creating skills during task execution, storing them with accumulated experience, evaluating them with automated tests, and refining them when they fail.
Motivation Large language model agents increasingly tackle complex, multi-step tasks, but raw model reasoning alone is insufficient at scale. Existing approaches to automatic skill creation treat skills as static, isolated outputs, leaving four practical gaps: skills are created without access to the agent's runtime context, there is no per-skill memory that accumulates experience across tasks, skills are never validated or refined through unit tests, and long conversation histories cause context windows to overflow. The paper argues that skills must be managed as long-lived, testable assets rather than disposable generation outputs.
Methodology The authors built the MUSE-Autoskill agent framework around a unified five-stage skill lifecycle — creation, memory, management, evaluation, and refinement. Skills are created on demand via a built-in skill_create tool invoked from within the agent's reasoning loop. A multi-level memory system includes short-term, long-term, and a novel skill-level memory that accumulates per-skill experience across tasks. An evaluation subsystem validates skills through unit tests and runtime execution feedback, automatically triggering refinement when tests fail. A structured context manager with adaptive compression and cross-session state persistence handles long-horizon tasks. The framework was evaluated on SkillsBench, a benchmark of 51 real-world tasks graded by automated verifiers in standardized Docker environments, using three GPT-5.5-backed agents (MUSE-Autoskill, Codex, and Hermes) as comparators.
Results MUSE-Autoskill achieved the best with-skills accuracy in 3 of 4 benchmark super-domains and overall (68.40%, a +15.21 percentage point lift over its no-skills baseline), compared to Codex at 67.3% and Hermes at 61.2%. On the 35 tasks where the agent successfully generated its own skills from prior trajectories, accuracy reached 87.94%, surpassing the ceiling set by human-authored skills. Skills generated by MUSE-Autoskill also transferred to a different agent (Hermes), raising its accuracy by +10.51 percentage points and closing 79% of the gap between Hermes with no skills and Hermes with human skills.
- AutoManual: Constructing Instruction Manuals by LLM Agents via Interactive Environmental Learning
Synthesis
Plain-language abstract AutoManual is a framework that lets AI agents learn to navigate unfamiliar environments on their own by building and refining a structured set of rules through hands-on interaction, then compiling those rules into a human-readable instruction manual. Given just one simple demonstration, the system achieved a 97.4% task success rate using GPT-4-turbo and 86.2% using GPT-3.5-turbo on standard household task benchmarks.
Motivation LLM-based agents typically depend on elaborate expert-written prompts and fixed in-context examples to function in specific domains, which limits their ability to adapt when conditions change. Prior methods that save successful experiences as skills suffer from a 'Path Dependence' problem — the agent blindly replicates past solutions rather than reasoning about new situations — and offline rule extraction cannot respond to distributional shift encountered during deployment.
Methodology AutoManual uses three cooperating agents in an alternating online loop. A Planner agent writes executable code plans guided by the current rule set and interacts with the environment. A Builder agent updates those rules after each episode using a structured rule management system; to reduce hallucinations, a case-conditioned prompting strategy directs the Builder to first diagnose the type of failure (unrecorded situation vs. failure to follow existing rules) before updating rules. Finally, a Formulator agent reorganizes all optimized rules into a comprehensive Markdown manual. The system was evaluated on the ALFWorld household task benchmark.
Results Starting from a single demonstration, AutoManual achieved a task success rate of 97.4% with GPT-4-turbo and 86.2% with GPT-3.5-turbo on ALFWorld benchmark tasks, substantially outperforming prior methods. The self-generated manual also improved planning by smaller LLMs, showing that knowledge accumulated during training transfers to less capable models at test time.
- Memory Transfer Learning: How Memories are Transferred Across Domains in Coding Agents
Synthesis
Plain-language abstract This paper studies whether AI coding agents can benefit from memories collected in one programming domain when working on tasks in a different domain. The authors introduce Memory Transfer Learning (MTL), which pools experiences from heterogeneous coding tasks—such as software engineering, machine learning development, and competitive programming—and makes them available to agents tackling new problems. They test this idea across six coding benchmarks and four different ways of representing memories, from raw execution traces to high-level abstract insights.
Motivation Most memory-augmented coding agents are restricted to reusing experiences from the same task domain, ignoring the fact that diverse programming problems share common infrastructure like Linux shells and programming languages. As gains from scaling training data plateau, self-evolution through accumulated experience offers a path to further improvement, but existing systems fail to exploit knowledge across domain boundaries—leaving a large pool of potentially transferable experience untapped.
Methodology The researchers evaluated MTL across six coding benchmarks spanning software engineering (SWE-level), machine learning, and competitive coding tasks. They used four memory representations of varying abstraction: concrete execution trajectories, code snippets, experiential planning and debugging traces, and high-level abstract insights. A unified memory pool drawn from all heterogeneous domains was made available during retrieval, and performance was compared against single-domain memory baselines.
Results Cross-domain memory transfer improved average performance by 3.7% across the six benchmarks. The primary source of benefit was meta-knowledge—operational know-how such as validation routines and structural inspection strategies—rather than task-specific code. The paper found that abstraction level determines transferability: high-level abstract insights generalize well across domains, while low-level execution traces often cause negative transfer by introducing excessive task-specific detail. Performance gains also scaled with the size of the memory pool and the number of contributing domains, and memory was shown to transfer effectively even between different underlying models.
- SEARL: Joint Optimization of Policy and Tool Graph Memory for Self-Evolving Agents
Synthesis
Plain-language abstract SEARL is a reinforcement learning framework that trains AI agents to simultaneously build up a library of reusable tools and improve their own decision-making policy. Rather than relying on a fixed set of pre-defined tools or simply accumulating raw past experiences, the agent continuously creates, stores, and reuses modular tools organized in a graph structure, growing smarter as it solves more problems.
Motivation Large language models still struggle with complex, multi-step tasks when prompted directly, and existing approaches either use static tool libraries that limit adaptability or rely on large-scale models and multi-agent systems that are expensive to deploy. Reward signals in agentic reinforcement learning are also typically sparse—given only at task completion—making it hard to assign credit to individual steps. There was no framework that jointly improved both the agent's policy and its external tool memory together.
Methodology The authors formalize agent training as a Tool Memory-Enhanced Markov Decision Process, where the agent operates over a dynamic directed graph of tools (nodes) connected by execution dependencies (edges). At each step the agent retrieves relevant tools from the graph, decides whether to reuse or create a new one, and executes actions. Training uses a composite reward combining a sparse binary outcome reward with dense process-level rewards for planning, tool creation, and tool execution. Credit assignment is handled through a two-level advantage scheme: episode-level advantages across full trajectories, and step-level advantages anchored to specific tools, grouping actions that used the same tool across different trajectories. Experiments use 10,000 open-source RL training samples and evaluate on mathematical reasoning (AIME2024, MATH500, GSM8K) and multi-hop knowledge QA benchmarks (HotpotQA, 2WikiMultihopQA, Musique, Bamboogle) against baselines including GRPO, DAPO, REINFORCE++, and ARPO.
Results SEARL achieves the best average rank (1.43) across all benchmarks compared to baselines. It matches the top-performing method on AIME2024 (0.3333) while consistently outperforming or matching baselines on multi-hop QA tasks; on Bamboogle it reaches 0.3040 versus 0.2480 for the next best. The Tool Graph Memory grows from small disconnected subgraphs into interconnected clusters spanning multiple domains as training progresses, with the agent demonstrating higher training rewards and sustained exploration entropy compared to the GRPO baseline throughout training.
- A Comprehensive Survey on Agent Skills: Taxonomy, Techniques, and Applications
Synthesis
Plain-language abstract This paper is a survey of "agent skills" — reusable, stored procedures that tell AI agents not just what tools exist, but how, when, and in what sequence to use them when completing complex tasks. The authors review the research literature on how these skills are represented, learned, retrieved, and updated, and provide a taxonomy and resource collection for the growing field of skill-centric AI agent design.
Motivation Large language model agents can access many tools via APIs and protocols, but simply having access to tools does not produce reliable behavior: agents must still figure out how to coordinate multiple tools, handle failures, and validate outputs from scratch on every task. This "procedural gap" makes agents brittle, slow, and hard to maintain as tasks grow more complex. The survey argues that reusable procedural artifacts — skills — are the missing layer between raw tool access and robust task execution.
Methodology The authors systematically organize existing research around four lifecycle stages of agent skills: representation (how skills are formally encoded), acquisition (how skills are learned from human demonstrations, execution traces, or task-conditioned generation), retrieval (how relevant skills are selected at runtime), and evolution (how skills are updated and governed over time). Representative methods, platforms, benchmarks, and application domains are reviewed within each stage, drawing on work published from approximately April 2023 through April 2026.
Results The survey identifies three main skill acquisition strategies — human-derived, experience-derived, and task-derived — and documents that systems such as Voyager, Reflexion, ExpeL, and Agent Workflow Memory illustrate a spectrum from selecting successful traces, to abstracting lessons, to packaging reusable executable workflows. Eight application domains are covered, including software engineering, web and GUI automation, robotics, and social simulation. Open challenges identified include weak standards for skill schemas and interoperability, lack of lifecycle robustness against API deprecation, and evaluation methods that cannot distinguish genuine skill improvements from stronger test-time compute or task synthesis.
- SkillDroid: Compile Once, Reuse Forever
Synthesis
Plain-language abstract SkillDroid is an Android automation system that learns from a task the first time an AI completes it, then replays that learned sequence on later requests without involving the AI again. Instead of reasoning through every step of a repeated task from scratch, it stores a reusable action template and replays it at machine speed, falling back to AI assistance only when something unexpected occurs.
Motivation Current AI-based mobile agents treat every task execution as an independent reasoning episode, calling the language model at each action step. This means a task completed successfully yesterday is re-derived entirely from scratch today, with no gain in speed or reliability. LLM calls account for 75-94% of total agent execution time, and in testing a stateless agent's success rate degraded from 80% to 44% over 150 rounds as instruction phrasing became more varied, because past successes provide no benefit to future attempts.
Methodology SkillDroid uses a three-layer architecture running on top of an open-source Android automation framework. In Layer 1, an LLM guides task execution step by step and, on success, a skill compiler extracts a parameterized template — a sequence of UI actions with weighted element locators and typed parameter slots — stored in a local SQLite database. In Layer 2, a matching cascade using regex patterns and embedding-based semantic similarity routes new instructions to stored skills for replay via Android's accessibility interface with zero LLM calls, using a state verifier to detect UI deviations and gracefully fall back when needed. In Layer 3, a failure-learning component tracks skill reliability and triggers recompilation when a skill's failure rate exceeds 50%, progressively replacing noisy initial compilations with cleaner versions.
Results Over a 150-round longitudinal evaluation spanning 15 task types across diverse Android applications with systematic instruction variation and controlled perturbations, SkillDroid achieved an 85.3% success rate — 23 percentage points above a stateless LLM baseline — while using 49% fewer LLM calls. The skill replay mechanism achieved a perfect 100% success rate across 79 replay rounds at 2.4 times the speed of full LLM execution. Critically, the system's success rate converged upward from 87% to 91% across experimental phases, while the baseline degraded from 80% to 44%, demonstrating that SkillDroid improves with use while stateless agents become less reliable as task variation grows.
- Beyond Goldfish Memory: Long-Term Open-Domain Conversation
Synthesis
Foundational long-term dialogue benchmark (pre-wave).
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- Keep Me Updated! Memory Management in Long-term Conversations
Synthesis
Early memory-management benchmark for long conversations.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- A pathway for forgetting
Synthesis
Neuroscience anchor: active forgetting pathway.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- A brain pathway for active forgetting
Synthesis
Neuroscience anchor: active forgetting.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- Memory consolidation in the neocortex
Synthesis
Neuroscience anchor: consolidation.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- Targeted Forgetting and False Memory Formation in Continual Learners through Adversarial Backdoor Attacks
Synthesis
Adversarial false-memory formation in continual learning.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- Tool-Making and Self-Evolving LLM Agents in Low-Latency Systems
Synthesis
Plain-language abstract This paper deploys a production LLM agent that, instead of writing fresh code for every request, compiles the repeated steps of a standard operating procedure (SOP) into validated, versioned tools ahead of time; at runtime the agent calls those tools directly and falls back to code generation only when a tool is unavailable or fails. It triages alarms in an Amazon fulfillment-center outbound dock against a 44-node SOP over heterogeneous metric backends.
Motivation In the prevailing CodeAct-style paradigm the agent generates and executes fresh code for each request, so when the same workflow repeats against a stable backend it re-interprets the same instruction, rediscovers the same schema, and regenerates similar code, raising latency, cost, and run-to-run variance. In this setting most latency and correctness errors come from translating underspecified SOP text into a concrete query against a production metric backend, which motivates self-evolving agents that build reusable tools before they are needed in production.
Methodology Offline, each SOP node is compiled into a tool: a data-collector sub-agent runs against the live environment via MCP, producing a trace of query code, backend responses, observed schema (field names, datatypes, value ranges), and a graded verdict; a tool-maker LLM writes a candidate tool conditioned on the SOP node text, the node's position in the decision tree, and that trace; and a reflector-tool-maker loop repairs the candidate against labeled cases. Online, the production agent invokes these compiled tools inline, one call per node, falling back to code generation only when a tool is unavailable or fails.
Results In production, tool calls reduce p50 latency by 42%; on 1,500 historical alarms they reduce end-to-end error rate by up to 53% by suppressing run-to-run variance in repeated steps. Because tools return compact structured verdicts, a simpler direct-call architecture reduces p50 latency by a further 62% in a controlled ablation. Both the data-collection trace and the test-repair loop are necessary, residual errors concentrate on underspecified SOP steps where targeted fixes raise pass@1 from 94.5% to 99.9%, and versioned tools improve auditability while exposing specification gaps and upstream data drift.
- SkillCorpus: Consolidating and Evaluating the Open Skill Ecosystem for Real-World LLM Agents
Synthesis
Plain-language abstract Community SKILL.md files package reusable procedural knowledge for LLM agents, but the public ecosystem is fragmented, redundant, and uneven in quality. SkillCorpus crawls roughly 821,000 skill files from 62 public sources, curates them through a six-stage pipeline into 96,401 skills organised by a 16-class taxonomy and three quality facets (utility, robustness, safety), and pairs the corpus with a fine-tuned retrieval-and-selection stack. Plugged into two agent harnesses across three real-task benchmarks, the corpus consistently raises pass rates, and the paper traces exactly where the gains stop.
Motivation Whether the abundant open skill ecosystem improves agents on real tasks was unsettled: hand-picked oracle skills help heterogeneously, while uncurated community libraries can fail to beat a no-skill baseline. No released corpus was simultaneously broadly aggregated, strictly quality-gated, and licence-cleared, and no prior evaluation served a deployed community corpus through retrieval on real benchmarks.
Methodology A registry of 62 sources across five ingestion mechanisms feeds a six-stage funnel: structural parse and length filters; two-tier deduplication in which exact fingerprints collapse 59.7% of stage input and an LLM judge adjudicates 66,751 borderline semantic pairs; an LLM judge emitting utility, robustness, and safety subscores plus 19 quality flags, five of which (prompt injection, command injection, unsafe execution, auth bypass, CSAM risk) force exclusion; a safety hard-gate plus OSI-permissive licence filter; and indexing with 1024-dimension retrieval embeddings. A fine-tuned recall-and-rerank stack with an LLM selector that reads full skill bodies matches skills to incoming tasks. Evaluation spans SkillsBench, GDPVal, and QwenClawBench on two harnesses (OpenClaw, Raven) and two open backbones, with a frontier robustness check.
Results Integration yields consistent gains on all three benchmarks, largest on SkillsBench (+7.5 pp mean; +13.4 pp on the strongest Raven cell over a 9.2% no-skill baseline; +8.0 pp for the frontier check). Lesion ablations show curation and retrieval each contribute: swapping the filtered corpus for the raw crawl drops the strongest cell from 22.6% to 14.9% pass@1, and swapping the fine-tuned stack for off-the-shelf retrieval drops it to 13.8%. The gains are bounded twice over. Coverage: mean per-task gain climbs from +2.2 to +25.1 pp across retrieval-match bins, and thin-coverage categories floor at zero rather than turning negative. Harness: on tasks Raven passes and OpenClaw fails, traces show OpenClaw writes scripts it never executes, while Raven completes an execute-verify-fix loop, so skill content converts into verifier passes mainly through such a loop.
- How Agent Skills Fail under Long Contexts: A White-Box Study in Code Auditing
Synthesis
Plain-language abstract Agent Skills package procedural instructions for coding agents, but a loaded skill's requirements do not all stay active across a long tool-using trajectory. In a white-box code-audit workflow with 24 fixed artifact checks, the same task passes 8/10 runs in a clean 11K-character context and only 3/10 in 299K-character contexts - whether the added material is relevant production text or irrelevant archive. Requirement coverage stays above 92% even in failing runs: agents lose one or two obligations, not the task. An external checklist restating all 24 checks passes 10/10 runs where a generic self-check passes 5/10.
Motivation Long-context research shows a model's usable context is smaller and less uniform than its advertised window, and trajectory studies show failures begin early and hide behind plausible final states. The missing piece is a focused test: hold a skill-based task and its checks fixed, vary only the surrounding context, and identify exactly which stated requirement fails - and whether a simple external check prevents the failure.
Methodology Mandatory instructions from a production-derived audit workflow (an industrial code-audit scanner's Stage 4CD task) are translated into 24 deterministic, equally weighted checks, each validated against positive and negative fixtures before any model runs. Every attempt starts from a sanitized, answer-free workspace; conditions add clean (10,991 chars), relevant-long (299,140 chars of same-workflow production material), or irrelevant-long (equal-length unrelated archive) context. Ten valid runs per condition with Codex + gpt-5.4-mini; failed runs are classified by first visible failure location (lost requirement, editing drift, failed checking, non-agent failure). A mitigation arm compares a generic self-validation prompt against a detailed checklist differing by only 649 characters; scaffold probes compare direct prompting, a retrospectively selected evidence bundle, and tool-using agent shells.
Results Clean passes 8/10; both long conditions pass 3/10 - a 50-point observed drop that remains trend-level (two-sided Fisher p=0.0698) - with no ordering between relevant and irrelevant context (p=1.0). Check coverage stays at 92-94% in the long conditions: typical failures omit one required array or exceed a field cardinality, though one run abandoned two of four audit tasks entirely. The detailed checklist passes 10/10 versus 5/10 for the generic self-check (p=0.0325); the generic validator's spot-checks omit the same field generation omitted. A second task passes every clean and long run, so the evidence supports no universal context-length threshold. Infrastructure is a separate failure source: only 29 of 57 extension attempts produced scoreable output, with first-token disconnects clustered in the irrelevant-long condition. For gpt-5.5, a small evidence bundle passes 3/3 without tools while the full 299K direct prompt passes 1/3, suggesting selective retrieval - not tools per se - explains coding-agent benefit.
- The Regression Tax: Decomposing Why Skills Help and Hurt LLM Agents
Synthesis
Plain-language abstract Procedural skills for LLM agents are normally judged by average improvement in task success, which hides the tasks a skill library breaks. Running the same agent with and without skills across 5,832 paired task-condition runs on two office-automation benchmarks and three model-harness stacks, the paper decomposes each pass-rate change into gains and regressions. Regressions offset 59% of gross gains, and the best libraries lead mainly by regressing less rather than gaining more. Three regression mechanisms are identified from traces - skill-description osmosis, grounding displacement and verification displacement - and the residual failures cluster at grounding and verification, the stages existing skills least often address.
Motivation Systems that generate skills automatically from execution traces are evaluated by average gain, so two libraries with identical averages can differ sharply in how many working tasks they destroy. Methods that detect and drop harmful skills identify which skill to remove but not why it regressed a task, so a mostly useful skill may be discarded wholesale. Those methods also act only when a skill is retrieved or invoked, while a skill's name and description remain in the system prompt at every step and can change behavior without ever being called - a channel selection-based approaches cannot observe.
Methodology Two benchmarks over real artifacts: OfficeQA-Pro (question answering over U.S. Treasury financial documents, where the hard part is finding the right table, vintage and definition rather than the arithmetic) and SpreadsheetBench (workbook manipulation from real Excel-forum problems, graded on exact cell values). Three stacks pair a harness with its usual model: OpenCode / minimax-m2.7, Codex / gpt-5.4-mini, Claude Code / sonnet-4.6. Each stack and benchmark runs under four conditions - none, plus three libraries built by different meta-skill creators from the same analyst-extracted failure signals, so only the library text changes within a stack. Every task falls into gain, regression, residual failure or retained against the no-skill baseline; net effect is gains minus regressions, tested with the exact two-sided McNemar test on discordant pairs with Newcombe 95% intervals. Skill invocation is read from the trajectory so presence-only influence can be separated from body engagement. Each condition is run once per task, so run-to-run variance is not estimated.
Results Regression counts range from 2 to 41 across the eighteen library conditions and never reach zero; 324 regression transitions cancel 59% of 553 gains, with the pattern holding on both benchmarks (66% of gains cancelled on OfficeQA-Pro, 56% on SpreadsheetBench). Even clearly positive cells are close-run: on SpreadsheetBench the openai library broke 41 while gaining 45 on one stack and broke 27 while gaining 30 on another. Five of eighteen conditions reach nominal p < .05, but only three survive Bonferroni correction, all on Claude Code / sonnet-4.6 with SpreadsheetBench - a real but narrow effect. Grounding displacement accounts for 72.8% of the 81 coded OfficeQA-Pro regressions and osmosis for 17.3%; on SpreadsheetBench osmosis accounts for 70 of 243 regressions against 46 with the body engaged and 32 attributable to a grader artifact. Body engagement is set by the harness rather than the skill: the same library is invoked on 73-91% of OfficeQA-Pro tasks but 5-14% of SpreadsheetBench tasks on one stack, and on 99-100% versus 0-1% on another. Correcting the known grader artifact required re-grading 226 treatment task-conditions with a full spreadsheet engine, since the default engine cannot recalculate Excel structured references and scores correct formulas as failures.
- Agentic Method for Deterministic Validation of Legacy Code Migration
Synthesis
Plain-language abstract Enterprises still run large COBOL systems on mainframes, and moving them to Java means proving the new program behaves like the old one. Testing that is hard because real test data is scarce and the corner cases are the point, including behavior that never matched the original product definition but became part of it over the years. This paper describes the Locksmith Loop, used at American Express. The COBOL source and its generated Java target are each instrumented with mocks and run off the mainframe on ordinary hardware, and a deterministic gate runs both on the same inputs and flags any divergence. A search phase drives inputs to reach as many branches as it can; when it stalls, an AI agent proposes a code mutation applied identically to both programs to open a blocked region, and the gate decides whether the mutation is kept. Successful mutations are saved as reusable skills. Across three programs the loop pushes coverage well past the plateau that input search alone reaches, and the Java matched the COBOL reference on every accepted test case.
Motivation Agentic coding systems make exploring and migrating legacy systems increasingly plausible, but evaluating parity between the legacy and modern variants remains hard, and organizations typically run both systems under strict evaluation until they have enough confidence to cut traffic over. The blocker is test data: only a limited number of real-world scenarios are usually covered, leaving a long tail of corner cases untested, and broken-as-usual behavior that deviates from the original specification has to be preserved anyway in lift-and-shift modernization. The authors observed empirically that established input-space techniques, including combinatorial interaction testing, adaptive random testing, search-based test generation and many-objective variants, fuzzing, and quality-diversity algorithms such as MAP-Elites, all converge to similar coverage ceilings, which indicated that the remaining branches were structurally unreachable without modifying state outside the input-search space.
Methodology The COBOL source passes through a deterministic Migrator to produce the Java target and through a deterministic Mock Generator to produce a runnable COBOL mock; a shared test harness exercises both, records a behavioral fingerprint, and enforces the Parity Gate. The loop follows a teacher-student pattern. The student is deterministic: Migrator, Analyzer, Runner and Parity Gate. Witness Search explores the input space, including mocked backend responses and environmental state, running six algorithms per sweep and taking the union of discovered branches with the test-case set, each sweep starting from the best previous set until two consecutive sweeps yield nothing new, which defines the plateau. At the plateau the Analyzer identifies a Locked Paragraph, a COBOL paragraph unreachable by input search alone. The teacher, an Authoring Layer agent, is then invoked to select or propose a Mutation Skill; the student applies the mutation symmetrically to both the COBOL mock and the Java target, and post-mutation Witness Search using UCB1 confirms the coverage gain. A mutation is retained only if it increases branch coverage and passes the Parity Gate, which compares end states across three equivalence axes; successful mutations are captured into the Skill Catalog. Control then returns to a full sweep, and the process recurses until no Locked Paragraph remains.
Results Three case studies span two open-source COBOL programs and one internal production-like program, ranging from 430 to 4,114 source lines. Locksmith consistently improved coverage beyond the input-search plateau, reaching nearly complete coverage on the two open-source programs and 91.90% branch coverage on the internal production-like program. On the production-shape run the loop covered 135 of 142 paragraphs (95.1%) and 101 of 146 static paragraph-to-paragraph transitions (69.2%) from 166 test cases, with Witness Search accounting for 54 transitions, agentic mutation for a further 47, and 45 left uncovered. Under deterministic parity checks the generated Java matched the COBOL reference on every accepted test case. The authors flag branch coverage as an imperfect proxy for fault detection, note that acceptance is anchored on cross-language parity rather than coverage, and decline to claim the resulting suite suffices for migration sign-off by itself.
- Self-Evolving Coding Agents
Synthesis
Plain-language abstract A survey of coding agents that update their own framework, memory, skills, tools, models, or workflow structure from prior coding attempts, organized by what evolves, when it evolves, and what software-specific evidence drives it.
Motivation Coding agents now operate as interactive systems inside real development workflows, interpreting requirements, inspecting repositories, editing multiple files, running tests, diagnosing failures and generating patches. But in most systems the base model, prompts, tool interfaces, memory mechanisms and control flow are fixed after deployment, which is hard to sustain when codebases evolve, APIs and dependencies change, conventions vary across repositories, and bug fixing requires repeated cycles of localization, patching, execution and revision. Meanwhile software engineering supplies unusually concrete feedback: unit tests, compiler errors, runtime traces, lint warnings, CI results and human code reviews. An agent that cannot accumulate experience from that feedback repeats its mistakes across tasks and never adapts to project-specific context. Existing work on self-evolving agents mostly targets broad task environments and leaves the software-specific requirements uncharacterized.
Methodology The survey is framed as a guiding synthesis rather than a review of a settled paradigm, organized around three questions: what components evolve and through what mechanisms, when evolution occurs and what evidence drives it, and how such agents should be evaluated beyond the setting they evolved in. It first separates coding agents, self-evolving agents and self-evolving coding agents conceptually, then builds an object-centered taxonomy with five categories: agent framework self-evolution (self-modifying scaffolds and archive-based variant search), memory self-evolution (experience, repository and plan-abstraction memory), skill and tool self-evolution, model self-evolution (adversarial test evolution, coder-verifier co-evolution, self-play policy evolution), and workflow and topology self-evolution. Two orthogonal dimensions cross it: timing (task-time, post-task, stage-wise) and evidence type (outcome, environmental, trajectory-derived). Representative systems are tabulated against all three dimensions plus their software-engineering task domain. Inclusion is limited to work whose central contribution changes an agent component or behavior through coding-specific feedback; benchmark-only datasets and static agent systems are treated as evaluation context rather than as methods.
Results The synthesis finds that executable feedback, repository-level context and coding trajectories give software engineering a distinctive role as a domain for agent self-evolution, because a remembered strategy can be validated by tests rather than merely accumulated, and repository history supplies long-term signal about how a project changes. Memory self-evolution clusters into experience banks over prior issue-resolution trajectories including failures (SWE-Exp), hierarchical pools separating general from repository-specific experience (EvoCoder), subtask-granularity stores that avoid coarse whole-trajectory matching, commit-and-issue-grounded repository memory for code localization, and plan abstraction reused as later context (SAGE). Skill and tool self-evolution is distinguished by actionability: CODESKILL maintains a skill bank at task and event granularity and treats skill management as a learnable policy; gskill learns per-repository skill documents validated by whether agents in isolated environments produce passing patches; Socratic-SWE distills a skill registry from traces that then generates the training curriculum. Tool self-evolution is the least developed, with Live-SWE-Agent the main example of an agent creating and revising its own tools from a bash-only scaffold. The named challenges are feedback reliability, benchmark overfitting, safety, maintainability, cost and generalization. Two are emphasized: memory must be evolved selectively, since noisy logs, misleading tests, brittle patches and repository-specific conventions produce memories that hurt when retrieved uncritically; and framework-level evolution carries the strongest risk, because a harmful modification to the machinery that generates future actions can break the agent loop, degrade tool use, overfit to benchmark feedback or exploit weaknesses in the evaluation harness, so it requires validation, rollback and robustness checks rather than performance-driven search alone.
- SkillResolve-Bench: Measuring and Resolving Same-Capability Ambiguity in Agent Skill Retrieval
Synthesis
Plain-language abstract A benchmark and method for a specific skill-retrieval failure: the retriever finds the right capability family but surfaces the wrong member of it, one that shares the vocabulary and procedure shape while pointing at a stale resource, skipping a precondition, or applying the wrong check. The benchmark pairs each query's helpful skill with that query-specific risky sibling inside a large public candidate pool and scores helpful ranking alongside a harmful sibling rate. The method resolves candidates into capability families, scores query-conditioned utility, and exposes one representative per family before the final top-K list.
Motivation Skills have become loadable operational artifacts carrying instructions, scripts, resources and metadata, so the retrieval layer decides which procedural context enters an agent before planning or execution. That makes retrieval failures more specific than broad irrelevance. Public skill audits find weak routing metadata, non-actionable bodies, reusable-artifact defects and technical debt, and gains from curated skills weaken when agents must retrieve from large real collections. Related work has shown top-K skill quality cannot be reduced to independent query-skill relevance because the retrieved set must be compatible as a set, and security work has established that loaded skill packages affect planning, context, permissions, scripts and local resources. Existing positive-skill retrieval benchmarks identify useful or gold skills but assign no query-specific execution-risk siblings, while malicious-skill detection and permission enforcement act after admission rather than at the retrieval-time choice of representative.
Methodology The setting is formalized as same-capability execution-risk retrieval: a collection of queries, each with a candidate pool, an admitted helpful skill, a query-specific execution-risk sibling, and a released family relation. Construction starts from a task-facing skill admitted for a query, and the paired sibling changes exactly the condition that makes the procedure usable, keeping the sibling plausible under ordinary semantic retrieval. Candidate pools add library pressure by ranking the pair among unrelated and partially related public skills drawn from a public SkillRet corpus, so a system must both recover active capability families and choose the right representative within each. Evaluation reports Recall@K and NDCG@K for the helpful skill together with HSR@K, the rate at which the risky sibling appears in the final top-K. The release records source role and admission evidence, risk taxonomy, cue and leakage checks, hashes, query-disjoint splits and held-out outputs. The method, SkillResolve, has three components: a Capability Resolver returning active candidate groups that should compete as alternative representatives (singleton groups allowed, which recovers ordinary ranking); a query-conditioned Utility Scorer trained with admitted helpful skills as positives and confusable library alternatives mined under the same query and pool protocol as negatives, using ordinary retrieval signals plus contract-profile cues; and a Representative Selector keeping the highest-utility member of each resolved group before final ranking. Family sources can also be derived from public metadata or skill text, which trades exposure against recall.
Results Same-capability ambiguity is prevalent in public libraries: 4,716 of 4,997 audited SkillRet queries have at least one non-gold skill in the gold skill's domain/action/object family, and across seven standard retrievers a top-three list surfaces such a sibling for 47.3% of queries, with 36.6% containing both the gold skill and a strict same-family sibling. Generic lexical retrieval, SkillRouter and BGE reranking retrieve relevant skills but expose risky siblings, while an attribution-listwise baseline suppresses them at the cost of helpful retrieval quality. SkillResolve reaches Recall@3 0.766, NDCG@3 0.699 and HSR@3 of 0 under the released family relation, improving over SkillRouter by 0.112 Recall@3 and 0.165 NDCG@3 while reducing HSR@3 from 0.693. Component analysis identifies representative selection as the controlling mechanism: with the same utility scorer but no representative selection, HSR@3 rises to 0.236. The recall-exposure tradeoff depends on the quality of the family source, since a resolver that splits a helpful skill and its risky sibling into different groups lets both survive into the final ranking. Note on versions: SciX holds the June 2026 v1 of this arXiv entry, titled SkillResolve-Bench with 661 helpful/risky pairs and a 7,982-candidate pool; a later revision circulates as SameCapRisk-Bench with a larger unit count and a different baseline table. The mechanism and the metric are unchanged across both; the figures above are the v1 body.
- SIGIL: Compiling Agent Skills into Typed Harnesses
Synthesis
Plain-language abstract Agent skills are prose procedure files loaded into a model's context and interpreted by a tool-calling loop, which means nothing in the runtime makes a mandated step happen. Measured against the procedures their own skills prescribe, a prose agent performs 56% of mandated steps on gpt-4o while still producing deliverables that pass output checks. SIGIL compiles a SKILL.md into an executable harness through a typed intermediate representation that marks each step as owned by code or by the model, raising step compliance to 86%, full-procedure completion from 28% to 65% of runs, and cutting median token cost to 0.58x.
Motivation Skills succeeded as an authoring format because domain experts can write, review and version them, but the property that makes them accessible leaves them unenforced. The document is consulted by the same process that is supposed to obey it, so an agent can satisfy its own reading of an instruction by writing a sentence asserting the outcome. Hand-writing a harness fixes enforcement at the cost of the authoring surface, and leaves two independent representations of one procedure free to drift. The resulting defect class is invisible to artifact-level testing: a financial-compliance report can carry reasonable figures and conclusions and still be invalid if the agent never retrieved the authoritative records, recalculated the totals, or checked the result against policy. Prior runtime supervision work adds monitors and guards that can block a disallowed action, but detection does not make a required action occur.
Methodology Compilation runs in two stages over AG-IR, a typed agentic IR whose nodes carry an owner stating whether code or the model executes the step, a modality recording how binding the source instruction was, and provenance to the mandating sentence. Extraction is the only stage containing a model and admits a rule only when a verbatim quotation supports it; six compile gates then reject an IR that points at content instead of embodying it, omits a mandated deliverable, fails to lower and type check, folds a mandatory rule into another slot's interior, or leaves a human-gated decision to model judgment. Lowering is deterministic, mapping each primitive onto an Object-Spatial Programming construct in Jac: nodes become node archetypes, edges fix walker traversal order, mandatory rules become abilities bound to node entry, model-owned nodes become typed llm() slots whose return type makes an out-of-range answer a type error, and forbidden rules lower to nothing, so the guarantee comes from the absence of a path. STRUCT-COV statically reports, per mandatory rule, whether the emitted module realizes it as a code gate, a dedicated model slot, monolithically inside another slot, or not at all, failing the last two. Evaluation covers 30 skills across document and tooling, software process, and governance and compliance families, with three process-scenario tasks per skill repeated three times per arm in isolated sandboxes, on gpt-4o and gpt-5, scored by Applicable-Mandate Compliance with a judge reading the full run and, for the harness, its node-path trace.
Results On gpt-4o the compiled harness performs 86% of mandated steps against 56% for prose, matching or exceeding prose on all 30 skills with 28 strict wins, 2 ties and no losses, and completing the full applicable procedure in 65% of runs against 28%, a factor of 2.3. Moving to gpt-5 leaves the harness at 86% while prose rises to 68%, so the advantage narrows from 30 points to 17; the harness artifact is byte-identical across both sweeps, which is what makes the guarantee model-independent by construction. Median token cost is 0.58x prose, cheaper on 24 skills and as low as 0.02x on a nearly all-code skill, with the exceptions concentrated in skills organized around a genuine tool-using loop, reaching 7.64x on using-superpowers and 3.09x on systematic-debugging, where the prose agent was cheaper because it truncated or skipped the loop. The compiler realizes 37% of mandates as code-owned gates on average, 32% to 44% by family, and the four skills where the harness loses on gpt-5 are judgment-heavy ones with little to compile.
- Auto-Policy, not Auto-Skill: Compiled Agent Skills for the Physical World
Synthesis
Plain-language abstract Agent Skills package procedural knowledge as markdown plus scripts, and that format describes how an agent should behave without deciding which behavior may become an action. As Skills move to settings that drive relays and locks, the gap becomes a physical one. The paper names Borrowed Authority: an inter-agent message carrying an instruction plus an unverifiable permission claim, which the receiving agent has no typed way to reject. Edge Skillguard answers it with a typed authority layer inside the Skill artifact - guard predicates over world state, leases and sensor evidence, expressed as a schema-validated policy file with a pure-function evaluator. On a live edge control plane it rejects 60/60 attacks across five variants while preserving all benign requests, holding at 5x scale and across hosts.
Motivation Self-evolving Skill harnesses generate orchestration automatically and report efficiency gains, not safety ones, so generating more Skills scales the advisory layer and leaves the authority decision to the model. Two adjacent attacks are already public: malicious skills distributed through community registries, plus a Claude Code project-file misconfiguration (CVE-2026-21852) that routed a session's API tokens to an attacker before trust was established, and jailbreaks of LLM-controlled robots reaching up to 100% success against deployed commercial platforms including a self-driving LLM, a wheeled UGV and a quadruped. Their intersection - a compromised skill artifact causing physical-state harm - is the open cell of the paper's attack table, and the authors construct and defend it before an in-the-wild incident rather than after.
Methodology An Edge Skillguard artifact is a tuple of orchestration states, typed world state (sensors, user identity, leases, device state, time, shared-state commit), typed envelope events, deterministic actions, guard predicates over state and event, a transition relation, bounded LLM holes, and inter-agent contracts incoming messages must satisfy. Guards are seven typed operators over dot-separated paths into envelope or state, shipped as a JSON-Schema-validated policy plus a pure-function evaluator that emits either an inbox publish or a structured policy_block log naming the failed predicates. It sits on a messaging substrate providing schema-validated typed envelopes, broker-attested sender_id from the connection token, durable per-agent FIFO inboxes, an audit-mirror outbox, and boundary rejection of malformed envelopes. Four conditions are compared - plain Skill, natural-language machine-to-machine with no receiver guard, a lease-only ablation, and the full policy - over 60 Borrowed Authority requests across five variants (stale presence, missing presence source, wrong-grantee lease, expired lease, lease-scope mismatch), 12 each, plus 60 benign requests, run in-process, on a live NATS broker against a Home Assistant deployment of 148 entities, and cross-host over Tailscale. Test subjects are isolated so no device adapter fires; the measurement is whether an unauthorized transition reaches the adapter boundary.
Results The full typed policy rejects 60/60 Borrowed Authority requests and preserves 60/60 benign ones, versus 60/60 wrongful actuation for both the plain Skill and the natural-language machine-to-machine baselines. The 5x run holds 300/300 attack rejection and 300/300 benign success at p95 399 microseconds on the live broker, and the cross-host Tailscale run holds the same correctness at p95 7.9 ms. Median latency is 3.2 microseconds in-process, 273 microseconds on the local broker, 5.7 ms over the mesh, with 0 LLM calls per decision against 1 for the advisory baselines. The lease-only ablation catches 36/60, covering the three lease-bound variants and letting both sensor-bound variants through, so freshness and source predicates carry the remainder. Blocked requests surface the failed predicates rather than a model rationale. The authors do not claim automated policy synthesis; hand-authored guards are the supported workflow, and the attack class is constructed rather than observed in the wild.
Reflection & Experience
Reflection & Experience-Stage Memory: self-evolving / reflective memory that improves an LLM agent's policy across trajectories (the Reflection -> Experience frontier)
Key threads
- Write-read decomposition of reflective memory: nearly every recent system splits memory into a prospective/write-side policy (what + how to store, via reflection or contrastive distillation) and a retrospective/read-side policy (retrieval refined by downstream utility), and the field is converging on evaluating these two stages independently (Reflective Memory Management, Learning How and What to Memorize, TSUBASA).
- From retrieved experience to generated/abstracted experience: the frontier is moving past raw trajectory retrieval toward cross-trajectory abstraction — clustering, contrastive analysis, hierarchical experience, workflow induction, and skill evolution — because retrieved raw episodes force the base LLM to re-adapt them (CLEAR, HiExp, Agent Workflow Memory, SkillClaw).
- Self-evolution couples memory with capability: the newest work jointly optimizes memory and policy/tool-graph/skill-library so accumulated experience compounds into expanded capability rather than just a growing text store (SEARL, Mem2Evolve, SkillClaw, Self-Learning Diagnostic Agent).
- Utility-driven, longitudinal metrics over surface-match: benchmarks are shifting to downstream-utility scoring and improvement-trajectory metrics across many sessions/cases instead of single-shot retrieval accuracy (BEHEMOTH's downstream-utility metric, Evo-MedAgent's beyond-one-shot framing).
- Parametric vs non-parametric consolidation as an explicit design axis: experience can be consolidated into per-user weights or into compacted context, and recent work treats this as a controlled comparison rather than an architectural assumption (Dennis consolidation-vs-compaction, TSUBASA context distillation, CLEAR's SFT+RL CAM).
Open gaps
- No standardized harness isolates the *reflection-induced* gain from base-model improvement: papers report end-task deltas (e.g. CLEAR's AppWorld 72.62 -> 81.15) but there is no shared protocol that ablates write-side vs read-side reflection on the SAME multi-session trajectory, so cross-paper comparison of 'does memory improve the policy' is apples-to-oranges.
- Catastrophic forgetting and memory drift in self-evolving stores are under-measured: systems like SkillClaw and Mem2Evolve let skills/experience evolve continually, but almost none report whether earlier-acquired competence degrades as memory evolves — there is no negative-transfer or forgetting metric in the agentic-memory eval canon.
- Synthetic multi-session trajectory pipelines are bespoke per paper: BEHEMOTH repurposes 18 existing datasets and others hand-build dialogue/diagnosis streams, but there is no reusable generator for controllable, ground-truth-labeled multi-session experience streams with injected conflicts, distractors, and known-reusable sub-skills.
- Parametric vs non-parametric experience consolidation is compared only in isolated studies (Dennis) on small settings; the field lacks a benchmark that scores both consolidation modes under matched compute/token budgets across episodic, semantic, and procedural memory types.
- Most reported numbers come from zero-citation 2026 preprints with single-domain evaluations (medical, web, search); external validity and reproducibility of the experience-reuse gains across domains remain unestablished, and open-source harnesses (CLEAR is a notable exception) are rare.
- Agent Workflow Memory
Synthesis
Plain-language abstract This paper introduces Agent Workflow Memory (AWM), a method that teaches language model-based web agents to extract reusable task routines — called workflows — from past experience and apply them to guide future actions. Rather than treating each task in isolation, AWM lets agents build up a growing library of skills, from simple steps like finding a place by name to more complex multi-step procedures composed from earlier workflows.
Motivation Current language model agents struggle with long, complex web navigation tasks because they process each task independently and do not learn from past successes or failures. They lack the ability to extract and reuse common task patterns across similar contexts, making them brittle when the task environment changes even slightly.
Methodology AWM operates in two modes: offline, where it extracts workflows from annotated training trajectories before test time, and online, where it induces workflows on the fly from self-generated predictions judged correct by an evaluator. The method was evaluated on two major web navigation benchmarks — Mind2Web (1000+ tasks across 200+ domains) and WebArena (execution-based evaluation covering travel, shopping, social media, and other domains) — using language model agents that maintain and grow a memory of induced workflows over time.
Results AWM improved baseline success rates by 24.6% relative on Mind2Web and 51.1% relative on WebArena, while also reducing the number of steps needed to solve WebArena tasks. It outperformed methods that use human-expert-written workflows by 7.9% on WebArena. In cross-task, cross-website, and cross-domain generalization evaluations, online AWM surpassed baselines by 8.9 to 14.0 absolute percentage points, with the performance gap growing as the train-test distribution divergence increased — reaching as high as 22.5 points after rolling over only tens of examples.
- SkillClaw: Let Skills Evolve Collectively with Agentic Evolver
Synthesis
Plain-language abstract SkillClaw is a framework that lets AI agents improve their reusable skills automatically by pooling experience across many users. Rather than each user rediscovering the same solutions independently, the system collects interaction traces from all users, identifies recurring patterns, and updates a shared skill library that every agent benefits from—without requiring any extra effort from users.
Motivation LLM-based agents like OpenClaw rely on a fixed set of reusable skills that remain static after deployment. As a result, similar workflows, tool-usage patterns, and failure modes are repeatedly rediscovered across users, and no mechanism exists to convert heterogeneous cross-user experience into reliable skill improvements. A single user rarely produces enough signal to distinguish a generalizable fix from an idiosyncratic one, so aggregating evidence across users is necessary for stable evolution.
Methodology SkillClaw operates in a closed loop: independently deployed agents record full session trajectories—capturing prompts, tool calls, intermediate feedback, and final responses—and upload them to a shared evidence base. A centralized, autonomous evolver periodically processes these trajectories to identify recurring behavioral patterns, then refines existing skills or adds new capabilities to a shared skill repository. Updated skills are synchronized back to all agents, so improvements discovered in one context propagate system-wide. Experiments were conducted on WildClawBench, a real-world agent benchmark, using Qwen3-Max as the underlying model.
Results Experiments on WildClawBench demonstrate that SkillClaw yields substantial improvements across tasks with limited interaction and feedback, highlighting the effectiveness of multi-user driven collective evolution for building continuously improving agent systems in real-world environments.
- SEARL: Joint Optimization of Policy and Tool Graph Memory for Self-Evolving Agents
Synthesis
Plain-language abstract SEARL is a reinforcement learning framework that trains AI agents to simultaneously build up a library of reusable tools and improve their own decision-making policy. Rather than relying on a fixed set of pre-defined tools or simply accumulating raw past experiences, the agent continuously creates, stores, and reuses modular tools organized in a graph structure, growing smarter as it solves more problems.
Motivation Large language models still struggle with complex, multi-step tasks when prompted directly, and existing approaches either use static tool libraries that limit adaptability or rely on large-scale models and multi-agent systems that are expensive to deploy. Reward signals in agentic reinforcement learning are also typically sparse—given only at task completion—making it hard to assign credit to individual steps. There was no framework that jointly improved both the agent's policy and its external tool memory together.
Methodology The authors formalize agent training as a Tool Memory-Enhanced Markov Decision Process, where the agent operates over a dynamic directed graph of tools (nodes) connected by execution dependencies (edges). At each step the agent retrieves relevant tools from the graph, decides whether to reuse or create a new one, and executes actions. Training uses a composite reward combining a sparse binary outcome reward with dense process-level rewards for planning, tool creation, and tool execution. Credit assignment is handled through a two-level advantage scheme: episode-level advantages across full trajectories, and step-level advantages anchored to specific tools, grouping actions that used the same tool across different trajectories. Experiments use 10,000 open-source RL training samples and evaluate on mathematical reasoning (AIME2024, MATH500, GSM8K) and multi-hop knowledge QA benchmarks (HotpotQA, 2WikiMultihopQA, Musique, Bamboogle) against baselines including GRPO, DAPO, REINFORCE++, and ARPO.
Results SEARL achieves the best average rank (1.43) across all benchmarks compared to baselines. It matches the top-performing method on AIME2024 (0.3333) while consistently outperforming or matching baselines on multi-hop QA tasks; on Bamboogle it reaches 0.3040 versus 0.2480 for the next best. The Tool Graph Memory grows from small disconnected subgraphs into interconnected clusters spanning multiple domains as training progresses, with the agent demonstrating higher training rewards and sustained exploration entropy compared to the GRPO baseline throughout training.
- Reflexion: Language Agents with Verbal Reinforcement Learning
Synthesis
Plain-language abstract This paper introduces Reflexion, a framework that teaches AI language agents to improve through verbal self-reflection rather than by retraining the underlying model. After each attempt at a task, the agent writes a short textual reflection on what went wrong, stores it in memory, and uses that reflection to make better decisions on the next try — much like a person learning from mistakes across multiple attempts.
Motivation Large language models used as autonomous agents struggle to learn efficiently from trial and error, because traditional reinforcement learning requires large amounts of training data and expensive model fine-tuning. There was no lightweight mechanism for an LLM-based agent to carry forward lessons from past failures without modifying model weights.
Methodology Reflexion converts binary or scalar feedback from the environment into natural-language summaries, which are stored in an episodic memory buffer and prepended as context in subsequent episodes. The framework was evaluated on three task categories: sequential decision-making (AlfWorld), knowledge-intensive reasoning (HotPotQA), and programming (HumanEval). Feedback signals included simple binary environment feedback, predefined heuristics for common failure cases, and self-evaluation methods such as LLM-based binary classification or self-written unit tests.
Results Reflexion improved performance over strong baselines by an absolute 22% on AlfWorld decision-making tasks within 12 iterative learning steps, by 20% on HotPotQA reasoning questions, and by up to 11% on HumanEval Python programming tasks. On HumanEval, Reflexion achieved 91% pass@1 accuracy, surpassing the prior state-of-the-art of 80% achieved by GPT-4.
- In Prospect and Retrospect: Reflective Memory Management for Long-term Personalized Dialogue Agents
Synthesis
Plain-language abstract This paper introduces Reflective Memory Management (RMM), a system that helps AI dialogue agents remember and retrieve relevant information across many conversations over time. Because large language models are stateless — they forget everything between sessions — the authors built an external memory mechanism with two complementary parts that work together to store and recall user information more accurately and adaptively.
Motivation AI assistants used in customer service, healthcare, or education need to remember what individual users have told them across many past conversations, not just the current session. Existing external memory systems for language models suffer from two problems: they store information at rigid, pre-defined chunk sizes (such as per conversation turn or per session) that do not match natural topic boundaries, and they rely on fixed retrieval mechanisms that cannot adapt to different users or dialogue styles, making personalized long-term interaction difficult.
Methodology The RMM framework combines two mechanisms. Prospective Reflection dynamically decomposes dialogue history into topic-based memory units across multiple granularities — individual utterances, turns, and whole sessions — so that semantically related content is grouped together regardless of where session or turn boundaries fall. Retrospective Reflection treats retrieval improvement as an online reinforcement learning problem: as the language model generates responses, it cites which retrieved memories were useful, and those citation signals are used as unsupervised reward feedback to iteratively refine the retriever without requiring any labeled training data. The system was evaluated on two benchmarks, MSC and LongMemEval, using Contriever and GTE retrievers with Gemini-1.5-Flash and Gemini-1.5-Pro as generators.
Results RMM achieves more than 10% accuracy improvement over a no-memory baseline on LongMemEval, and more than 5% improvement over the strongest prior baseline across memory retrieval and response generation metrics on both benchmarks. The full RMM framework reaches a METEOR score of 30.8% on MSC and Recall@5 of 60.4% on LongMemEval. Citation-based scoring used in Retrospective Reflection was validated as reliable, achieving an overall F1 of 86.7% for identifying useful versus non-useful retrieved memories. Experiments also show that flexible topic-based granularity from Prospective Reflection approaches oracle-level performance compared to any single fixed granularity strategy.
- CLEAR: Context Augmentation from Contrastive Learning of Experience via Agentic Reflection
Synthesis
Plain-language abstract CLEAR is a framework that helps AI agents perform better on tasks by generating customized background knowledge before each task, rather than simply retrieving stored instructions from previous runs. It trains a small, lightweight model to produce this task-specific context, which is then fed into the main AI agent's prompt. The system was tested on two benchmarks for agent task completion and outperformed existing approaches.
Motivation Large language model agents typically rely on either their built-in knowledge or retrieval of past experience to guide decision-making. Retrieved context from prior tasks is general-purpose and static, so the agent must figure out how to adapt it to each new situation — a burden that is especially problematic when the agent has limited reasoning ability or when new tasks differ substantially from past ones. There was no method that generated context tailored to the specific task at hand rather than reusing historical guidance.
Methodology CLEAR uses a two-stage training pipeline for a context augmentation model (CAM). First, a reflection agent performs contrastive analysis over past task execution trajectories, comparing successful and unsuccessful runs to produce task-specific summaries; these summaries become supervised fine-tuning data for the CAM. Second, the CAM is further optimized with reinforcement learning, where reward signals come from actually running the execution agent on tasks. The CAM is kept small and model-agnostic, adding minimal overhead, and does not require any modification to the underlying execution agent — making it compatible with proprietary LLMs. Evaluations were conducted on the AppWorld and WebShop benchmarks.
Results On the AppWorld benchmark test set, CLEAR improved the task completion rate from 72.62% to 81.15% compared to the baseline agent. On a subset of WebShop, it raised the averaged reward from 0.68 to 0.74. CLEAR consistently outperformed strong baselines across both benchmarks.
- Self-Evolving LLM Memory Extraction Across Heterogeneous Tasks
Synthesis
Plain-language abstract This paper tackles the problem of what an AI assistant should remember from past conversations. The authors build a benchmark called BEHEMOTH covering 18 datasets across very different task types, then propose a new method called CluE that learns better memory-extraction rules by grouping similar examples together before updating its strategy.
Motivation As LLM-based assistants become persistent across sessions, they need to decide what information from past conversations is worth storing as memory. Existing systems use fixed, hand-written extraction rules tuned for one narrow use case, but a general-purpose assistant faces many different kinds of interactions. There was no benchmark to measure how well memory extraction generalizes across such diverse tasks, and existing self-evolving prompt optimization methods were designed for homogeneous data and degrade on heterogeneous distributions.
Methodology The authors formalize memory extraction as producing a memory string from a past conversation using an extraction prompt, evaluated by how well that memory helps a separate generation model answer follow-up queries (a utility-driven metric). They construct BEHEMOTH by repurposing 18 existing datasets spanning personalization, problem-solving, and agentic task categories. They then propose CluE (Cluster-based Evolution), a self-evolving framework that batches training examples, clusters them by summarized extraction scenario, performs local analysis within each cluster, and synthesizes cross-cluster insights to iteratively update the extraction prompt.
Results Experiments on BEHEMOTH show that no single static extraction prompt dominates across all task categories. CluE achieves a +9.04% relative gain over a static baseline and consistently outperforms prior self-evolving frameworks (GEPA, ACE, MemEvolve), which were found to degrade under heterogeneous task distributions.
- TSUBASA: Improving Long-Horizon Personalization via Evolving Memory and Self-Learning with Context Distillation
Synthesis
Plain-language abstract This paper introduces TSUBASA, a framework for making AI language models better at personalizing their responses over long stretches of time—for example, tracking a user's preferences and history across many conversations. It combines two components: one that maintains and updates a structured memory of the user, and one that trains the model to internalize that memory more effectively so it can answer personal questions without needing to look up everything at retrieval time.
Motivation Personalized language models struggle with long-horizon tasks—situations where they must reason across a user's extensive history of interactions. Existing memory systems grow linearly and fail at tasks requiring implicit temporal reasoning; retrieval-augmented approaches face a quality-efficiency tradeoff where better answers require retrieving more context at prohibitive cost; and fine-tuning approaches are held back by a train-inference gap because raw conversation data does not prepare models well for the complex personalization tasks they face at evaluation time.
Methodology TSUBASA uses a two-wing design. The first wing handles dynamic memory writing: core factual observations are extracted from raw conversations and a memory manager applies structured operations (ADD, UPDATE, RECONCILE, IGNORE) to keep the memory store compact and conflict-free. The second wing handles internalized memory reading through a self-learning pipeline that applies a teacher-student context distillation objective on synthetic question-answer pairs: a frozen teacher model sees the full session context, while a trainable student model sees only the question, and the distillation loss trains the student to internalize user-specific knowledge parametrically. Evaluations were conducted on long-horizon personalization benchmarks using the Qwen-3 model family ranging from 4B to 32B parameters, compared against memory-augmented baselines including Mem0 and Memory-R1.
Results TSUBASA surpasses competitive memory-augmented systems that rely primarily on memory writing, such as Mem0 and Memory-R1, on long-horizon benchmarks. The framework achieves Pareto improvements over prior approaches—delivering higher personalization fidelity while using a reduced token budget—effectively breaking the quality-efficiency tradeoff. The approach also preserves user privacy by avoiding cross-user training.
- Beyond Stochastic Exploration: What Makes Training Data Valuable for Agentic Search
Synthesis
Plain-language abstract This paper introduces HiExp (Hierarchical Experience), a framework that improves how AI language models learn to search the web or external knowledge sources when solving complex, multi-step questions. Instead of having the model stumble through trial-and-error searches during training, HiExp teaches it strategic search patterns distilled from its own past successes and failures, making the model faster, more accurate, and more stable to train.
Motivation Current reinforcement learning methods for training AI search agents rely on stochastic exploration: the model tries many random reasoning paths and is rewarded only for getting the right answer. This is inefficient, prone to redundant or irrelevant search steps, and produces unstable training signals — especially for smaller models tackling complex multi-hop questions that require chaining several pieces of information together. There was no principled way to extract and reuse the procedural knowledge embedded in a model's own successful reasoning trajectories.
Methodology HiExp operates in two stages. First, it constructs hierarchical experience from the model's own rollouts: for each training question, multiple reasoning trajectories are sampled, then contrasted by outcome (successful vs. failed) to identify key decision points and reasoning traps. A multi-level agglomerative clustering step abstracts these case-specific insights into higher-level strategic principles. Second, during reinforcement learning training, these distilled experiences are dynamically injected into the rollout stage so the model's exploration is guided by accumulated knowledge rather than pure trial-and-error. Experiments used Qwen2.5-7B and Qwen2.5-32B base models trained on six multi-hop QA benchmarks (HotpotQA, 2WikiMultiHopQA, Musique, Bamboogle, MoreHopQA, Frames) and six mathematical reasoning benchmarks.
Results HiExp-Searcher outperforms prior reinforcement-learning-based search agents across all evaluated benchmarks. On the 7B model, it achieves an average CEM gain of roughly 9.7 points over the next-best RL baseline across the four primary multi-hop benchmarks. The framework also generalizes to out-of-domain datasets and to mathematical reasoning tasks without task-specific retraining. An ablation on experience source showed that self-distillation (the 7B model generating its own experiences) slightly outperforms using a larger teacher model (Qwen-Max) by about 1.2% on average, indicating that alignment with the student model's own reasoning distribution matters more than raw experience quality. Training stability analysis confirmed that HiExp substantially reduces reward variance and gradient noise compared to the standard GRPO baseline.
- Mem2Evolve: Towards Self-Evolving Agents via Co-Evolutionary Capability Expansion and Experience Distillation
Synthesis
Plain-language abstract This paper introduces Mem2Evolve, a framework for building AI agents that can improve themselves over time by combining two types of memory: a store of past task experiences and a store of dynamically created tools and specialist sub-agents. Rather than treating these two growth processes separately, the system makes them work together so each one reinforces the other.
Motivation Existing self-evolving agent frameworks either let agents learn from experience but keep them locked to a fixed set of tools, or let agents create new tools and sub-agents but do so blindly without drawing on past experience. Both approaches are limited: the first cannot expand what the agent is capable of doing, while the second produces unreliable results because it ignores proven strategies and known pitfalls.
Methodology Mem2Evolve maintains two memory components — an Experience Memory that stores trajectories from past task executions, and an Asset Memory that stores dynamically created tools and expert agents. When a new task arises, the system retrieves relevant past experience to guide the creation of new tools or specialist agents, then stores the resulting execution trajectory back into experience memory, enabling a continuous co-evolutionary loop. The framework was evaluated across 6 task categories and 8 benchmarks.
Results Mem2Evolve achieves an 18.53% improvement over standard large language models, an 11.80% improvement over agents that evolve only through experience accumulation, and a 6.46% improvement over agents that evolve only through asset creation, demonstrating that the co-evolutionary approach is more effective and stable than either strategy in isolation.
- Learning How and What to Memorize: Cognition-Inspired Two-Stage Optimization for Evolving Memory
Synthesis
Plain-language abstract This paper introduces MemCoE, a two-stage framework that teaches AI assistants to better remember and update information about individual users over long conversations. Rather than relying on hand-crafted memory rules, MemCoE learns both how to organize memory (what patterns to follow) and what specific information to store or forget, resulting in more consistent and personalized responses over time.
Motivation Large language models have limited context windows, so they cannot simply remember everything a user has said across many sessions. Existing memory systems use static, hand-crafted rules that cannot adapt to changing user behavior, while reinforcement learning approaches that treat memory updates as learnable actions suffer from sparse, delayed rewards that make training unstable and data-hungry. There was no principled way to jointly learn the organizational structure of memory and the specific update decisions an agent should make.
Methodology MemCoE draws an analogy to human memory schema theory, specifically the functional division between prefrontal cortex (which configures schemas) and hippocampus (which encodes episodic details). Stage one, Memory Guideline Induction (MGI), treats the memory-update instruction prompt as a learnable natural-language parameter and refines it using contrastive feedback over memory-augmented conversation trajectories, interpreted as textual gradients aggregated at the batch level. Stage two, Guideline-Aligned Memory Policy Optimization (GMPO), uses the induced guideline to define structured process rewards and trains a memory-evolution policy via multi-turn reinforcement learning. The framework is evaluated on three personalization memory benchmarks: PersonaMem, PrefEval, and PersonaBench, covering explicit and implicit user preferences across varying history lengths and noise levels.
Results MemCoE consistently outperformed strong retrieval-based and RL-based memory baselines across all three benchmarks. On the PersonaMem benchmark, the MGI-induced guideline achieved accuracy of 53.28 at 32K context and 43.76 at 128K context, corresponding to relative improvements of +10.4% and +11.3% over a manually written prompt baseline. The induced guideline also proved transferable across different LLM backbones: optimizing with one model generalized well to others including GPT-5 and Gemini-2.5-flash. The system showed favorable robustness under longer histories, noisier evidence, and different retrieval configurations.
- Evo-MedAgent: Beyond One-Shot Diagnosis with Agents That Remember, Reflect, and Improve
Synthesis
Plain-language abstract Evo-MedAgent is a memory system that lets an AI medical imaging agent learn from its own past cases at test time, without any retraining. Instead of treating each chest X-ray case in isolation, the agent accumulates three kinds of memory — records of past diagnostic episodes, a bank of distilled diagnostic rules, and a tracker of which tools are reliable — and uses them to do better on each new case.
Motivation Current tool-augmented LLM agents for medical image interpretation solve every case independently: they cannot retain lessons from prior successes or failures, correct recurring reasoning mistakes, or adjust their trust in specialist tools without expensive retraining. Human radiologists naturally improve with experience, but existing agents remain static across an entire evaluation benchmark.
Methodology The authors formalize the setting as sequential inference over an ordered series of chest X-ray cases from ChestAgentBench (2,500 multiple-choice questions across 675 expert-curated cases). After each case, ground-truth feedback triggers a reflection step that updates three memory stores: an episodic store of compressed past cases retrieved by similarity, a procedural store of priority-tagged diagnostic heuristics with per-rule utility tracking, and a tool-governance store that labels each specialist tool as trusted, caution, or avoid based on accumulated interaction statistics. The framework requires no LLM parameter updates — only one retrieval pass and one reflection call per case — and was tested with GPT-5-mini, Gemini-3 Flash, and GPT-5.2 as backbone vision-language models.
Results On ChestAgentBench, adding the full Evo-MedAgent memory raised multiple-choice accuracy from 0.68 to 0.79 on GPT-5-mini and from 0.76 to 0.87 on Gemini-3 Flash. An ablation showed that episodic and procedural memory each contribute independently, and their combination consistently outperforms either alone. Notably, for qualitative diagnostic tasks, the tool-free full-memory configuration outperformed the tool-enabled baseline, suggesting that accumulated reasoning heuristics can substitute for noisy external specialist tools when the base model is strong. GPT-5-mini full-memory accuracy was stable across three random case-order permutations (mean 0.79, SD 0.025).
- Joint Optimization of Reasoning and Dual-Memory for Self-Learning Diagnostic Agent
Synthesis
Plain-language abstract This paper introduces SEA, a self-learning AI agent designed to improve its clinical diagnostic ability over time by accumulating and reusing experience, much like a human physician does. Rather than treating each patient case in isolation, SEA maintains a memory system that stores recent cases and distills them into reusable diagnostic rules, then uses reinforcement learning to improve both its reasoning and its memory management simultaneously.
Motivation Most LLM-based diagnostic agents treat each case independently, which prevents them from learning and adapting through experience the way clinicians do. Prior work focuses on what to diagnose rather than how to improve over time, leaving a gap in long-horizon, experience-driven learning for medical AI. The medical domain is especially challenging because clinical cases are information-dense and useful learning often requires abstraction into generalizable rules rather than verbatim storage.
Methodology SEA uses a dual-memory architecture inspired by human cognition: a short-term memory stores a bounded set of recent concrete cases (up to capacity K), and a long-term memory stores abstract diagnostic rules distilled from those cases via a consolidation step. The agent is trained with a reinforcement learning framework that produces structured reasoning trajectories and applies adaptive rewards optimizing both diagnostic accuracy and effective memory management decisions. The system is evaluated on two datasets: MedCaseReasoning for static diagnostic competence, and ER-Reason for simulating streaming deployment with ongoing feedback.
Results On the MedCaseReasoning dataset, SEA achieves 92.46% accuracy, outperforming the strongest baseline by +19.6 percentage points. On the long-horizon ER-Reason dataset, SEA attains the best final accuracy of 0.7214 and the largest improvement of +0.35 delta accuracy over 100 cases, while standard and RL-trained baselines show only marginal gains or even degradation. Expert clinical evaluation of the agent's consolidated rules yields strong scores for overall trust (4.216 out of 5), rule usefulness (3.946), and clinical correctness (3.865), indicating the induced rules are reliable and practically meaningful.
- Beyond Inference-Only Deployment: Comparing Weight-Based Consolidation Against Cascading Compaction
Synthesis
Plain-language abstract This paper asks whether AI coding assistants should update their own weights nightly based on user interactions, instead of relying on in-context summaries that get repeatedly compressed and discarded. The authors build a three-stage pipeline that extracts knowledge from daily conversations, generates synthetic training data, and fine-tunes a small language model using LoRA on a single consumer GPU overnight. They compare this approach against the context-compaction strategy used by current deployed assistants across ten simulated software development projects.
Motivation Large language models deployed as coding assistants never update their weights per user, so they cannot accumulate preferences, corrections, or project-specific knowledge across sessions. Platforms that carry forward summaries must repeatedly compress prior context at a roughly 6:1 ratio, and each compression cycle degrades what was retained. After only three such cycles, a significant fraction of knowledge is lost — yet the volume of relevant project history grows continuously while the context window does not.
Methodology The authors generated ten realistic multi-turn software development conversations (each 50,000–65,000 tokens, covering projects such as CLI tools, ML frameworks, and distributed systems) using Claude Sonnet 4. For each conversation, a three-stage consolidation pipeline ran: a reflection stage extracted structured memories classified as procedural, semantic, or episodic; a synthesis stage produced roughly 20 paraphrased user-assistant conversation pairs per fact (approximately 18,000 training examples per source conversation); and a training stage fine-tuned a Qwen2.5-7B-Instruct model via LoRA (rank 16, 8 epochs) on an NVIDIA A100. A parallel compaction condition simulated three cycles of 6:1 summarization plus fresh continuation conversations, matching the behavior of deployed coding assistants. Retention was measured on 1,146 test questions judged by an LLM evaluator.
Results Three cycles of cascading compaction retained 36.8 ± 3.0% of knowledge, compared to 80.4 ± 1.3% for weight-based consolidation — a 43.6 percentage-point gain (paired t(9) = 14.8, p < 0.001) that more than doubles what compaction preserves. The gains were largest for procedural corrections (36.3% vs 74.6%) and episodic project facts (31.5% vs 78.2%), while semantic memories were better preserved under both strategies. The paper also reports a methodological finding: median per-token validation cross-entropy tracks LLM-judged task accuracy almost perfectly (r = +0.99), while mean per-token cross-entropy is negatively correlated with accuracy (r = −0.51) due to a heavy-tailed token-loss distribution, making the mean a misleading training signal when the evaluator tolerates surface-form variation.
- From Storage to Experience: A Survey on the Evolution of LLM Agent Memory Mechanisms
Synthesis
Plain-language abstract This paper is a survey of how memory systems in AI agents powered by large language models (LLMs) have developed over time. The authors propose a three-stage evolutionary framework — Storage, Reflection, and Experience — to organize and explain the progression of memory designs, and use it to identify the core technical drivers and open challenges in the field.
Motivation LLMs are stateless by nature, meaning they cannot retain information across interactions on their own. This makes it hard for LLM-based agents to stay consistent over long, multi-step tasks or to learn from past mistakes. Prior survey work on agent memory was fragmented, split between engineering-oriented and cognitive-science-oriented perspectives, with no unified framework explaining why and how memory mechanisms have evolved.
Methodology The authors conduct a systematic literature survey organized around a novel three-stage taxonomy they formally define: Storage (faithful recording of interaction trajectories), Reflection (dynamic evaluation and refinement of stored records), and Experience (cross-trajectory abstraction of generalized behavioral patterns). They analyze the field using a 'Why-How-What' structure addressing three research questions about the drivers, path, and outcomes of memory evolution, and they also catalog relevant benchmarks across each stage.
Results The survey maps existing memory mechanisms onto the three-stage framework and identifies the core catalysts driving evolution: the need for long-range consistency, the challenges of dynamic environments, and the goal of continual learning. It highlights that the frontier Experience stage — characterized by active exploration and cross-trajectory abstraction using techniques such as Minimum Description Length compression of trajectory clusters — addresses bottlenecks in agent adaptability. The authors also identify gaps in benchmark coverage, particularly for the Experience stage, and call out distributed shared memory and multimodal memory fusion as critical directions for future work.
- Cognitive Architectures for Language Agents (CoALA)
Synthesis
Plain-language abstract This paper proposes CoALA (Cognitive Architectures for Language Agents), a conceptual framework for organizing and designing AI agents that use large language models (LLMs) to interact with the world. The authors draw on the history of cognitive science and symbolic AI — specifically production systems and cognitive architectures like Soar — to give a principled structure to a rapidly growing but terminologically fragmented field.
Motivation Researchers have built many different language agents that connect LLMs to memory, tools, and environments, but each work uses its own custom vocabulary (such as 'tool use', 'grounding', 'actions'), making it hard to compare systems, trace how the field is evolving, or build new agents on clean, consistent abstractions. There was no unifying framework to organize existing agents or guide future development.
Methodology The authors propose CoALA, which characterizes language agents along three dimensions: information storage (working memory and long-term memory subdivided into procedural, semantic, and episodic types); an action space (internal actions like reasoning and retrieval, and external actions like interacting with the environment); and a structured decision-making loop consisting of planning and execution phases. They use this framework to retrospectively survey and taxonomize a large body of recent language-agent work, and to prospectively identify open research directions.
Results CoALA successfully organizes a wide range of existing language agents under a common conceptual structure, showing that diverse systems can be understood as varying instantiations of the same memory, action, and decision-making components. The framework also highlights systematic gaps in current agents — particularly in long-term memory management and learning — and outlines actionable directions toward more capable, general-purpose language agents. The paper was published in Transactions on Machine Learning Research in February 2024.
- SEAGym: An Evaluation Environment for Self-Evolving LLM Agents
Synthesis
Plain-language abstract SEAGym is a testing environment for AI agents that improve themselves over time by editing their own setup—their prompts, memory, skills, tools, and configuration—rather than by retraining the underlying model. Instead of just checking whether a self-improved agent scores higher on a final task, SEAGym measures the improvement process itself: whether each self-edit actually helps on new tasks, whether gains stick or later collapse, and what they cost.
Motivation Self-evolving agents improve mainly by changing their agent harness—the structured execution layer around a base model. Existing evaluations reduce this to isolated task scores or a single sequential learning curve, which obscures whether a given update produces reusable improvement, overfits the recent tasks, increases cost, or harms older behavior. Most agent benchmarks are built for static evaluation, resetting agent state between isolated episodes and removing exactly the state persistence that self-evolution depends on.
Methodology SEAGym uses an RL-style environment formulation in which the self-evolving agent supplies both the task policy and the harness-update rule, while the environment defines task sampling, feedback, schedules, and snapshot assessment. It converts Harbor-compatible static benchmarks into reusable task sources organized into train batches and frozen evaluation views—update-validation, held-out in-domain transfer, out-of-domain transfer, replay diagnostics, and cost records—and saves agent snapshots and metric artifacts. Explicit schedule parameters (state reset, task reuse, batch size, update timing) let single-task adaptation, online transfer, and epoch-based batch learning be studied under one protocol. Task rollout is separated from method update, so methods such as ACE, TF-GRPO, and AHE connect through thin wrappers while keeping their native update rules; experiments instantiate the environment on Terminal-Bench 2.0 and HLE.
Results The evaluation views provide complementary signals about the evolution process rather than one summary number. Frequent updates may fail to improve held-out performance, validation gains do not always transfer to in-domain or out-of-domain test views, and useful intermediate snapshots can collapse later or recover. Batch size, source diversity, and the rollout model backend all affect harness reliability, showing that self-evolution dynamics depend on the evaluation schedule and setup, not just the update method.
- AutoMem: Automated Learning of Memory as a Cognitive Skill
Synthesis
Plain-language abstract AutoMem trains an agent to get better at managing its own memory, the way a person gets better at note-taking with practice. It gives the agent file-system operations (read, write, search, append) as memory actions on equal footing with its normal task actions, then uses a strong meta LLM to review whole episode traces (tens of thousands of steps) and improve both the memory scaffold the agent works within and, separately, the agent's own skill at making memory decisions.
Motivation Long-horizon tasks can run for 10^4-10^5 steps, far past what a human reviewer can practically read through to find where a memory decision went wrong; a single bad memory choice can stay hidden for thousands of steps before it matters. Existing memory systems treat memory as a fixed architectural module rather than a skill the agent can improve, so there's no natural way to optimize it beyond manual tuning.
Methodology Two outer loops wrap a shared inner-loop agent that treats a directory of files as its memory. Loop 1 (structure): a meta-LLM reads full episode traces, diagnoses memory-use failure patterns, and revises the agent's scaffold, prompts, file schema, action vocabulary. Loop 2 (proficiency): a meta-LLM selects the agent's own good memory decisions across many episodes as supervised training data and orchestrates LoRA fine-tuning of a dedicated memory-specialist model, while the task-action model stays frozen. Evaluated on three procedurally generated long-horizon games (Crafter, MiniHack, NetHack) with Qwen2.5-32B-Instruct as the base model.
Results Optimizing memory alone, without touching the model's task-action behavior, improves the base agent's performance roughly 2x-4x across the three games, and the optimized 32B model outperforms Qwen2.5-72B-Instruct on all three, becoming competitive with frontier systems like Claude Opus 4.5 and Gemini 3.1 Pro Thinking. The authors frame this as evidence that memory management is an independently learnable skill and a high-leverage optimization target for long-horizon agents.
- SelfMem: Self-Optimizing Memory for AI Agents
Synthesis
Plain-language abstract SelfMem gives an AI agent a set of memory tools and feedback signals, instead of a fixed rule for what to remember and how, and lets the agent figure out its own memory strategy. The idea, as the authors put it, is teaching the agent to fish rather than giving it a fish: rather than forcing a predefined summarization format, the agent inspects the raw conversation, decides what's worth writing to its memory workspace, and can revise that memory when a self-check flags a problem.
Motivation Existing agent-memory systems (Mem0, MemGPT, MemoryBank, A-Mem) rely on manually specified strategies for what to store, update, and retrieve, which are rigid across tasks and need hand-tuning. Different tasks and conversation histories need different memory behaviors, and no fixed schema fits all of them; the authors argue this calls for letting the agent adapt its own strategy rather than hand-crafting one.
Methodology SelfMem keeps the raw transcript as an immutable source of truth, accessible only through read-only tools like a SQL-queryable turns table, and gives the agent a separate memory workspace plus a memory action space: read the transcript, read/write/revise memory, check memory quality, and even extend its own memory toolkit. The agent decides what to store, compress, update, or leave for transcript retrieval. Evaluated on BEAM across conversation scales from 100K to 1M tokens against retrieval, compression, and agent-memory baselines.
Results SelfMem gets the highest official score and Pass0.5 at all three tested scales (100K, 500K, 1M tokens), improving the official score over the strongest baseline by 0.165, 0.141, and 0.134 respectively, and Pass0.5 by 14.3-17.0 percentage points. It's the best performer on 9/10 question types at 100K tokens (8/10 at 500K, 7/10 at 1M), and a model-guided strategy-refinement study shows further gains are possible on top of the base approach.
- One Recipe, Many Harnesses: What Self-Evolution Encodes Across Languages and Models
Synthesis
Plain-language abstract Holding a diagnostic-routed self-evolution recipe (TRIAGE) fixed across 8 programming languages and 3 base models, evolved coding-agent harnesses turn out to mostly compensate for recoverable execution defects (like test collisions or non-compiling code) rather than encode deep language-specific knowledge, and share an abstract playbook but not the concrete machinery across languages.
Motivation Self-evolving coding agents that edit their own prompts, hooks, memory, and tools show large empirical gains, but it's unclear whether these evolved harnesses encode genuine language expertise or are just compensating for fixable execution-environment bugs, and whether what's learned transfers across languages or models.
Methodology A fixed diagnostic-routed self-evolution recipe, TRIAGE, run across a grid of 8 programming languages by 3 base models, analyzing what kind of defect (recoverable execution defect vs. deeper knowledge gap) each evolved harness edit addresses, and measuring how much of each harness's machinery is shared across languages versus ecosystem-specific, plus testing a distilled universal harness against native per-language harnesses.
Results Evolved harnesses primarily compensate for recoverable execution defects (test-file collisions, non-compiling code, skipped test runs) rather than encoding deep language knowledge, with which defect dominates varying by language/model cell rather than following a fixed rule. Harnesses share an abstract playbook across languages but instantiate it with 20-40% ecosystem-specific machinery per harness, and a distilled universal harness recovers only 48-68% of the native per-language gains on some ecosystems.
- On the Fragility of Self-Improving Agents: Variance, Task Order, and Underspecification
Synthesis
Plain-language abstract A re-evaluation of memory-based self-improving web agents (Agent Workflow Memory, ReasoningBank) across WebArena, VisualWebArena, and SCUBA, adding multiple runs and randomized task ordering to standard single-run, fixed-order evaluation. Both additions expose that reported improvements are considerably less stable than prior single-run reports suggested.
Motivation Self-improving agents that write and reuse a textual memory bank across a stream of tasks are promoted as a path to reliable long-horizon automation, but their reliability under realistic conditions — repeated runs, unordered task streams — had not been stress-tested. In enterprise deployment, tolerance for early failure is low and mistakes compound silently.
Methodology The authors re-run Agent Workflow Memory and ReasoningBank with a stronger base model and harness, then extend evaluation along two axes: multiple runs of the same setting to quantify variance, and randomly shuffled task orders to test sensitivity to the default (often implicitly easy-to-hard) task curriculum. They then manually inspect agent-written memories to identify failure drivers, and test whether adding rubrics and environment feedback to memory construction narrows the gap.
Results Variance across runs increases in 71% of settings when a self-improving loop is stacked on a baseline agent; on WebArena's GitLab subset, the best/worst run gap widens from 4.4% (no memory) to 7.8% (ReasoningBank). Under the default task order, ReasoningBank gains 1.5% on average; under random shuffling, it degrades by 4.5%. Manual inspection attributes much of this to task and environment underspecification, which causes agents to write plausible but inapplicable memories; adding rubrics and environment feedback partially, but not fully, closes the degradation.
- Self-Evolving Coding Agents
Synthesis
Plain-language abstract A survey of coding agents that update their own framework, memory, skills, tools, models, or workflow structure from prior coding attempts, organized by what evolves, when it evolves, and what software-specific evidence drives it.
Motivation Coding agents now operate as interactive systems inside real development workflows, interpreting requirements, inspecting repositories, editing multiple files, running tests, diagnosing failures and generating patches. But in most systems the base model, prompts, tool interfaces, memory mechanisms and control flow are fixed after deployment, which is hard to sustain when codebases evolve, APIs and dependencies change, conventions vary across repositories, and bug fixing requires repeated cycles of localization, patching, execution and revision. Meanwhile software engineering supplies unusually concrete feedback: unit tests, compiler errors, runtime traces, lint warnings, CI results and human code reviews. An agent that cannot accumulate experience from that feedback repeats its mistakes across tasks and never adapts to project-specific context. Existing work on self-evolving agents mostly targets broad task environments and leaves the software-specific requirements uncharacterized.
Methodology The survey is framed as a guiding synthesis rather than a review of a settled paradigm, organized around three questions: what components evolve and through what mechanisms, when evolution occurs and what evidence drives it, and how such agents should be evaluated beyond the setting they evolved in. It first separates coding agents, self-evolving agents and self-evolving coding agents conceptually, then builds an object-centered taxonomy with five categories: agent framework self-evolution (self-modifying scaffolds and archive-based variant search), memory self-evolution (experience, repository and plan-abstraction memory), skill and tool self-evolution, model self-evolution (adversarial test evolution, coder-verifier co-evolution, self-play policy evolution), and workflow and topology self-evolution. Two orthogonal dimensions cross it: timing (task-time, post-task, stage-wise) and evidence type (outcome, environmental, trajectory-derived). Representative systems are tabulated against all three dimensions plus their software-engineering task domain. Inclusion is limited to work whose central contribution changes an agent component or behavior through coding-specific feedback; benchmark-only datasets and static agent systems are treated as evaluation context rather than as methods.
Results The synthesis finds that executable feedback, repository-level context and coding trajectories give software engineering a distinctive role as a domain for agent self-evolution, because a remembered strategy can be validated by tests rather than merely accumulated, and repository history supplies long-term signal about how a project changes. Memory self-evolution clusters into experience banks over prior issue-resolution trajectories including failures (SWE-Exp), hierarchical pools separating general from repository-specific experience (EvoCoder), subtask-granularity stores that avoid coarse whole-trajectory matching, commit-and-issue-grounded repository memory for code localization, and plan abstraction reused as later context (SAGE). Skill and tool self-evolution is distinguished by actionability: CODESKILL maintains a skill bank at task and event granularity and treats skill management as a learnable policy; gskill learns per-repository skill documents validated by whether agents in isolated environments produce passing patches; Socratic-SWE distills a skill registry from traces that then generates the training curriculum. Tool self-evolution is the least developed, with Live-SWE-Agent the main example of an agent creating and revising its own tools from a bash-only scaffold. The named challenges are feedback reliability, benchmark overfitting, safety, maintainability, cost and generalization. Two are emphasized: memory must be evolved selectively, since noisy logs, misleading tests, brittle patches and repository-specific conventions produce memories that hurt when retrieved uncritically; and framework-level evolution carries the strongest risk, because a harmful modification to the machinery that generates future actions can break the agent loop, degrade tool use, overfit to benchmark feedback or exploit weaknesses in the evaluation harness, so it requires validation, rollback and robustness checks rather than performance-driven search alone.
- LivingRAG: Augmenting Graph RAG with Experience
Synthesis
Plain-language abstract Graph RAG systems answer each query independently and discard the reasoning afterwards, so related later queries start from scratch. LivingRAG adds a writable experience store to a graph retrieval backbone, keeping for each verified answer the entity activation map that worked and a compact reasoning summary, and reusing them on two separate paths: fused into the retriever's starting activation, and inserted into the prompt as a scaffold. Across five online QA streams it improves accuracy over graph RAG baselines while cutting completion tokens 22.7% and estimated cost 12.1%, with grounding and novelty gates admitting only 27.4% of candidate experiences.
Motivation Reuse across an online query stream is not limited to repeated entities. Two questions may visit nearby regions of the retrieval graph with entirely different entities, or follow the same reasoning pattern with different subjects, as when two comparison questions both ask which person was born earlier. A measurement of the streams supports the distinction: direct entity overlap with an earlier query ranges from 4.30% to 76.69% by dataset, while graph-neighborhood overlap runs 80.45% to 99.70%, so an entity-keyed answer cache would miss most of the available reuse. The countervailing risk is that a writable store lets unsupported reasoning be written once and then amplified by every later query that reuses it.
Methodology The retrieval backbone is LinearRAG, unchanged: a passage-sentence-entity graph built with lightweight entity extraction and no LLM calls during indexing, query entity activation, propagation over the sentence-entity graph, and Personalized PageRank over the passage-entity graph. A verified experience stores the query, its embedding, a sparsified final activation vector, a compact summary, the answer, a timestamp and a grounding confidence. Experiences are scored against a new query by a convex combination of query-embedding cosine and activation-map cosine, and the top-K maps are fused into the initial activation vector with softmax weights scaled by stored confidence and deliberately not renormalized. Scaffold selection adds a masked-template similarity term that retrieval omits, because a scaffold only enters the prompt and cannot inject historical entities into graph retrieval. Write-back requires a novelty score computed against the base rather than the fused activation to avoid circularity, and a grounding score equal to the fraction of extracted atomic claims entailed by retrieved passages under an NLI model; novelty is checked first so NLI runs only on survivors, and the grounding score becomes the stored confidence. Evaluation runs 2WikiMultiHopQA, HotpotQA, MuSiQue, MuSiQue-full and WixQA as online streams with an empty initial store, generating with Qwen3.6 Plus, reporting contain-match and LLM-evaluation accuracy.
Results LivingRAG leads all baselines on the four multi-hop benchmarks, for instance 58.42 LLM-evaluation accuracy on MuSiQue-full against 52.71 for LinearRAG, 47.75 for GFM-RAG and 44.06 for HippoRAG2, and 70.25 against 66.00 on WixQA. Prompt tokens rise 3.5% weighted because scaffolds add context, completion tokens fall 22.7%, and total estimated cost falls from $51.05 to $44.87, a reduction on every dataset. The saving is not a late-stage artifact: per-segment traces show the system spending more completion tokens than its backbone in the earliest segments and turning negative once experience accumulates. Realized reuse differs sharply by stream, with graph transfer at 91.20% on MuSiQue and 0.00% on 2Wiki, where realized template reuse is 84.15% instead. Ablations match those traces, since removing activation fusion costs most where graph transfer is realized, removing scaffolds costs most on 2Wiki and cuts token savings from 23.6% to 8.3%, and removing the quality gate lowers accuracy on all three tested datasets. The stated limits are the store's lifecycle: nothing updates, downweights or deletes an accepted experience, and the fixed-corpus benchmarks contain no chronological updates or fact-validity intervals, so staleness cannot be evaluated.
Benchmarks
Benchmarks and datasets for long-term / multi-session / multi-turn agent memory (task types, dataset sizes, composition)
Key threads
- Task-type taxonomy is converging but uneven: single-hop / multi-hop recall, temporal reasoning, knowledge-update, and multi-session aggregation are well-covered (LoCoMo, LongMemEval), while abstention/adversarial-refusal, conflict-resolution, multi-party speaker attribution, and procedural/implicit memory are only just being added by 2026 benchmarks.
- Synthetic vs real-world data split: the dominant benchmarks (LoCoMo, LongMemEval) are LLM-synthesized via persona + event-graph pipelines, prompting a counter-movement toward genuinely human data (REALTALK 21-day) and topic-guided generation pipelines (AgenticAI-DialogGen) to control the synthetic distribution gap.
- Scenario expansion beyond dyadic Person-AI chat: 2026 benchmarks push into continuous lifelog/always-on wearable capture (LifeMem/EgoMem), multi-party group conversations (GroupMemBench), and multimodal interactions (MemLens, MemEye).
- Diagnostic and failure-mode evaluation is emerging as a complement to single-number accuracy: stress-testing failure modes (MemFail) and conflicting-memory diagnostic testbeds (Selective QA) measure where and how memory breaks rather than aggregate score.
- Procedural/agent-trajectory memory is a separate benchmark lineage from conversational recall: workflow induction over long-horizon web/task trajectories (Agent Workflow Memory) and implicit behavioral adaptation (ImplicitMemBench) target the procedural leg of the semantic/episodic/procedural triad.
Open gaps
- No unified harness spans the full task taxonomy: recall, temporal, knowledge-update, abstention, conflict-resolution, multi-party, procedural, and personalization each live in separate benchmarks with incompatible formats and metrics, so cross-system comparison is impossible.
- Abstention / hallucination-resistance (refusing questions about never-disclosed facts) is almost never reported despite being a first-class LongMemEval ability; most LoCoMo leaderboards omit it entirely, so adversarial 'unanswerable' splits are under-resourced.
- Procedural and implicit memory are barely benchmarked relative to semantic/episodic recall; ImplicitMemBench and Agent Workflow Memory are early and isolated, with no standard task suite for skill/workflow reuse across sessions.
- Dataset scale is small and possibly contaminated: LoCoMo has only 10 conversations / 1,813 questions, raising statistical-power and train-test-leakage concerns for systems now scoring >94%, yet scalable synthetic-generation pipelines that preserve answerability ground truth are immature.
- Real-world, multi-party, and multimodal/lifelog memory benchmarks are nascent (REALTALK, GroupMemBench, MemLens, MemEye, LifeMem) with no shared evaluation protocol, leaving open how to score speaker-attribution, visual-evidence retention, and ambient-capture recall consistently.
- Agent Workflow Memory
Synthesis
Plain-language abstract This paper introduces Agent Workflow Memory (AWM), a method that teaches language model-based web agents to extract reusable task routines — called workflows — from past experience and apply them to guide future actions. Rather than treating each task in isolation, AWM lets agents build up a growing library of skills, from simple steps like finding a place by name to more complex multi-step procedures composed from earlier workflows.
Motivation Current language model agents struggle with long, complex web navigation tasks because they process each task independently and do not learn from past successes or failures. They lack the ability to extract and reuse common task patterns across similar contexts, making them brittle when the task environment changes even slightly.
Methodology AWM operates in two modes: offline, where it extracts workflows from annotated training trajectories before test time, and online, where it induces workflows on the fly from self-generated predictions judged correct by an evaluator. The method was evaluated on two major web navigation benchmarks — Mind2Web (1000+ tasks across 200+ domains) and WebArena (execution-based evaluation covering travel, shopping, social media, and other domains) — using language model agents that maintain and grow a memory of induced workflows over time.
Results AWM improved baseline success rates by 24.6% relative on Mind2Web and 51.1% relative on WebArena, while also reducing the number of steps needed to solve WebArena tasks. It outperformed methods that use human-expert-written workflows by 7.9% on WebArena. In cross-task, cross-website, and cross-domain generalization evaluations, online AWM surpassed baselines by 8.9 to 14.0 absolute percentage points, with the performance gap growing as the train-test distribution divergence increased — reaching as high as 22.5 points after rolling over only tens of examples.
- Evaluating Very Long-Term Conversational Memory of LLM Agents
Synthesis
Plain-language abstract This paper introduces LoCoMo, a dataset and benchmark for testing whether AI language models can remember and reason about information across very long conversations — up to 35 chat sessions and around 300 turns. The authors also build and evaluate several model approaches against human performance on tasks like question answering, event summarization, and multi-modal dialogue generation.
Motivation Prior work on long-term open-domain dialogue only evaluated models over contexts spanning at most five chat sessions, leaving it unknown how well large language models or retrieval-augmented generation systems handle truly extended conversational histories. This gap matters because real human relationships involve months or years of accumulated shared context that a useful conversational AI should be able to track.
Methodology The authors created a machine-human pipeline that uses LLM-based agent architectures to generate long-term dialogues grounded in character personas and temporal event graphs; agents were also given the ability to share and react to images. The generated conversations were then verified and edited by human annotators to ensure long-range consistency and fidelity to the event graphs, resulting in the LoCoMo dataset of conversations averaging 300 turns and 9,000 tokens each over up to 35 sessions.
Results Experiments show that current LLMs struggle to understand lengthy conversations and to track long-range temporal and causal dynamics across sessions. Techniques such as long-context LLMs and retrieval-augmented generation offer some improvement, but all tested models still fall substantially short of human performance on the benchmark tasks.
- Synthius-Mem: Brain-Inspired Hallucination-Resistant Persona Memory Achieving 94.4% Memory Accuracy and 99.6% Adversarial Robustness on LoCoMo
Synthesis
Plain-language abstract Synthius-Mem is a memory system for AI agents that stores what is known about a person rather than replaying raw conversation history. Drawing on how the human brain organizes memory into specialized subsystems, it decomposes conversations into six typed domains — biography, experiences, preferences, social circle, work, and psychometrics — and retrieves structured facts at query time. On the LoCoMo benchmark it achieves 94.37% overall accuracy and 99.55% adversarial robustness while consuming roughly five times fewer tokens than full-context replay.
Motivation Current LLM memory approaches — sliding windows, summarization, embedding-based retrieval, and flat fact extraction — each reduce token cost but introduce information loss, semantic drift, or uncontrolled hallucination about the user. No published system on the LoCoMo benchmark reported adversarial robustness, meaning the ability to refuse questions about facts the user never disclosed. The paper addresses this gap by arguing that domain-agnostic storage discards the structural advantages that neuroscience shows different memory types require.
Methodology Synthius-Mem uses a multi-stage pipeline: conversations are parsed and chunked, then six parallel domain-specific extractors pull typed facts into separate stores for biography, experiences, preferences, social circle, work, and psychometrics (the last using nine validated psychological frameworks). Each domain undergoes its own consolidation and deduplication pass. At inference time, a planner LLM selects relevant domains and a CategoryRAG component retrieves structured facts with a reported mean latency of 21.79 ms. The system was evaluated on the LoCoMo benchmark (ACL 2024), which contains 10 multi-session conversations and 1,813 questions spanning single-hop recall, multi-hop reasoning, temporal reasoning, open-domain knowledge, and adversarial false-premise questions.
Results Synthius-Mem achieves 94.37% accuracy on LoCoMo, exceeding the prior best published system MemMachine (91.69%) and human performance (87.9 F1). Core memory fact accuracy reaches 98.64%. Adversarial robustness — refusal to hallucinate facts the user never disclosed — reaches 99.55%, a metric no competing system reports. Token consumption is approximately five times lower than full-context replay at 500 messages, where full-context replay itself achieves only 85.46% in the authors' controlled evaluation.
- LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memory
Synthesis
Plain-language abstract LongMemEval is a benchmark for testing how well AI chat assistants remember and reason over information shared across many conversations with a user. It contains 500 carefully crafted questions embedded within long, scalable user-assistant chat histories, covering five memory abilities: extracting information, reasoning across sessions, handling time, updating knowledge, and knowing when not to answer.
Motivation Current AI chat assistants struggle to remember personal details and preferences across extended interactions, yet existing benchmarks for evaluating this mostly use human-to-human dialogues, lack task-oriented exchanges, and cover only short histories of a few thousand tokens. There was no rigorous, scalable benchmark that tested the full range of memory abilities needed for sustained, personalized user-AI interactions.
Methodology The authors built LongMemEval with 500 questions spanning five memory ability categories, embedded within freely scalable synthetic chat histories. They evaluated commercial systems (ChatGPT and Coze) and long-context LLMs on these questions, then developed a unified three-stage framework (indexing, retrieval, reading) and proposed specific optimizations: session decomposition for finer-grained value storage, fact-augmented key expansion at indexing time, and time-aware query expansion to sharpen retrieval scope.
Results Commercial chat assistants and long-context LLMs showed roughly a 30% accuracy drop when memorizing information across sustained interactions compared to offline reading with the full history provided. ChatGPT tended to overwrite crucial information as conversations continued, while Coze often failed to record indirectly provided user information. The proposed memory design optimizations substantially improved both memory recall and downstream question-answering performance on LongMemEval.
- REALTALK: A 21-Day Real-World Dataset for Long-Term Conversation
Synthesis
Plain-language abstract REALTALK is a dataset of real conversations collected over 21 days from messaging apps, where pairs of people who initially met through those apps exchanged daily messages. The dataset contains 10 unique conversations totaling more than 16,000 words each, and is used to evaluate whether AI language models can hold long-term, emotionally aware conversations the way humans do.
Motivation Most research on long-term dialogue systems uses synthetic conversations generated by AI models rather than real human exchanges, leaving it unclear whether those simulated dialogues capture the emotional nuance and persona consistency of genuine human interaction. REALTALK was created to fill that gap by providing an authentic benchmark that can be directly compared against LLM-generated conversation datasets.
Methodology Ten participants each engaged in two separate 21-day conversation threads with different partners via messaging apps, producing conversations that span approximately 21 daily sessions per pair. The dataset was analyzed for emotional intelligence attributes and persona consistency, and compared against LLM-generated conversations. Two benchmark tasks were then defined: persona simulation, where a model must continue a conversation on behalf of a specific user given prior dialogue context, and memory probing, where a model must answer questions requiring recall of information from earlier in a long conversation.
Results Analysis showed that real-world conversations contain more diverse emotional expressions and greater variation in persona stability than synthetic LLM-generated dialogues. Benchmark experiments found that models struggle to simulate a specific user's conversational style from dialogue history alone, but fine-tuning on that user's own chat history improves persona emulation. Existing models also faced significant challenges in recalling and leveraging long-term context from real-world conversations.
- Evaluating Memory Capability in Continuous Lifelog Scenario
Synthesis
Plain-language abstract This paper introduces LifeDialBench, a new benchmark for testing how well AI memory systems can handle continuous spoken conversations recorded by wearable devices like smart glasses. Unlike existing benchmarks that focus on chatting directly with an AI, this one evaluates memory over the kind of multi-person, everyday dialogues that an always-on microphone would capture. The paper also proposes a new evaluation protocol that respects the time-ordering of events, mimicking how such a system would work in practice.
Motivation Current AI memory benchmarks focus on one-on-one person-AI chat sessions and do not address the emerging use case of wearable devices that continuously record ambient conversations throughout the day. Existing approaches to extending memory — such as feeding ever-longer text into a model — become prohibitively expensive and still underperform. There was no public benchmark designed for the continuous, multi-person, time-stamped dialogue streams that wearable lifelogging devices produce.
Methodology The authors built LifeDialBench from two complementary data sources: EgoMem, derived from real-world egocentric video recordings (transcribed via automatic speech recognition), and LifeMem, constructed through a hierarchical life-simulation framework using a virtual community with human-in-the-loop review. Question-answer pairs cover four types — single-event, event detail, multi-event, and temporal information queries — spanning timescales from 30-second clips to week-level summaries. Crucially, the paper introduces an Online Evaluation protocol that enforces temporal causality, evaluating memory systems incrementally as data is stored rather than all at once after the fact.
Results Experiments reveal a counterintuitive finding: sophisticated memory systems with complex architectures fail to outperform a simple retrieval-augmented generation (RAG) baseline. The results show that over-designed structures and lossy compression hurt performance, and that preserving raw conversational text with high fidelity is more important than elaborate memory abstractions. Temporal retrieval is identified as a universal bottleneck across all systems tested.
- GroupMemBench: Benchmarking LLM Agent Memory in Multi-Party Conversations
Synthesis
Plain-language abstract GroupMemBench is a benchmark for testing how well AI agent memory systems handle conversations involving multiple people — such as workplace channels or group chats — rather than simple back-and-forth with a single user. It generates realistic multi-party conversations and poses questions that require knowing who said what, to whom, and in whose vocabulary, exposing gaps that existing benchmarks never measure.
Motivation AI memory systems and the benchmarks used to evaluate them are built around one-on-one conversations, yet real deployments increasingly involve groups where multiple users talk to each other and to the agent simultaneously. This mismatch leaves three important properties of group memory untested: the complex social dynamics of group dialogue, the need to track beliefs separately for each speaker, and the way vocabulary shifts depending on the audience — for example, the word 'token' means something different to an NLP engineer than to a systems engineer.
Methodology The benchmark is built in two stages. First, a graph-grounded synthesis pipeline creates multi-party conversations by encoding domains, topics, phases, and users in a directed knowledge graph, then generating messages conditioned on per-user personas and target audiences, with controllable reply structure to produce threaded debates and cross-topic shifts. Second, an adversarial query pipeline generates questions bound to specific asking users across six categories — multi-hop reasoning, knowledge update, term ambiguity, user-implicit reasoning, temporal reasoning, and abstention — and iteratively refines them through a Solve-Judge-Refine loop to ensure each query defeats a competent retrieval baseline before being accepted. The resulting corpus contains 120,000 turns across 123 topics.
Results Benchmarking five leading agent memory systems on GroupMemBench revealed a sharp performance collapse: the strongest system reached only 46.0% average accuracy, with knowledge update dropping to 27.1% and term ambiguity to 37.7%. A simple BM25 keyword-retrieval baseline, which performs no memory transformation at all, matched or exceeded most agent memory systems at effectively zero cost, Pareto-dominating four of the five systems. Failure analysis showed that retrieval failures — not reasoning failures — account for 41–79% of errors, meaning memory ingestion pipelines are discarding the structural and speaker-identity information that group memory depends on.
- ImplicitMemBench: Measuring Unconscious Behavioral Adaptation in Large Language Models
Synthesis
Plain-language abstract This paper introduces ImplicitMemBench, the first benchmark designed to test whether large language models can automatically adapt their behavior based on past experience — without being explicitly reminded to do so. It evaluates 17 AI models on 300 tasks drawn from three types of unconscious memory studied in cognitive science, finding that even the best models fall well short of human performance.
Motivation Existing benchmarks for AI memory focus on explicit recall — directly asking a model to retrieve a fact it was told. But effective assistants also need implicit memory: the ability to automatically apply a learned procedure or avoid a repeated mistake without being prompted. No prior benchmark measured this kind of unconscious behavioral adaptation, leaving a critical gap in understanding how well AI assistants actually learn from experience.
Methodology The benchmark operationalizes three cognitively grounded constructs drawn from nondeclarative memory research: Procedural Memory (one-shot skill acquisition that persists after distracting interference), Priming (theme-driven behavioral bias measured via paired experimental and control instances), and Classical Conditioning (whether stimulus-response pairings shape first decisions). All 300 items follow a unified Learning/Priming–Interfere–Test protocol scored on the first attempt, with passive scenario-driven triggers rather than explicit retrieval cues.
Results No model exceeded 66% overall accuracy. Top performers were DeepSeek-R1 at 65.3%, Qwen3-32B at 64.1%, and GPT-5 at 63.0%, all well below human baselines. Analysis revealed dramatic asymmetries between memory subtypes, with inhibition (avoiding a previously failed action) succeeding only 17.6% of the time versus preference-based priming at 75.0%, pointing to universal architectural bottlenecks that parameter scaling alone does not address.
- MemFail: Stress-Testing Failure Modes of LLM Memory Systems
Synthesis
Plain-language abstract MemFail is a diagnostic benchmark for testing where and why AI memory systems break down. When AI assistants need to remember information across long conversations, they rely on memory systems that compress, store, and retrieve facts. MemFail isolates exactly which part of that pipeline fails — summarization, storage, or retrieval — rather than just measuring whether a final answer is right or wrong.
Motivation AI agents increasingly depend on external memory systems to stay consistent across long interactions, but existing benchmarks only report overall question-answering accuracy and treat memory systems as black boxes. This makes it impossible to pinpoint whether a wrong answer came from the system losing information during compression, storing facts incorrectly, or retrieving the wrong memories — a gap that prevents targeted improvements to memory architectures.
Methodology The authors formalized memory systems as a composition of three operations — summarization, storage, and retrieval — and identified the failure modes each can introduce. They then built five adversarially designed datasets spanning four tasks (Conditional-Facts, Coexisting-Facts, Persona-Retrieval, and Long-Hop) to isolate these failure modes. Four state-of-the-art memory systems — Mem0, A-MEM, SimpleMem, and StructMem — were evaluated across these tasks using multiple underlying LLMs (GPT-4.1-mini, Haiku-4.5, GPT-5.4-mini, Gemini-3.1) and varying retrieval counts.
Results No single memory system dominated: graph-based StructMem excelled at causal reasoning tasks but failed on coexisting-fact retrieval, while Mem0 showed the opposite pattern. Scaling either the number of retrieved memories or the strength of the underlying LLM yielded little or no improvement, and sometimes degraded performance, indicating that current systems are limited by architectural constraints rather than model intelligence. The relationship between token usage and accuracy was task-dependent: tasks bottlenecked by summarization failures improved with more verbose storage, while retrieval-heavy tasks suffered when large memories polluted the embedding space.
- Selective QA over Conflicting Multi-Source Personal Memory: A Diagnostic Testbed and Method Comparison
Synthesis
Plain-language abstract This paper studies how AI systems can answer personal questions when the evidence they have access to is conflicting or incomplete — and when they should simply refuse to answer. The authors build a benchmark and compare several methods, ranging from simple baselines to large language models, on this task.
Motivation Personal AI agents increasingly maintain memory from multiple sources (calendars, messages, notes, etc.), and those sources often contradict each other. Existing benchmarks do not isolate whether a system fails because of bad evidence or because it cannot resolve conflicts, leaving a diagnostic gap that this work directly addresses.
Methodology The authors construct a benchmark of 34,560 instances built from 18 question templates spanning 8 reasoning types, 480 synthetic personas, and 4 random seeds, with controlled source distortions and deterministic ground truth. They evaluate baselines with no source access, single-source access, structured fusion methods, and frontier large language models, measuring both standard accuracy and selective accuracy under abstention.
Results The best trained fusion resolver achieves 80.3% accuracy overall, compared to 70.0% for the strongest prompt-only LLM baseline. When abstention is allowed, the fusion resolver reaches 85.3% selective accuracy at 78.3% coverage, while the best LLM reaches 71.0% selective accuracy at 95.4% coverage. Different model types show different strengths across the eight reasoning types. All data, code, and cached outputs are released for reuse.
- AgenticAI-DialogGen: Topic-Guided Conversation Generation for Fine-Tuning and Evaluating Short- and Long-Term Memories of LLMs
Synthesis
Plain-language abstract This paper introduces AgenticAI-DialogGen, a software framework that automatically generates realistic, topic-organized conversations for training and testing AI language models on memory tasks. It also releases a new dataset called TopicGuidedChat (TGC) built from these generated conversations, which encodes both short-term and long-term memory cues for each pair of simulated speakers.
Motivation Existing conversational datasets lack the structure needed to train language models to reliably remember and reference information across a conversation — either they test short question-answering without capturing speaker personality, or they capture free-form dialogue without organizing it around coherent topics or memory. Creating such datasets manually is expensive and hard to do consistently, creating a gap that prevents progress on memory-aware conversational AI.
Methodology The framework takes an unstructured conversational dataset as input — primarily the Multi-Session Chat (MSC) dataset, restricted to 1,001 speaker pairs with four sessions each — and runs it through a pipeline of coordinated LLM-based modules and agents. These components preprocess conversations, extract factual knowledge triples, group them into topics, build per-speaker knowledge graphs, generate speaker personas, simulate multi-turn dialogues using LangGraph-based agents, validate and refine the output for topical adherence and quality, and finally produce memory-grounded question-answer pairs. The resulting TGC dataset stores long-term memory as structured knowledge graphs and short-term memory as simulated conversational turns.
Results Human and automatic evaluations show that AgenticAI-DialogGen improves discourse quality and topic coherence compared to baselines. Lightweight language models fine-tuned on the TGC dataset outperformed larger zero-shot models on memory-grounded tasks, demonstrating that the dataset's structured memory design provides practical utility for training memory-aware conversational systems.
- MemLens: Benchmarking Multimodal Long-Term Memory in Large Vision-Language Models
Synthesis
Plain-language abstract MemLens is a benchmark designed to test how well large vision-language models (AI systems that handle both images and text) can remember and reason over long, multi-session conversations. It contains 789 questions that require retrieving and connecting visual and textual evidence spread across conversation histories ranging from 32,000 to 256,000 tokens, and it evaluates two competing approaches to giving these models long-term memory.
Motivation As AI assistants handle longer conversations involving both images and text, they need to reliably recall and reason over past interactions. Two approaches have emerged — expanding the model's native context window and using external memory stores with retrieval — but no existing benchmark directly compared the two on questions that genuinely require visual evidence. Prior text-only benchmarks ignored images entirely, and multimodal conversational benchmarks allowed most questions to be answered from text alone, leaving the harder multimodal memory problem unevaluated.
Methodology The authors constructed MemLens using a four-stage pipeline modeled on the needle-in-a-haystack paradigm: for each question, a coherent multi-session chat history is built with evidence distributed across one or more user-assistant sessions alongside topically related distractor turns. Questions span five memory abilities — information extraction, multi-session reasoning, temporal reasoning, knowledge update, and answer refusal — at four standardized context lengths (32K, 64K, 128K, and 256K tokens) under a cross-modal token-counting scheme. They then evaluated 27 large vision-language models and 7 memory-augmented agents across all lengths, and ran an image-ablation study to confirm the benchmark requires visual evidence.
Results Removing evidence images caused accuracy for two frontier models to collapse below 2% on the 80.4% of questions that have image-based evidence, confirming the benchmark is genuinely multimodal. Long-context models performed well at shorter lengths through direct visual grounding but degraded as conversation length grew, while memory-augmented agents were more length-stable but lost visual fidelity when compressing memories at storage time. Multi-session reasoning capped most evaluated systems below 30% accuracy, and neither approach alone came close to solving the full benchmark, pointing toward hybrid architectures that combine long-context attention with structured multimodal retrieval.
- MemEye: A Visual-Centric Evaluation Framework for Multimodal Agent Memory
Synthesis
Plain-language abstract MemEye is a benchmark and evaluation framework for testing how well AI agents remember and reason over visual information across long conversations. It introduces 371 question-answer pairs spanning eight everyday life scenarios, each tagged by how fine-grained the required visual evidence is and how complex the memory reasoning must be, then tests 13 different memory systems to reveal where they break down.
Motivation Existing long-term memory benchmarks for AI agents are mostly text-centric: even when images are present, many questions can be answered from captions or dialogue context alone, without retaining the original visual evidence. There is also little coverage of questions that require tracking how a visual scene changes over time. This leaves two core failure modes undiagnosed: agents losing fine-grained visual details during memory compression, and agents failing to synthesize a coherent current state when earlier observations are superseded by new ones.
Methodology The authors built a two-dimensional evaluation framework. The X-axis captures visual evidence granularity across four levels — scene-level, region-level, instance-level, and pixel-level — reflecting how much detail must be preserved from images. The Y-axis captures memory reasoning depth across three levels: atomic retrieval of a single fact, relational association of evidence across sessions, and evolutionary synthesis where the agent must resolve conflicts and track state changes. A benchmark of 371 mirrored multiple-choice and open-ended questions was constructed across 221 sessions, 848 dialogue rounds, and 438 images from eight life-scenario tasks. Questions were validated with ablation-driven gates to check answerability, shortcut resistance, visual necessity, and reasoning structure. Thirteen memory methods were evaluated across four vision-language model backbones.
Results No current memory system comes close to saturating the benchmark. The best-performing method, SRAG(V), achieved an LLM-as-a-Judge score of 0.49 on open-ended questions and an exact-match score of 0.62 on multiple-choice questions. Performance consistently degrades as visual granularity increases from scene-level to pixel-level and as reasoning depth increases from atomic retrieval to evolutionary synthesis. A key trade-off emerged: text-based memory methods manage state changes better but lose fine-grained visual details, while image-based memory methods preserve visual evidence but struggle with temporal validity. Cross-topic scaling experiments further showed that specialized memory mechanisms become more important as conversation history grows longer and more thematically diverse.
- Evaluating LLM-based Agents for Multi-Turn Conversations: A Survey
Synthesis
Plain-language abstract This paper surveys how researchers evaluate AI chatbots and assistants built on large language models when those systems must hold multi-turn conversations — exchanges that unfold over many back-and-forth messages rather than a single prompt. The authors reviewed nearly 250 published studies to map out what is being evaluated and how, producing two classification frameworks that together cover the full range of current evaluation practice.
Motivation AI conversational agents powered by large language models are increasingly deployed in customer service, personal assistants, and other settings that require sustained, context-aware dialogue. Despite this growth, the field lacked a systematic overview of how such multi-turn systems are evaluated — what dimensions matter and what measurement methods are available — leaving practitioners without a consolidated reference.
Methodology Using a PRISMA-inspired systematic review process, the authors examined nearly 250 scholarly sources from a range of publication venues. From this corpus they constructed two interrelated taxonomy systems: one defining what to evaluate (task completion, response quality, user experience, memory and context retention, planning and tool integration) and one categorizing how to evaluate (annotation-based evaluations, automated metrics such as BLEU and ROUGE, hybrid human-plus-quantitative strategies, and self-judging methods that use LLMs as evaluators).
Results The survey produced a structured, dual-taxonomy framework covering both evaluation dimensions and evaluation methodologies for LLM-based multi-turn conversational agents. The framework captures traditional language-understanding metrics alongside newer techniques suited to the dynamic, interactive nature of multi-turn dialogue, offering a consolidated foundation for researchers and practitioners assessing conversational AI systems.
- Recent Trends in Personalized Dialogue Generation: A Review of Datasets, Methodologies, and Evaluations
Synthesis
Plain-language abstract This paper is a systematic survey of personalized dialogue generation — the field of building conversational AI systems that tailor their responses to individual users. The authors review 22 datasets, analyze 17 research papers published at top NLP conferences between 2021 and 2023, and summarize the evaluation metrics used across this body of work.
Motivation Personalization is increasingly important for conversational agents, especially as large language models can generate fluent but generic responses. The field lacks a unified definition of personalization — it can mean giving an agent a persona, modeling a user's traits, or both — and no comprehensive survey had catalogued the datasets, methods, and evaluation practices across this rapidly growing area.
Methodology The authors conducted a keyword-based literature search of top NLP venues (ACL, NAACL, EMNLP, AAAI, and others) covering 2021 through October 2023, selecting 17 seminal works. They systematically categorized 22 datasets by language, persona representation type (descriptive sentences or key-value pairs), data source (crowdsourcing or social platforms such as Reddit and Weibo), and features such as persona grounding labels and multi-session support. They then identified five distinct problem types across the surveyed methods and compiled a summary of evaluation facets and metrics.
Results The survey identifies five distinct problem formulations within personalized dialogue generation and highlights both benchmark datasets (such as PersonaChat and ConvAI2) and newer datasets with richer features including knowledge graphs, empathy signals, and out-of-distribution personas. The authors note strong language and domain biases across datasets — most are English or Chinese, and several are domain-specific rather than truly open-domain. The paper also surveys recent progress by large language models on personalized dialogue tasks and outlines open challenges and directions for future research.
- StreamMemBench: Streaming Evaluation of Agent Memory for Future-Oriented Assistance
Synthesis
Plain-language abstract StreamMemBench is a streaming benchmark that tests whether a personal-agent memory system can turn what it observes and how users interact with it into future-oriented assistance. Built on EgoLife egocentric lifelogs, it anchors each evaluation on a hidden piece of user-specific evidence and wraps a two-step task around it: an initial task that depends on the evidence, then a follow-up task that tests whether the agent reused both the evidence and the user's feedback. Four metrics diagnose evidence retention, feedback incorporation, initial evidence use, and follow-up reuse.
Motivation A central job of personal-agent memory is to carry stored observations and prior interactions forward into later, similar tasks, but existing memory benchmarks test dialogue recall or task improvement in isolation and usually rely on scripted or synthesized dialogues whose feedback is not tied to verifiable observations. That leaves the trajectory from streaming observations to later assistance largely untested — and even commercial assistants such as ChatGPT and Gemini store information that fails to help when it is actually needed.
Methodology In the construction stage an anchor agent processes five-minute EgoLife segments in stream order and extracts a user-specific evidence anchor plus two application-oriented queries, and a review agent retains a candidate only if both queries satisfy Leak=0 (the query does not reveal the evidence), Need=1 (ignoring the anchor yields a wrong or generic answer), and Natural=1 (it reads as a plausible request). In the evaluation stage the memory system ingests the lifelog chronologically, answers the initial task, receives confirming or correcting feedback from a user simulator, commits that interaction to memory, and then answers a follow-up task grounded in the same anchor; an evaluation agent scores Fidelity, Feedback Incorporation, Initial Evidence Use, and Follow-up Reuse against atom-level checklists, and the Fidelity−IEU / Fidelity−FUR gaps localize failures.
Results Across eight systems — two retrieval baselines (RAGraw, RAGext) and six memory systems (A-Mem, Mem0, EverMemOS, MemOS, MemoryOS, MemSkill) — on two backbones, current memory systems are not yet reliable for future-oriented assistance: they often fail to use evidence from egocentric observations in the initial task and to turn interaction feedback into reusable follow-up behavior. The failures are not explained by storage alone — systems frequently retain the evidence (with some Fidelity inflated by raw-text retention) yet do not use it — which motivates evaluation that traces each piece of evidence from its first appearance in the stream through initial use, feedback incorporation, and follow-up reuse.
- MemTrace: Probing What Final Accuracy Misses in Long-Term Memory
Synthesis
Plain-language abstract MemTrace is a benchmark for testing how well an AI assistant remembers facts about a user across many conversations. Instead of scoring isolated questions, it tracks each individual fact—like a user's job title—and repeatedly asks about it under different conditions: long after it was mentioned, when it has since changed, or when the question contains false information. This reveals failures that a single overall accuracy score hides, such as a system that recalls a user's current role correctly but invents a false history of how they got there.
Motivation Long-term memory benchmarks usually aggregate accuracy over question rows or interaction episodes, treating questions that probe the same underlying fact as independent items. That makes it impossible to hold a fact fixed and ask how a system behaves as conditions around it change—whether it still recalls a fact after many sessions, whether it tracks how the fact evolved, and whether it behaves safely when evidence is missing or contradicted. Two systems with similar pooled scores can fail in entirely different ways, and aggregate scoring cannot show which.
Methodology MemTrace makes the knowledge point—a single typed fact about the user—the unit of measurement, and probes each fact along three controlled dimensions: memory age (how many sessions ago it appeared), question type (current state, an earlier state, or the trajectory of change), and evidence condition (present, missing, or contradicted by a false premise). It comprises 835 typed knowledge points from 20 users, expanded into 15,422 question rows and over 200,000 scored answers, and evaluates 13 memory-system configurations across four paradigms: long-context models, retrieval-augmented systems, external-memory stores, and agentic-memory architectures. A diagnostic step classifies each failure by whether the needed evidence was unreachable or reachable but unused.
Results Performance varies systematically across all three dimensions. Long-context systems answer recent facts well but lose accuracy as facts age, especially on trajectory questions; RAG systems, including graph-based retrieval, handle current and earlier-state questions better than questions about change over time; some external-memory systems decline almost all questions about facts that were never mentioned yet rarely correct a false premise. The dominant remaining bottleneck is evidence use, not retrieval: when systems fail, the evidence was already retrievable about 10× more often than it was missing, so improving memory depends on using reachable evidence rather than storing or retrieving more.
- MemSyco-Bench: Benchmarking Sycophancy in Agent Memory
Synthesis
Plain-language abstract MemSyco-Bench is a benchmark that tests a specific failure mode in AI agents with long-term memory: sycophancy, where an agent trusts a memory of something the user said or believed before, even when that memory is outdated, out of scope, or contradicted by current evidence. Existing memory benchmarks mostly test whether an agent can retrieve the right memory; this one tests whether the agent uses a retrieved memory correctly once it has it.
Motivation The authors first show the problem is real: adding a plausible-but-wrong memory snippet before an objective factual question drops accuracy across all tested models and roughly doubles the rate at which the agent adopts the incorrect claim. They then show existing benchmarks (LongMemEval, LoCoMo, STALE, PersonaMem) can't isolate this: 47.4-66.1% of their errors come from failed retrieval, versus only 5.8-13.7% from correct-retrieval-but-wrong-use, so post-retrieval reasoning failures are essentially invisible in current scores.
Methodology MemSyco-Bench defines five task categories matched to the decisions an agent should make about a retrieved memory: reject it as factual evidence, respect its scope, resolve a conflict between memory and objective evidence, track that a memory has been updated, and use a genuinely valid memory for personalization. Multiple memory systems and backbone models are evaluated across these categories.
Results In the preliminary study, injecting a misleading memory cue drops factual accuracy on DeepSeek-V4-Flash from 56.1% to 40.2% and raises its sycophancy rate from 24.3% to 52.3%, with similar (smaller) effects on the other tested models. Full benchmark results show current memory systems generally increase sycophancy and struggle to balance personalization against factual reliability.
- MemOps: Benchmarking Lifecycle Memory Operations in Long-Horizon Conversations
Synthesis
Plain-language abstract MemOps is a benchmark that reframes long-term conversational memory as a lifecycle of explicit operations (remembering, forgetting, updating, reflecting, and their compositions) rather than as static question answering. Each memory event is a structured trace specifying its trigger, target, scope, state transition, and supporting evidence. A controllable pipeline embeds these operations into long, task-oriented conversations, producing gold operation traces and six categories of operation-level probes evaluated under both adjacent-evidence and long-context settings. Across long-context, retrieval-based, parametric, and managed-memory systems, MemOps disentangles failure modes that final-answer accuracy alone conceals.
Motivation Existing long-term memory benchmarks such as LoCoMo, LongMemEval, MemBench, and others evaluate almost exclusively through downstream question answering, scoring only the correctness of a final answer. That black-box formulation conflates heterogeneous causes of failure (missing the introduction of a relevant fact, binding an operation to the wrong target, or relying on a stale value after a correction) and can credit a correct answer that rests on an inconsistent or unsafe memory state. This is most acute in dynamic long-horizon interaction, where memory functions as a lifecycle process: a user introduces a fact, corrects it, asks that part be forgotten, or implicitly signals a preference, each of which is a distinct operation with its own trigger, target, scope, state transition, and characteristic failure modes that downstream QA cannot diagnose.
Methodology Each instance is a tuple of a topic-specific user background, a set of evidence conversations, a gold operation trace, and evaluation probes. The trace is the evaluation anchor: each operation carries a type, target object, old and new value, and evidence spans quoted verbatim from user turns. Five operation types are defined, including TrajectoryOps that compose remember, update, forget, and reflect events across time so the benchmark can check intermediate states and their temporal order. A four-stage generation pipeline (background construction; evidence conversation and gold-trace generation; operation-level probe generation; long-context dialogue generation with distractor pools) produces natural conversations with explicit operation supervision, verified by local schema and span gates plus an LLM verifier. Six probe categories (operation trace, target binding, state transition, candidate disambiguation, operation application, state trajectory) score intermediate memory behavior, and representative systems from four paradigms are evaluated under adjacent-evidence and long-context settings.
Results Performance is strongest when evidence sits adjacent to the query and degrades consistently once it is dispersed into long, distractor-laden histories, for both answer accuracy and operation-level reliability. Session-level retrieval substantially outperforms turn-level retrieval, and managed-memory services that preserve longer, context-rich memory units outperform those storing short, isolated facts, indicating that surrounding context is critical for correctly executing lifecycle operations rather than merely retrieving relevant content. Parametric memory, which folds interaction history into model parameters, remains markedly unreliable across almost all diagnostic dimensions. Reconstructing an ordered memory-state trajectory across multiple composed operations is far more fragile than any single-step operation, and this weakness persists even for otherwise strong long-context models, exposing a failure mode that final-answer accuracy alone would not surface.
- RECON: Benchmarking Agent Memory for Compositional Reasoning over Long Contexts
Synthesis
Plain-language abstract RECON (Reasoning over Extended Contexts with Obfuscated Narratives) is a benchmark that tests whether an agent's memory can maintain a coherent, evolving understanding over long contexts where facts do not just accumulate but interact, contradict, and cascade. It spans 24 investigative case files across criminal, medical, and financial domains, each 50k to 100k tokens, with 1,604 questions over six memory-intensive tasks, and reports that even the strongest non-Oracle system reaches only 22.4% accuracy.
Motivation Existing memory benchmarks model memory as a state machine: they check whether an agent can retrieve a scattered fact or detect that a fact changed. Real workflows demand more. When a lab result is revised on Day 9, a witness statement is contradicted on Day 5, or a flagged transaction is reversed, an agent must trace which downstream conclusions are affected, which survive on independent support, and how an alternative timeline would have unfolded. RECON targets what happens after a change, not just whether the current value is tracked.
Methodology A deterministic pipeline constructs each case from a provenance DAG, then a question generator traverses the DAG to synthesize questions per task category, with a fixed question matrix enforcing per-task and per-format quotas so the distribution does not drift between runs. The six tasks are chain reconstruction (order 5-15 evidence hops), cascade propagation (which conclusions break versus survive after an invalidation), source-conflict resolution, counterfactual reasoning, temporal-constraint satisfaction, and temporal fact retrieval as a control. Solvers - long-context, RAG, hybrid RAG, Supermemory, Mem0, Mem0-Graph, Hindsight, closed-book, and an Oracle handed the full structured ground truth - share one answering template; freeform answers are graded by two independent LLM judges from different model families and averaged, while other formats are scored deterministically with an explicit abstain option (+1 correct, -0.2 wrong, 0 abstain).
Results Even the Oracle given the ground-truth dependency graph reaches only 54.6% accuracy, and the best non-Oracle system 22.4%; RAG attains 20.6% on full-coverage retrieval hits. Decomposing failures shows roughly four in five persist even when retrieval succeeds, placing the bottleneck in reasoning rather than evidence selection. Human annotators reach 63.0% accuracy, exceeding the Oracle solver by 8.4 points and confirming reasoning, not retrieval, as the residual challenge across long-context, retrieval, and agentic-memory architectures.
- Can Agent Memory Systems Track Evolving State?
Synthesis
Plain-language abstract A benchmark and method for a memory capability separate from recall: keeping track of which version of a fact is currently in force after it has been revised across sessions. The benchmark, StateMemBench, generates each scenario as a symbolic program of state operations so the correct answer is computed by replay and the specific way a lazy reader would get it wrong is known in advance. The method, StateMem, parses each turn into structured state units with typed dependency links, then handles supersession and staleness deterministically rather than with an LLM.
Motivation Existing memory systems and benchmarks optimize recall of relevant facts, but as agents run longer, facts, constraints and decisions get revised, and an answer must reflect the current state rather than a superseded one. The authors call the failure state drift: the relevant fact is present in the assembled context, but the agent acts on a stale or incomplete version of it. This is distinct from dialogue state tracking, which prescribes a slot-value representation and evaluates it directly over cooperative dialogues that accumulate a goal monotonically; here state is whatever a system must maintain to answer correctly, evaluation is purely behavioral, and revisions are adversarial across sessions. Some concurrent work centers state, but the authors argue none cleanly isolates state tracking from the other errors it co-occurs with.
Methodology The authors first define and label drift on existing benchmarks, assigning a failure to drift only after excluding retrieval, comprehension, schema and reasoning readings, dropping unassignable points, and cross-checking with two judge passes, a cross-family judge and two human annotators. They then build StateMemBench: each scenario is a symbolic event program of typed operations over ground, derived and declared state; the gold answer comes from deterministic replay; a family of executable lazy reader policies is run against the replay, and a scenario is admitted as a trap when policies disagree, with the disagreeing set forming its failure-mode signature (status, salience, sequence, compound, plus anti-trap controls). Programs are grounded in public data for surface vocabulary and rendered into multi-session dialogue by a strong LLM, then programmatically verified for fact placement and phrase leakage. Probes are closed-pool: an unseen pool of three to four options holds the gold answer, the targeted policy's drift answer and neutral distractors. StateMem itself runs a per-turn TurnEncoder producing state units (id, content, priority, source, deps), a deterministic update stage applying supersessions and marking dependents needs_recheck by dependency-graph traversal, and a single answer-time call over the assembled active state. A wrapper variant applies the same trace-then-resolve structure as a prompt-level transformation of any backend's answer call, evaluated against a length- and cost-matched generic-extraction control.
Results Drift leads the confirmed failure distribution on several existing benchmarks (63.5% on MemoryArena-shopping, 44.4% on LongMemEval oracle where retrieval is perfect by construction, 10 of 16 on tau-squared-bench-Z) but is not universal, falling to 19.0% on MemoryArena-travel. On StateMemBench, long-context is not the strong baseline it is on recall tasks: the best long-context model reaches 0.277 and same-backbone long-context 0.149. StateMem reaches 0.363 on DeepSeek-V4-Flash, 1.8x the best memory system and 2.4x same-backbone long-context, and 0.233 on Qwen-3.5-9B, 1.6x the best memory system, both significant by paired McNemar at p < 0.001; GraphRAG at 0.224 is statistically level on Qwen. Ablations put supersession marking as the largest single component and show dependency propagation over-fires on Set B anti-traps by 12.5 points, so removing it leaves DeepSeek slightly better. Drift-rate analysis shows the memory layer barely changes outcomes on a weak answerer, where every arm drifts at 61 to 66%, and separates on the stronger backbone, where StateMem's drift rate falls 15 points and correct answers rise by 42 while long-context, Mem0 and BM25 move by 1 to 3 points. The wrapper improves every one of six backends on both benchmarks, adding 31.7 to 66.6 points on StateMemBench with 15.0 to 31.7 attributable to state structure over the matched control, significant in all twelve cells. State tracking does not cost recall: StateMem also leads memory systems on LongMemEval (0.656 on DeepSeek) and LoCoMo (0.592), with margins concentrated on temporal-reasoning and knowledge-update question types. The authors note StateMem mirrors the policy family behind the traps, so its StateMemBench margins should be read as an upper bound.
- Remember, Verify, or Ask? Cross-Family Evaluation of Memory Commitment in LLM Agents
Synthesis
Plain-language abstract A benchmark for the decision an agent makes before it writes to memory: should this piece of interaction-derived information be persisted durably, used only in the current context, re-checked against the world, or clarified with the user. It evaluates three models from two families under three prompt conditions, and separately tests whether the stated decision predicts which memory tool the model actually calls.
Motivation Persistent memory personalizes an agent, but an incorrect durable update silently distorts future behavior. A temporary request should not become a standing preference, a service status can go stale, one tool failure may be noise, and an underspecified correction may need a question before it is generalized. The authors argue the critical capability is not recall but commitment, and that two sources of uncertainty are usually collapsed: verification queries the world, which is authoritative for changing facts, while clarification queries the user, who is authoritative for intent and scope. Prior work covers adjacent targets (binary session-level storage gating, ADD/UPDATE/DELETE/NOOP operations, whether retrieved memory grounds tool parameters, general ambiguity clarification) without jointly distinguishing durable storage, local use, world verification and user clarification at commitment time.
Methodology Each item supplies an acquire context, a candidate update and a later reuse context, with a gold action assigned by released rules and a tie between persist and a weaker action resolved toward the weaker commitment. 140 primary scenarios are split 70/70 by sorted identifier within category, covering stable and episodic preferences, freshness-sensitive facts, one-off corrections, policy constraints, ambiguous updates and noisy failures at 20 items each, with eight lexical traps where a surface cue points to the wrong action. Two non-authors labeled the held-out and contrast items blind to author labels and to each other, with a blind third resolving ties. Claude Haiku 4.5, Claude Sonnet 4.6 and a locally served Qwen3.5-9B (Q4_K_M via Ollama, temperature 0, seed 13, thinking disabled) were each run under three conditions: a bare prompt defining the actions, a policy prompt adding five commitment rules including the tie-breaker, and a four-shot prompt with one development example per action. A separate track, MCB-Act, removes the label vocabulary and requires one structured tool call, scored by mapping the selected tool to an action. Analysis uses accuracy with bootstrap intervals, macro-F1, over-memory, under-memory and per-class recalls, with exact paired McNemar tests and Holm correction within each family of comparisons.
Results Both model families under-ask. Claude label-mode verification recall runs 0.889 to 1.000 while clarification recall runs 0.500 to 0.750; bare Qwen verifies 12 of 18 freshness items and asks on 0 of 12 clarification items. Few-shot prompting lifts Qwen accuracy from 0.557 to 0.771 (paired delta +0.214, p_H = 0.002) and clarification recall from 0 to 0.333, still missing 8 of 12. The policy prompt raises Qwen accuracy by only 0.071 (p_H = 0.539) but cuts erroneous persistence from 0.243 to 0.100 (p_H = 0.038), moving the uncertainty to verification (recall 0.667 to 0.944) rather than to the user (clarification 0 to 0.083). Haiku's policy and few-shot gains survive correction (p_H = 0.002 and 0.047); Sonnet's do not, so the benchmark measures a prompt-conditioned commitment policy rather than a fixed model trait. Label-to-tool agreement is 0.571 for each Claude model and 0.229 for Qwen; Sonnet accuracy falls from 0.814 to 0.529 (p_H < 0.001) and Qwen from 0.557 to 0.343 (p_H = 0.047), with Qwen calling use_now on 54 of 70 items and verification recall collapsing to 0.056. All emitted arguments pass the deterministic well-formedness rules, locating the bottleneck in tool choice. On the combined 140 Qwen items of the contrast extension, bare, policy and few-shot accuracy is 0.614, 0.757 and 0.843, with clarification remaining the weakest class throughout; the authors retain the extension as a controlled sensitivity check rather than a claim of naturalistic external validity, since its rule-authored templates align closely with the explicit policy rules. MCB-Act scores tool-call selection and does not execute downstream effects.
Eval Methodology
Evaluation methodology and metrics for agentic memory systems: retrieval-aware vs answer-level scoring, white-box diagnostics, failure attribution, LLM-as-judge reliability, scoring-target sensitivity, statistical rigor, and reproducibility
Key threads
- Stage-decomposed / white-box diagnostics: a clear shift from answer-only scoring toward attributing memory failures to write, retrieve, evidence-construction, or generation stages (MemTrace, AuthTrace), enabling failure-attribution rather than a single pass/fail.
- Beyond factual recall as the scoring target: benchmarks increasingly distinguish shallow recall from strategic/procedural memory use and from temporal update-tracking (StratMem-Bench, Continuous Lifelog), making the choice of scoring target a first-class methodological variable.
- LLM-as-judge reliability and calibration for memory QA: judges carry position/verbosity/self-preference biases and fine-tuned judges fail to transfer, so memory-eval pipelines must validate judge-human agreement before trusting judge-based correctness (Gu, Li, Huang).
- Reproducibility and ecological validity: benchmark contamination/leakage, content drift, and the realism-reproducibility-scalability trilemma threaten the validity of memory-system comparisons and push toward leak-controlled synthetic trajectories (NumLeak, WebForge, AlphaEval).
- Richer-than-binary correctness metrics: graded support relations and groundedness taxonomies replace binary hallucination flags, changing how grounded memory answers are scored (Sarkar).
- Metric saturation on incumbent benchmarks: high reported LoCoMo numbers indicate single-benchmark accuracy is approaching ceiling, motivating harder, adversarial, and multi-axis memory evaluation (Synthius-Mem).
Open gaps
- No standardized failure-attribution taxonomy or shared harness: MemTrace and AuthTrace each invent their own stage decomposition, with no common schema or open tooling to make per-stage memory diagnostics comparable across systems.
- Judge reliability is studied generically but almost never validated specifically for memory QA (temporal grounding, multi-session attribution, contradiction handling); calibration of LLM judges against human labels on memory-specific question types is largely unmeasured.
- Scant statistical rigor: memory-system comparisons report point accuracies (e.g. single LoCoMo numbers) without confidence intervals, seed/variance reporting, or significance testing across systems, so ranking stability is unknown.
- Contamination control for memory benchmarks is unaddressed: NumLeak-style leakage is documented for numeric benchmarks but no memory benchmark reports leak-controlled construction, conflating memorized recall with genuine retrieval-and-use.
- Evaluation conflates retrieval quality with answer quality: few harnesses jointly report retrieval-aware metrics (did the right memory get retrieved) and answer-level metrics, leaving the retrieve-vs-reason attribution to ad hoc analysis.
- SkillEvolBench: Benchmarking the Evolution from Episodic Experience to Procedural Skills
Synthesis
Plain-language abstract SkillEvolBench is a benchmark designed to test whether AI agents can turn their own task experience into reusable procedural skills — not just replay what they did once, but extract general instructions a future agent can follow on related tasks. It contains 180 tasks across six real-world work domains and evaluates ten large language model configurations under three agent frameworks, comparing skill-based conditions against baselines that use no skills or raw trajectory replay.
Motivation LLM agents accumulate detailed records of how they solved past tasks, but it is unclear whether that experience can be distilled into compact, reusable procedures rather than task-specific patches. Prior work either studied skill use (given curated skills) or experience reuse (replaying trajectories), leaving a gap: can agents themselves convert noisy one-off episodes into external skill artifacts that help on harder, related tasks they have not yet seen?
Methodology The benchmark organizes 180 tasks into six environments covering code modification, API orchestration, data processing, document transformation, research synthesis, and communication operations, with five task families per environment. Each family follows a six-role arc: three acquisition tasks (canonical, enriched, variant) used to build the skill library, and three frozen deployment tasks (context-shift, adversarial, composition) where no further skill updates are allowed. Agents operate in Self-Generated or Curated-Start settings; a separate Skill Author step uses compacted trajectories and structured verifier feedback to decide whether to write a new skill, revise an existing one, or leave the library unchanged. Controls include a No-Skill condition and a Raw-Trajectory condition that provides the original episode directly.
Results Across ten model configurations and three agent harnesses, current agents adapt locally but rarely form robust reusable skills. Raw-trajectory reuse frequently outperforms distilled skills, indicating that current abstraction procedures discard contextual and procedural cues that remain useful for future tasks. The always-update curated variant showed the strongest average gain (+0.78 percentage points in frozen evaluation success rate), but benefits were model-specific: GPT-5.4 improved by +6.7 percentage points and Opus 4.5 by +4.4 percentage points, while Gemini 2.5 Pro was harmed by most variants (average -3.70 percentage points). Adding more skills or larger resource libraries did not reliably help and often introduced episode-specific drift and procedural clutter without improving deployment success.
- Synthius-Mem: Brain-Inspired Hallucination-Resistant Persona Memory Achieving 94.4% Memory Accuracy and 99.6% Adversarial Robustness on LoCoMo
Synthesis
Plain-language abstract Synthius-Mem is a memory system for AI agents that stores what is known about a person rather than replaying raw conversation history. Drawing on how the human brain organizes memory into specialized subsystems, it decomposes conversations into six typed domains — biography, experiences, preferences, social circle, work, and psychometrics — and retrieves structured facts at query time. On the LoCoMo benchmark it achieves 94.37% overall accuracy and 99.55% adversarial robustness while consuming roughly five times fewer tokens than full-context replay.
Motivation Current LLM memory approaches — sliding windows, summarization, embedding-based retrieval, and flat fact extraction — each reduce token cost but introduce information loss, semantic drift, or uncontrolled hallucination about the user. No published system on the LoCoMo benchmark reported adversarial robustness, meaning the ability to refuse questions about facts the user never disclosed. The paper addresses this gap by arguing that domain-agnostic storage discards the structural advantages that neuroscience shows different memory types require.
Methodology Synthius-Mem uses a multi-stage pipeline: conversations are parsed and chunked, then six parallel domain-specific extractors pull typed facts into separate stores for biography, experiences, preferences, social circle, work, and psychometrics (the last using nine validated psychological frameworks). Each domain undergoes its own consolidation and deduplication pass. At inference time, a planner LLM selects relevant domains and a CategoryRAG component retrieves structured facts with a reported mean latency of 21.79 ms. The system was evaluated on the LoCoMo benchmark (ACL 2024), which contains 10 multi-session conversations and 1,813 questions spanning single-hop recall, multi-hop reasoning, temporal reasoning, open-domain knowledge, and adversarial false-premise questions.
Results Synthius-Mem achieves 94.37% accuracy on LoCoMo, exceeding the prior best published system MemMachine (91.69%) and human performance (87.9 F1). Core memory fact accuracy reaches 98.64%. Adversarial robustness — refusal to hallucinate facts the user never disclosed — reaches 99.55%, a metric no competing system reports. Token consumption is approximately five times lower than full-context replay at 500 messages, where full-context replay itself achieves only 85.46% in the authors' controlled evaluation.
- Evaluating Memory Capability in Continuous Lifelog Scenario
Synthesis
Plain-language abstract This paper introduces LifeDialBench, a new benchmark for testing how well AI memory systems can handle continuous spoken conversations recorded by wearable devices like smart glasses. Unlike existing benchmarks that focus on chatting directly with an AI, this one evaluates memory over the kind of multi-person, everyday dialogues that an always-on microphone would capture. The paper also proposes a new evaluation protocol that respects the time-ordering of events, mimicking how such a system would work in practice.
Motivation Current AI memory benchmarks focus on one-on-one person-AI chat sessions and do not address the emerging use case of wearable devices that continuously record ambient conversations throughout the day. Existing approaches to extending memory — such as feeding ever-longer text into a model — become prohibitively expensive and still underperform. There was no public benchmark designed for the continuous, multi-person, time-stamped dialogue streams that wearable lifelogging devices produce.
Methodology The authors built LifeDialBench from two complementary data sources: EgoMem, derived from real-world egocentric video recordings (transcribed via automatic speech recognition), and LifeMem, constructed through a hierarchical life-simulation framework using a virtual community with human-in-the-loop review. Question-answer pairs cover four types — single-event, event detail, multi-event, and temporal information queries — spanning timescales from 30-second clips to week-level summaries. Crucially, the paper introduces an Online Evaluation protocol that enforces temporal causality, evaluating memory systems incrementally as data is stored rather than all at once after the fact.
Results Experiments reveal a counterintuitive finding: sophisticated memory systems with complex architectures fail to outperform a simple retrieval-augmented generation (RAG) baseline. The results show that over-designed structures and lossy compression hurt performance, and that preserving raw conversational text with high fidelity is more important than elaborate memory abstractions. Temporal retrieval is identified as a universal bottleneck across all systems tested.
- Evaluating LLM-based Agents for Multi-Turn Conversations: A Survey
Synthesis
Plain-language abstract This paper surveys how researchers evaluate AI chatbots and assistants built on large language models when those systems must hold multi-turn conversations — exchanges that unfold over many back-and-forth messages rather than a single prompt. The authors reviewed nearly 250 published studies to map out what is being evaluated and how, producing two classification frameworks that together cover the full range of current evaluation practice.
Motivation AI conversational agents powered by large language models are increasingly deployed in customer service, personal assistants, and other settings that require sustained, context-aware dialogue. Despite this growth, the field lacked a systematic overview of how such multi-turn systems are evaluated — what dimensions matter and what measurement methods are available — leaving practitioners without a consolidated reference.
Methodology Using a PRISMA-inspired systematic review process, the authors examined nearly 250 scholarly sources from a range of publication venues. From this corpus they constructed two interrelated taxonomy systems: one defining what to evaluate (task completion, response quality, user experience, memory and context retention, planning and tool integration) and one categorizing how to evaluate (annotation-based evaluations, automated metrics such as BLEU and ROUGE, hybrid human-plus-quantitative strategies, and self-judging methods that use LLMs as evaluators).
Results The survey produced a structured, dual-taxonomy framework covering both evaluation dimensions and evaluation methodologies for LLM-based multi-turn conversational agents. The framework captures traditional language-understanding metrics alongside newer techniques suited to the dynamic, interactive nature of multi-turn dialogue, offering a consolidated foundation for researchers and practitioners assessing conversational AI systems.
- MemTrace: Tracing and Attributing Errors in Large Language Model Memory Systems
Synthesis
Plain-language abstract MemTrace is a framework for automatically finding and explaining errors in the memory systems used by AI language model agents. When a memory-augmented agent gives a wrong answer, MemTrace traces the sequence of memory operations — storing, updating, retrieving, deleting — to pinpoint exactly which step introduced the failure and why. The authors also release MemTraceBench, a benchmark of 160 annotated real failure cases, and show that fixing identified errors can improve end-task accuracy by up to 7.62%.
Motivation Language model agents increasingly rely on persistent memory to handle long conversations and multi-session tasks, but when these systems fail it is very hard to tell where things went wrong. Unlike simpler stateless agents where errors are usually local to one step, memory failures can originate in an early storage or update operation and only become visible much later during retrieval or answer generation. Existing memory benchmarks only measure whether a system succeeds or fails overall; they do not recover the causal chain that led to the failure, leaving a traceability gap that makes debugging slow and unreliable.
Methodology The authors instrument the source code of a memory system to record every memory update, memory read, and answer-generation step as it runs. These records are assembled into an execution graph — a directed acyclic bipartite graph whose nodes are variables (raw messages, retrieved memory units, summaries, prompts) and operations (LLM inference, retrieval, filtering, parsing), connected by directed edges that capture information flow. Given a failed case, the MemTrace attribution method retrieves relevant source messages and then iteratively traces operation subgraphs to locate the earliest minimal set of faulty operations whose correction would have prevented the failure. MemTraceBench was constructed from four representative memory systems (LongContext, RAG, Mem0, EverMemOS) and three public datasets (LoCoMo, LongMemEval, RealMem), yielding 160 human-annotated failure cases each with QA pairs, execution logs, ground-truth error labels, faulty operations, and human explanations.
Results Experiments on MemTraceBench show that diagnosing memory failures remains challenging, but MemTrace successfully recovers meaningful faulty operations and error types and generates coherent explanations suitable for debugging. The analysis reveals that memory failures are systematic, most commonly arising from operation-level issues such as information loss and retrieval misalignment. Using the fine-grained attribution signals from MemTrace to guide automatic prompt optimization produces a closed-loop correction system that improves end-task performance by up to 7.62%.
- StratMem-Bench: Evaluating Strategic Memory Use in Virtual Character Conversation Beyond Factual Recall
Synthesis
Plain-language abstract This paper introduces StratMem-Bench, a benchmark for testing how well AI-powered virtual characters use memory strategically in conversation. Rather than just checking whether a chatbot recalls facts, the benchmark asks whether it knows which memories to use, which to optionally enrich a response with, and which to ignore entirely — mirroring how humans selectively deploy information in dialogue.
Motivation Existing benchmarks for memory-augmented AI treat memory as a static fact store and evaluate only whether relevant facts are recalled — a property called factual recall. This is insufficient for human-like virtual characters, where good responses also require selectively incorporating supportive personal context and actively suppressing irrelevant information. No prior benchmark captured this distinction.
Methodology The authors built a dataset of 657 conversation instances in which a virtual character must respond given a heterogeneous memory pool partitioned into three types: required memories (must), supportive memories (nice), and irrelevant memories (irr). They evaluated state-of-the-art LLMs as virtual characters in zero-shot mode using four metrics: Strict Memory Compliance (SMC, a pass/fail rule-based check), Memory Integration Quality (MIQ, an LLM-judged 1–5 Likert quality score designed to be failure-sensitive), Proactive Enrichment Score (PES, measuring tendency to incorporate nice memories), and Conditional Irrelevance Rate (CIR, measuring how often irrelevant memories intrude).
Results All evaluated models perform well at separating required from irrelevant memories, but none achieves above 50% SMC once supportive memories are introduced into the pool. Integration quality scores drop noticeably when nice memories are used (MIQ around 3.9–4.4 versus 4.2–4.6 for must memories) and collapse severely when irrelevant memories are incorporated (MIQ 2.4–3.1). A clear proactivity–risk aversion trade-off emerges: Gemini 3 Pro reaches the highest enrichment rate (~73% PES) but also the highest irrelevance contamination rate (~47% CIR in nice-only scenarios), while GPT-5-chat stays conservative (~8% CIR) at the cost of rarely enriching responses.
- AuthTrace: Diagnosing Evidence Construction in Thematically Dense Single-Author Corpora
Synthesis
Plain-language abstract AuthTrace is a benchmark for testing how well AI systems gather and organize evidence when answering questions about a single author's body of work. It uses 860 public-domain essays by five modern Chinese prose writers to create 2,099 question-answer instances, each tagged with exactly how many source documents are needed to support the answer. The benchmark lets researchers compare four different evidence-organization strategies — retrieval, memory compression, graph traversal, and thematic indexing — on the same dataset using the same metrics.
Motivation AI evidence-construction systems (retrieval, memory, graph, and structured indexing) are benchmarked in isolation, each with its own corpus and metrics, so when a system fails there is no principled way to tell whether the problem is missing evidence, noisy evidence, or poor answer synthesis. Single-author corpora are a particularly hard test case because distractors share the same style, vocabulary, and recurring themes as the correct evidence, making it difficult to distinguish direct support from mere thematic adjacency.
Methodology The benchmark is built from public-domain nonfiction prose by Lu Xun, Zhou Zuoren, Zhu Ziqing, Xiao Hong, and Yu Dafu — 860 articles totaling roughly 2 million Chinese characters — processed through a staged LLM-assisted annotation pipeline. Each instance provides a query, quoted gold evidence spans linked to source documents, atomic gold claim units, a reference answer, and an exact fan-in label (the count of distinct source documents required). Instances are grouped into Single-doc (fan-in = 1), Low multi-doc (fan-in = 2), and High multi-doc (fan-in >= 3). All systems are evaluated with a unified pack-level protocol measuring Evidence Recall, Evidence Precision, and Answer Correctness scored by an LLM judge.
Results Evidence recall was the strongest observed predictor of answer correctness across eight systems and two QA models, with a correlation of r = 0.96; most failures stem from missing evidence rather than flawed answer synthesis. Flat retrieval degrades 2–3 times faster than thematically organized evidence construction as fan-in increases. Graph retrieval performs best at single-document grounding (fan-in = 1) while thematic indexing leads on multi-document synthesis (fan-in >= 2), with a crossover at fan-in 2, providing a practical selection heuristic for practitioners.
- From Binary Groundedness to Support Relations: Towards a Reader-Centred Taxonomy for Comprehension of AI Output
Synthesis
Plain-language abstract When an AI system answers a question by drawing on a document, current tools simply label the answer as either 'supported' or 'unsupported.' This paper argues that label is too coarse: a verbatim quote, a paraphrase, a deduction, and an assumption-laden inference are all technically 'supported' but require very different levels of reader scrutiny. The authors propose building a richer taxonomy of support relations that would let interfaces show not just whether a claim is grounded, but exactly how it connects to the source.
Motivation Binary groundedness labels obscure the wide variety of ways a language model can transform source text into an answer — from direct quotation to paraphrase to inductive inference — and may lull readers into passive acceptance rather than critical engagement. Survey evidence already shows that higher confidence in AI is associated with less critical thinking. Without finer-grained provenance information, users cannot easily judge which claims deserve scrutiny and which can be trusted as verbatim.
Methodology This is a position and research-agenda paper rather than an empirical study. The authors demonstrate the insufficiency of binary labels through worked examples tested on four commercial systems, then sketch a construction path for a reader-centred taxonomy: a structured literature review drawing on Toulmin's argumentation model, Gricean pragmatics, and scholarly discourse ontologies (e.g., ScholOnto) to produce candidate support relations; iterative refinement guided by discriminability (can annotators reliably distinguish categories?) and actionability (do distinctions matter for provenance interfaces?); and validation via a human annotation study on statement-source pairs enriched from existing hallucination benchmarks, with interannotator agreement measuring construct validity.
Results The paper does not report experimental measurements; it is a proposal. Its key contribution is a framework articulating a taxonomy of support relations — including direct quotation, paraphrase, deductive support, inductive support, and support contingent on ancillary assumptions — and an evaluation roadmap involving human annotation benchmarks and LLM-as-judge protocols. The authors argue this taxonomy would enable interfaces that communicate the type of grounding behind each AI-generated claim, supporting more informed critical reading.
- An Empirical Study of LLM-as-a-Judge for LLM Evaluation: Fine-tuned Judge Model is not a General Substitute for GPT-4
Synthesis
Plain-language abstract This paper examines whether open-source language models fine-tuned specifically to act as evaluators can replace GPT-4 when judging the quality of other AI language model outputs. The authors run a systematic series of experiments comparing several fine-tuned judge models against GPT-4 across multiple benchmarks, then propose a hybrid method that mixes the two approaches to cut costs while preserving accuracy.
Motivation Evaluating large language models is expensive and raises privacy concerns when it depends on proprietary APIs such as GPT-4. Researchers had proposed fine-tuning smaller open-source models as local substitutes, and those models reported accuracy matching GPT-4 on their own test sets — but those benchmarks closely resembled the training data. No systematic study had tested whether fine-tuned judge models actually generalize beyond their training distribution.
Methodology The authors benchmarked four representative fine-tuned judge models — JudgeLM, PandaLM, Auto-J, and Prometheus — across dimensions including generalizability to out-of-domain data, fairness (bias toward superficial response features), ability to evaluate specific quality aspects, and responsiveness to prompt engineering. They then analyzed the softmax probability distributions of the fine-tuned judges to build a confidence indicator, and used it to design CascadedEval: a hybrid pipeline that routes low-confidence samples to GPT-4 for re-evaluation while handling high-confidence samples locally.
Results Fine-tuned judge models surpassed GPT-4 on their respective in-domain test sets but fell short on every other dimension tested: generalizability, fairness, aspect-specific evaluation, and prompt-engineering responsiveness. The analysis showed these models behave as task-specific classifiers overfitted to their training data rather than as general evaluators. CascadedEval achieved accuracy on par with GPT-4 on both in-domain and out-of-domain test sets while using only 50% of the GPT-4 API calls, cutting the cost by half.
- A Survey on LLM-as-a-Judge
Synthesis
Plain-language abstract This paper is a comprehensive survey of systems where large language models (LLMs) are used as automated evaluators — a setup called LLM-as-a-Judge. It catalogs existing approaches, proposes a formal definition and taxonomy, identifies key reliability challenges, and introduces a benchmark for measuring how trustworthy these judge systems are. The survey covers strategies for making LLM judges more consistent and less biased, as well as practical applications across domains from NLP to law and science.
Motivation Evaluating AI-generated outputs at scale is difficult: expert human review is costly and inconsistent, while automated metrics like BLEU and ROUGE miss nuance and fail on open-ended tasks such as story generation. LLM-as-a-Judge emerged as a way to combine the scalability of automatic metrics with the contextual reasoning of human experts, but the field lacked formal definitions, systematic reviews, and agreed methods for assessing whether these judge systems are actually reliable.
Methodology The authors conduct a systematic literature review of the LLM-as-a-Judge paradigm, organizing existing work into a formal taxonomy that spans in-context learning approaches, model selection, post-processing strategies, and evaluation pipelines. They analyze strategies for improving judge reliability — including prompt engineering, fine-tuning, and bias mitigation — and examine metrics and datasets used to assess judge quality. They also design a novel benchmark specifically for evaluating the reliability of LLM-as-a-Judge systems, and survey practical deployments across machine learning, finance, law, and scientific domains.
Results The survey finds that LLMs such as GPT-4 can evaluate text generation tasks at a level comparable to humans, and that LLM-as-a-Judge has been successfully applied across NLP tasks including summarization, dialogue, and reasoning. The paper identifies persistent challenges — position bias, inconsistency, and adversarial vulnerability — and maps out mitigation strategies. It also documents the growing use of LLM judges in reinforcement learning from human feedback pipelines and in guiding reasoning path selection in multi-agent systems. The accompanying benchmark and taxonomy are offered as a reference infrastructure for the field.
- LLMs-as-Judges: A Comprehensive Survey on LLM-based Evaluation Methods
Synthesis
Plain-language abstract This paper is a comprehensive survey of using large language models (LLMs) as automatic evaluators — a practice called "LLMs-as-judges." Instead of relying on human annotators or simple metrics to assess AI-generated text, researchers are increasingly asking LLMs themselves to rate or compare outputs. The survey maps out the entire landscape of this approach: why it is used, how evaluation systems are built with it, where it is applied, how to assess its quality, and what its known failure modes are.
Motivation Traditional evaluation metrics like BLEU and ROUGE often fail to capture important qualities of generated text such as fluency, logical coherence, and creativity. Human annotation is accurate but slow and expensive to scale. This created a gap: a need for evaluation methods that are flexible, interpretable, generalizable across tasks, and cheap enough to run at scale — a gap the LLMs-as-judges paradigm aims to fill.
Methodology The authors conduct a structured literature survey organized around five key perspectives: Functionality (why use LLM judges), Methodology (how to build evaluation systems using LLMs, including single-LLM approaches with prompt engineering and fine-tuning, multi-LLM systems, and human-AI collaboration), Application (domains where LLM judges are deployed), Meta-evaluation (methods for assessing judge quality), and Limitations (known biases and failure modes). The survey also covers how LLM judges are used in data annotation and synthesis workflows.
Results The survey identifies and taxonomizes a wide range of biases that afflict LLM judges, including position bias, verbosity bias, self-enhancement bias, sentiment bias, token bias, overconfidence bias, and diversity bias tied to demographic identity markers. It finds that prompt template choice alone can lead to inconsistent or biased assessments, and that LLMs can inherit implicit biases from pretraining data. The paper maps future research directions and maintains an open-source resource list cataloguing work in this rapidly growing area.
- Survey on Evaluation of LLM-based Agents
Synthesis
Plain-language abstract This paper is a comprehensive survey of how LLM-based agents — AI systems that go beyond single-step text generation by planning, using tools, and maintaining memory across multiple steps — are evaluated. It catalogs the benchmarks, environments, and frameworks used to assess these agents across a wide range of tasks and domains.
Motivation Standard language model benchmarks were designed for single-turn, text-to-text tasks, but LLM-based agents operate in multi-step, dynamic environments where they plan, call external tools, and adapt to feedback. No comprehensive mapping of evaluation methodologies existed for this broader class of systems, leaving researchers and practitioners without a clear guide to what benchmarks exist, what they measure, and where the gaps are.
Methodology The authors systematically analyze the evaluation landscape across four dimensions: (1) fundamental agent capabilities such as planning, multi-step reasoning, tool use, self-reflection, and memory; (2) application-specific benchmarks for web agents, software engineering agents, scientific agents, and conversational agents; (3) benchmarks for generalist agents and leaderboards; and (4) agent evaluation frameworks used throughout the development cycle, including tools such as LangSmith, Langfuse, and BrowserGym.
Results The survey identifies an emerging trend toward more realistic and continuously updated benchmarks that pose harder challenges. It also surfaces critical gaps in the field: existing evaluations largely neglect cost-efficiency, safety, robustness, and fine-grained or scalable assessment methods. The authors propose these as priority directions for future research in agent evaluation.
- AlphaEval: Evaluating Agents in Production
Synthesis
Plain-language abstract AlphaEval is a benchmark designed to test AI agent products under conditions that actually resemble real business use, rather than the idealized settings of typical research benchmarks. It contains 94 tasks drawn directly from seven companies that deploy AI agents in their core operations, covering six occupational domains. The paper also introduces a systematic process for turning genuine business requirements into reproducible evaluation tasks, and uses the benchmark to compare six frontier language models deployed through four commercial agent products.
Motivation Existing agent benchmarks like SWE-bench and WebArena are built from retrospectively curated tasks with clear requirements and deterministic metrics — conditions that do not match how agents are actually used in production. A survey of 27 AI product companies found that 63% have low confidence that model updates genuinely improve their products, 25.9% have no explicit evaluation criteria, and 70.4% rely on developers testing as a side activity. This gap between research benchmarks and production reality was the central problem the paper set out to address.
Methodology The authors partnered with seven companies and AI-focused organizations to collect 94 authentic production tasks spanning six O*NET occupational domains. Tasks were formalized through a four-stage pipeline: partner engagement, requirement elicitation, task formalization, and iterative validation. The evaluation framework combines multiple paradigms — LLM-as-a-Judge, reference-driven metrics, formal verification, rubric-based assessment, and automated UI testing — with individual domains composing several paradigms simultaneously. Six frontier models (including Claude Opus 4.6, GPT-5.2, and Gemini 3 Pro Preview) were evaluated across four commercial agent scaffolds (Claude Code, Codex, GitHub Copilot, and Cursor), yielding 14 model-scaffold configurations.
Results The best-performing configuration (Claude Code with Opus 4.6) achieved only 64.41 out of 100, indicating a substantial gap between frontier agent capability and production requirements. Scaffold choice proved as consequential as model choice: the same Opus 4.6 model scored 64.41 via Claude Code but only 53.45 via Codex, an 11-point difference. Domain performance varied widely, from 62.0 on Technology Research tasks to 30.0 on Human Resources tasks, showing that no single aggregate score captures production readiness. The paper also identifies six recurring production-specific failure modes through systematic error analysis.
- WebForge: Breaking the Realism-Reproducibility-Scalability Trilemma in Browser Agent Benchmark
Synthesis
Plain-language abstract WebForge is a fully automated system for building benchmarks that test AI agents that control web browsers. It generates complete, interactive fake websites from scratch — no human annotation required — and includes realistic web nuisances like pop-ups and cookie dialogs. Using this system, the authors built WebForge-Bench, a set of 934 tasks across 7 domains and 3 difficulty levels, and used it to evaluate multiple AI models.
Motivation Existing browser-agent benchmarks are caught in a trilemma: real-website benchmarks are realistic but become outdated as web content changes (nearly half of one benchmark's tasks expired within two years), while controlled sandbox environments are reproducible but unrealistically clean and require expensive manual curation. No prior benchmark simultaneously achieved realism, reproducibility, and scalability, and none offered fine-grained, multi-dimensional control over task difficulty.
Methodology WebForge uses a four-agent pipeline — Plan, Generate, Refine, and Validate — to produce self-contained static websites end-to-end. The Plan Agent designs tasks using a seven-dimensional difficulty vector (covering navigation depth, visual complexity, reasoning difficulty, and other axes) at three levels each. The Generation Agent builds functional HTML/CSS/JS websites populated with real data collected from the web. The Refinement Agent injects realistic noise such as pop-ups, cookie dialogs, and network delays. The Validation Agent checks that each task is actually solvable. The resulting environments require no external services and can be run by opening an HTML file.
Results On WebForge-Bench (934 tasks), difficulty stratification effectively separated model capabilities: Level 1 tasks were solved by at least one model 95% of the time, while Level 3 tasks remained unsolved by all 14 evaluated models 23.5% of the time. Cross-model experiments revealed distinct capability profiles invisible to aggregate scores — for example, the strongest model (Gemini-3-Pro, 75.9% overall) dropped 35 percentage points on Visual Complexity tasks from Level 1 to Level 3, while a mid-tier model (Gemini-3-Flash, 67.1%) dropped 42 percentage points on both Information Complexity and Reasoning tasks. The weakest model (GPT-5-Nano, 31.3%) achieved near-zero accuracy on all dimensions at Level 3.
- NumLeak: Public Numeric Benchmarks as Latent Labels in Foundation Models
Synthesis
Plain-language abstract This paper introduces NumLeak, a measurement framework for detecting when large language models have memorized public numeric benchmark data — such as financial return series, unemployment figures, and climate records — and are recalling those memorized values rather than reasoning from scratch. It tests several top-tier models (including Claude Opus, Sonnet, Haiku, and GPT-5.4) and shows that the best models reproduce historical data with near-perfect fidelity, raising serious concerns about evaluations that use those same public datasets.
Motivation Public numeric datasets like the Fama-French factor library, macroeconomic releases, and NOAA temperature records are widely mirrored online and likely appear in the pretraining corpora of large language models. If a model can retrieve historical values simply from a date and a series name, then any evaluation or financial strategy that conditions on those dates may be measuring memorized recall rather than genuine predictive skill — a form of data contamination that prior work on verbatim text extraction had not specifically addressed for continuous, date-indexed numeric series.
Methodology NumLeak combines API-boundary behavioral probes on closed production models with a controlled white-box validation on an open model. Four diagnostic metrics are used jointly: Pearson correlation with published ground truth, mean absolute error, within-25-basis-point accuracy, and sign accuracy, along with parse rate to track refusal behavior. The identification protocol applies factor-specificity contrasts, temporal stratification, fabricated-series probes, and rank/value decoupling tests. For white-box validation, the authors LoRA fine-tune Qwen-2.5-1.5B-Instruct on a synthetic date-indexed series (SMR-A) at four exposure levels (0x, 1x, 5x, 20x mentions per date-value pair) and probe using both open-ended generation and direct log-probability inspection.
Results Top-tier frontier models recall Fama-French market excess returns at 3-seed pooled Pearson r=0.97-0.99, with comparable fidelity on U.S. unemployment, CPI inflation, and NOAA temperature. Recall weakens monotonically with model capability within each provider (Opus 4.7 at r=0.99, Sonnet 4.6 at 0.97, Haiku 4.5 at 0.57). On a recent-release holdout, parse rate collapses to 21-57% but correlation stays near 0.99 on the months the model does answer, consistent with a memorization channel bounded by training data availability. A system-prompt defense blocks 99.8% of a non-adaptive single-turn suffix attack at near-zero utility cost, and a regression using a model's own date-to-market-sentiment output collapses from r=0.74 to r=0.02 once the model's recall is residualized out.
- Same Ranking, Different Winner: How Scoring Targets Shape LLM Memory Benchmarks (TIAP)
Synthesis
Plain-language abstract Modern AI assistants often store conversation history as multiple forms — raw dialogue turns, extracted facts, summaries, and timelines — all linked to the same original source. When benchmarks test how well these systems retrieve relevant memories, they must choose which stored form counts as a correct answer. This paper shows that this seemingly minor choice — called the scoring target — is routinely left unspecified, and that changing it can flip which system looks better without changing how either system actually behaves.
Motivation Conversational memory benchmarks are increasingly used to guide design decisions about how AI systems store and retrieve dialogue history. When a memory system transforms raw conversation turns into facts or summaries, multiple stored versions of the same evidence exist in the same index. Benchmarks implicitly choose which version to credit as correct, but this choice is almost never stated explicitly — creating a hidden variable that can change benchmark conclusions without changing the underlying retrieval system.
Methodology The authors introduce TIAP, a fixed-output audit procedure that rescores already-saved ranked retrieval outputs under three different scoring targets — Raw (only the original source turn gets credit), Source (any stored descendant linked to the same source gets credit), and Canonical (only transformed serving-form memories get credit) — without re-running retrieval. They apply this to two benchmark datasets, LoCoMo and LongMemEval-S, across four retrieval providers, and also test transfer to two external memory architectures, Mem0 and MemoryOS. A 1,902-case semantic audit using five large language models as judges assessed whether relaxed credit was semantically warranted.
Results Switching only the scoring target changed nDCG scores on 83.4% to 94.0% of shared queries across the two benchmarks and four retrievers. The same fixed ranked outputs flipped the winner ordering between memory architectures (Mem0 and MemoryOS) depending on which target was used, and reversed recommendations about parser density (how many facts to extract per turn). The semantic audit found that relaxed source-linked credit was fully supported by the retrieved content only 29.2% of the time under a five-model majority vote, with 31.2% of relaxed credits entirely unjustified. The authors conclude that benchmark conclusions about memory system design can silently reverse based solely on which stored form is credited, and recommend that all conversational-memory papers explicitly define and report their scoring target.
- MemConflict: Evaluating Long-Term Memory Systems Under Memory Conflicts
Synthesis
Plain-language abstract MemConflict is a diagnostic framework for testing whether AI conversational agents can correctly handle conflicting information in their long-term memory. It introduces a benchmark where user facts change over time, contradict each other, or apply only under certain conditions, then measures whether six representative memory systems retrieve and use the right information to answer questions.
Motivation Conversational AI agents rely on long-term memory to track user-specific facts across many sessions, but user information is not static: it evolves, can be contradicted, and may apply only in certain contexts. Existing evaluations mostly measure whether a system gives the right final answer, which obscures whether failures come from retrieving the wrong memory, ranking it too low, or failing to use a correctly retrieved memory. No prior framework systematically diagnosed these distinct failure modes under conflicting memory candidates.
Methodology The authors define three conflict types — dynamic (a later update supersedes an older state), static (a false contradiction should not overwrite a stable fact), and conditional (multiple memories are valid under different conditions) — grounded in an information-quality notion of fitness-for-use. They simulate long-horizon multi-session conversation histories from structured user profiles, inject cross-session conflicts, and add semantically similar distractors to create competition among memory candidates. A two-level evaluation protocol combines black-box scoring of final answers with white-box inspection of which memory items were retrieved and ranked, applied to six representative long-term memory systems.
Results Experiments on six systems show uneven strengths across conflict types, with no system dominating all three. Answer correctness frequently diverges from memory retrieval quality, revealing a measurable Evidence Utilization Gap. Retrieval failures account for the majority of errors across most systems and conflict types, but non-trivial utilization failures also appear — notably, LangMem under dynamic conflicts more often retrieves the relevant memory but still produces a wrong answer than it fails to retrieve it at all. Performance degrades with longer histories, more distractors, implicit queries, and larger conflict distances between conflicting memory entries. MemOS shows the strongest overall performance and efficiency, while Letta is competitive on conditional conflicts and LangMem is strongest on dynamic conflicts.
- Engram: A Bi-Temporal Memory Engine Where a Lean Retrieved Context Beats the Full History
Synthesis
Plain-language abstract Engram is an open-source long-term memory engine for LLM agents. Instead of replaying an entire conversation history into the prompt, it stores the past as a bi-temporal knowledge graph and retrieves a small, precisely-targeted slice at answer time. On a standard 500-question memory benchmark that lean ~9.6k-token slice answers more accurately than feeding the model the full ~79k-token history, turning memory from a cost optimization into an accuracy improvement.
Motivation Stateless LLM agents forget across sessions, and the usual fix — concatenating the whole history — grows token cost and latency linearly and loses accuracy as distractors crowd the window ('lost in the middle'). Two gaps stay open: most memory systems are cheaper or faster but not more accurate than full-context, and memory benchmarks run on inconsistent harnesses where one system reports wildly different scores across sources. Engram targets both — beating full-context on accuracy, and shipping a neutral, re-runnable harness.
Methodology A dual-process design. A System-1 hot write path appends lossless episodes with no LLM (sub-50ms) and enqueues them. A System-2 async path extracts atomic (subject,predicate,object) facts, builds a bi-temporal knowledge graph (valid time vs transaction time on every fact and edge), detects conflicts, and resolves them cheap-then-escalate: exact slot match, embedding similarity, and content subsumption handle the common case with no LLM call, invalidating (never deleting) a superseded fact and recording a supersedes chain and provenance, with only ambiguous cases escalated to an LLM adjudicator. The hybrid read path retrieves through four channels (dense, BM25, graph n-hop, recency/salience), fuses them with Reciprocal Rank Fusion, applies an 'as-of' temporal filter and an abstention gate, and assembles a deduplicated, provenance-tagged, token-budgeted context of facts plus raw chunks.
Results On the full 500-question LongMemEval_S under the official category-specific judge, Engram's lean configuration scores 83.6% vs 73.2% for full-context (+10.4 points, McNemar exact p<10^-6) at ~8x fewer tokens (9.6k vs 79k), 0/500 errored. The gain is load-bearing on the read path being hybrid: facts alone lose recall, while facts plus retrieved chunks recover detail. Bi-temporal modeling pays off most on knowledge-update (87.5%) and temporal (81.1%) categories, while multi-session aggregation and preference remain headroom. The paper documents measurement-integrity pitfalls (truncation, home-grown judges, full-history leaks) and ships a neutral in-repo harness with the official judge baked in and raw per-question logs, every number reproducible by command.
- GitOfThoughts: Version-Controlled Reasoning and Agent Memory You Can Replay, Diff, and Merge
Synthesis
Plain-language abstract GitOfThoughts stores an LLM agent's reasoning tree as a git repository — every scored thought is a commit, scores are git notes, validation outcomes are tags, and retrieval is git log over the agent's own history — which makes reasoning replayable, auditable, diffable, and mergeable across agents. The paper then asks the harder question of whether memory, in any substrate, actually improves accuracy, and runs a pre-registered comparison of five substrates (none, markdown, vector, graph, git).
Motivation Reasoning is the last unversioned software process: chains of thought expire with the context window, pruned search branches leave no record, and memory buffers cannot be diffed, merged, or audited. The authors argue this ephemerality is a structural blocker — it prevents reproducibility ('what did the agent think at step 17?'), audit (detecting train–test leakage or gold-answer memorization), memory transfer between agents, and incident review. Code, infrastructure, datasets, and experiments are all version-controlled; reasoning is the remaining outlier.
Methodology A reasoning tree shares git's structural invariants, so the paper maps it one-to-one onto git primitives (node = commit, refinement = parent edge, score = note, outcome = tag, session vs. cross-session = branch, retrieval = git log --grep / -S). A pluggable MemoryBackend routes every read/write through one interface so the same agent can swap substrate with a one-line change. To isolate retrieval from write-path noise, all five backends ingest identical answer-free lessons, then solve held-out, domain-stratified problems read-only; benchmarks are GPQA-Diamond and MATH-500, scored with paired-bootstrap CIs, across two backbones and pre-registered replications, with a similarity sweep to locate when retrieval helps.
Results H-substrate is supported: git delivers auditability, line-level diffs over reasoning text, deterministic replay by SHA, and mergeable memory at accuracy parity, costing ~15 ms/write and ~48 ms/read. H-memory is rejected: across two benchmarks, two backbones, and up to n=500, no substrate reliably improves accuracy on novel problems, and a +15 pp git trend at n=40 collapsed under its pre-registered replication. Memory pays only above a 'copyability threshold' — a near-duplicate retrieved case (cosine ≳ 0.8) lifts accuracy +12 to +13.5 pp, and a 4.5× larger model steepens that step to +22.5–28.5 pp but still extracts no transferable method; the only general accuracy lever is test-time sampling (self-consistency, +3.4 pp at n=500). The authors deliberately document a measurement bug, a retracted result, and a refuted hypothesis as the evaluation standard.
- StreamMemBench: Streaming Evaluation of Agent Memory for Future-Oriented Assistance
Synthesis
Plain-language abstract StreamMemBench is a streaming benchmark that tests whether a personal-agent memory system can turn what it observes and how users interact with it into future-oriented assistance. Built on EgoLife egocentric lifelogs, it anchors each evaluation on a hidden piece of user-specific evidence and wraps a two-step task around it: an initial task that depends on the evidence, then a follow-up task that tests whether the agent reused both the evidence and the user's feedback. Four metrics diagnose evidence retention, feedback incorporation, initial evidence use, and follow-up reuse.
Motivation A central job of personal-agent memory is to carry stored observations and prior interactions forward into later, similar tasks, but existing memory benchmarks test dialogue recall or task improvement in isolation and usually rely on scripted or synthesized dialogues whose feedback is not tied to verifiable observations. That leaves the trajectory from streaming observations to later assistance largely untested — and even commercial assistants such as ChatGPT and Gemini store information that fails to help when it is actually needed.
Methodology In the construction stage an anchor agent processes five-minute EgoLife segments in stream order and extracts a user-specific evidence anchor plus two application-oriented queries, and a review agent retains a candidate only if both queries satisfy Leak=0 (the query does not reveal the evidence), Need=1 (ignoring the anchor yields a wrong or generic answer), and Natural=1 (it reads as a plausible request). In the evaluation stage the memory system ingests the lifelog chronologically, answers the initial task, receives confirming or correcting feedback from a user simulator, commits that interaction to memory, and then answers a follow-up task grounded in the same anchor; an evaluation agent scores Fidelity, Feedback Incorporation, Initial Evidence Use, and Follow-up Reuse against atom-level checklists, and the Fidelity−IEU / Fidelity−FUR gaps localize failures.
Results Across eight systems — two retrieval baselines (RAGraw, RAGext) and six memory systems (A-Mem, Mem0, EverMemOS, MemOS, MemoryOS, MemSkill) — on two backbones, current memory systems are not yet reliable for future-oriented assistance: they often fail to use evidence from egocentric observations in the initial task and to turn interaction feedback into reusable follow-up behavior. The failures are not explained by storage alone — systems frequently retain the evidence (with some Fidelity inflated by raw-text retention) yet do not use it — which motivates evaluation that traces each piece of evidence from its first appearance in the stream through initial use, feedback incorporation, and follow-up reuse.
- MemTrace: Probing What Final Accuracy Misses in Long-Term Memory
Synthesis
Plain-language abstract MemTrace is a benchmark for testing how well an AI assistant remembers facts about a user across many conversations. Instead of scoring isolated questions, it tracks each individual fact—like a user's job title—and repeatedly asks about it under different conditions: long after it was mentioned, when it has since changed, or when the question contains false information. This reveals failures that a single overall accuracy score hides, such as a system that recalls a user's current role correctly but invents a false history of how they got there.
Motivation Long-term memory benchmarks usually aggregate accuracy over question rows or interaction episodes, treating questions that probe the same underlying fact as independent items. That makes it impossible to hold a fact fixed and ask how a system behaves as conditions around it change—whether it still recalls a fact after many sessions, whether it tracks how the fact evolved, and whether it behaves safely when evidence is missing or contradicted. Two systems with similar pooled scores can fail in entirely different ways, and aggregate scoring cannot show which.
Methodology MemTrace makes the knowledge point—a single typed fact about the user—the unit of measurement, and probes each fact along three controlled dimensions: memory age (how many sessions ago it appeared), question type (current state, an earlier state, or the trajectory of change), and evidence condition (present, missing, or contradicted by a false premise). It comprises 835 typed knowledge points from 20 users, expanded into 15,422 question rows and over 200,000 scored answers, and evaluates 13 memory-system configurations across four paradigms: long-context models, retrieval-augmented systems, external-memory stores, and agentic-memory architectures. A diagnostic step classifies each failure by whether the needed evidence was unreachable or reachable but unused.
Results Performance varies systematically across all three dimensions. Long-context systems answer recent facts well but lose accuracy as facts age, especially on trajectory questions; RAG systems, including graph-based retrieval, handle current and earlier-state questions better than questions about change over time; some external-memory systems decline almost all questions about facts that were never mentioned yet rarely correct a false premise. The dominant remaining bottleneck is evidence use, not retrieval: when systems fail, the evidence was already retrievable about 10× more often than it was missing, so improving memory depends on using reachable evidence rather than storing or retrieving more.
- SEAGym: An Evaluation Environment for Self-Evolving LLM Agents
Synthesis
Plain-language abstract SEAGym is a testing environment for AI agents that improve themselves over time by editing their own setup—their prompts, memory, skills, tools, and configuration—rather than by retraining the underlying model. Instead of just checking whether a self-improved agent scores higher on a final task, SEAGym measures the improvement process itself: whether each self-edit actually helps on new tasks, whether gains stick or later collapse, and what they cost.
Motivation Self-evolving agents improve mainly by changing their agent harness—the structured execution layer around a base model. Existing evaluations reduce this to isolated task scores or a single sequential learning curve, which obscures whether a given update produces reusable improvement, overfits the recent tasks, increases cost, or harms older behavior. Most agent benchmarks are built for static evaluation, resetting agent state between isolated episodes and removing exactly the state persistence that self-evolution depends on.
Methodology SEAGym uses an RL-style environment formulation in which the self-evolving agent supplies both the task policy and the harness-update rule, while the environment defines task sampling, feedback, schedules, and snapshot assessment. It converts Harbor-compatible static benchmarks into reusable task sources organized into train batches and frozen evaluation views—update-validation, held-out in-domain transfer, out-of-domain transfer, replay diagnostics, and cost records—and saves agent snapshots and metric artifacts. Explicit schedule parameters (state reset, task reuse, batch size, update timing) let single-task adaptation, online transfer, and epoch-based batch learning be studied under one protocol. Task rollout is separated from method update, so methods such as ACE, TF-GRPO, and AHE connect through thin wrappers while keeping their native update rules; experiments instantiate the environment on Terminal-Bench 2.0 and HLE.
Results The evaluation views provide complementary signals about the evolution process rather than one summary number. Frequent updates may fail to improve held-out performance, validation gains do not always transfer to in-domain or out-of-domain test views, and useful intermediate snapshots can collapse later or recover. Batch size, source diversity, and the rollout model backend all affect harness reliability, showing that self-evolution dynamics depend on the evaluation schedule and setup, not just the update method.
- MemOps: Benchmarking Lifecycle Memory Operations in Long-Horizon Conversations
Synthesis
Plain-language abstract MemOps is a benchmark that reframes long-term conversational memory as a lifecycle of explicit operations (remembering, forgetting, updating, reflecting, and their compositions) rather than as static question answering. Each memory event is a structured trace specifying its trigger, target, scope, state transition, and supporting evidence. A controllable pipeline embeds these operations into long, task-oriented conversations, producing gold operation traces and six categories of operation-level probes evaluated under both adjacent-evidence and long-context settings. Across long-context, retrieval-based, parametric, and managed-memory systems, MemOps disentangles failure modes that final-answer accuracy alone conceals.
Motivation Existing long-term memory benchmarks such as LoCoMo, LongMemEval, MemBench, and others evaluate almost exclusively through downstream question answering, scoring only the correctness of a final answer. That black-box formulation conflates heterogeneous causes of failure (missing the introduction of a relevant fact, binding an operation to the wrong target, or relying on a stale value after a correction) and can credit a correct answer that rests on an inconsistent or unsafe memory state. This is most acute in dynamic long-horizon interaction, where memory functions as a lifecycle process: a user introduces a fact, corrects it, asks that part be forgotten, or implicitly signals a preference, each of which is a distinct operation with its own trigger, target, scope, state transition, and characteristic failure modes that downstream QA cannot diagnose.
Methodology Each instance is a tuple of a topic-specific user background, a set of evidence conversations, a gold operation trace, and evaluation probes. The trace is the evaluation anchor: each operation carries a type, target object, old and new value, and evidence spans quoted verbatim from user turns. Five operation types are defined, including TrajectoryOps that compose remember, update, forget, and reflect events across time so the benchmark can check intermediate states and their temporal order. A four-stage generation pipeline (background construction; evidence conversation and gold-trace generation; operation-level probe generation; long-context dialogue generation with distractor pools) produces natural conversations with explicit operation supervision, verified by local schema and span gates plus an LLM verifier. Six probe categories (operation trace, target binding, state transition, candidate disambiguation, operation application, state trajectory) score intermediate memory behavior, and representative systems from four paradigms are evaluated under adjacent-evidence and long-context settings.
Results Performance is strongest when evidence sits adjacent to the query and degrades consistently once it is dispersed into long, distractor-laden histories, for both answer accuracy and operation-level reliability. Session-level retrieval substantially outperforms turn-level retrieval, and managed-memory services that preserve longer, context-rich memory units outperform those storing short, isolated facts, indicating that surrounding context is critical for correctly executing lifecycle operations rather than merely retrieving relevant content. Parametric memory, which folds interaction history into model parameters, remains markedly unreliable across almost all diagnostic dimensions. Reconstructing an ordered memory-state trajectory across multiple composed operations is far more fragile than any single-step operation, and this weakness persists even for otherwise strong long-context models, exposing a failure mode that final-answer accuracy alone would not surface.
- Reclaim Evaluation: A Lossy Memory Is Worse Than an Empty One
Synthesis
Plain-language abstract A language model's memory can be worse than no memory at all. Give a model a memory that kept a wrong conclusion but dropped the work behind it and it re-emits the stale value as a confident answer; give the same model an empty memory and it abstains. The paper names this failure brittle memory, measures it with a reclaim-evaluation protocol that tests whether a correction can recover a known answer after compression, and shows a one-line fix (keep the recomputable source, drop the re-derivable conclusion) restores correctability at equal memory budget.
Motivation Memory systems carry information across sessions by compressing it, on the implicit assumption that a compression preserving the model's answer has preserved what matters. The paper shows the same compression decides whether the model can later be corrected: once the answer-determining source is gone, a correction has nothing to act on, and the resulting error compounds as deployed agents feed memory into memory.
Methodology Reclaim evaluation drifts a model into committing to a wrong answer via a planted premise, deepens the commitment over neutral turns, then issues a correction in a fresh session whose only inheritance is a memory written under one of three matched-budget policies: lossy (keep the salient conclusion, shed the source), source-first (keep the source, shed the conclusion), and lossy-padded (lossy plus neutral filler to at least source-first's length, controlling for budget). Success is exact recovery of the known answer, with no judge. Tasks are multi-step arithmetic and constraint-logic puzzles with objectively scorable answers; the pipeline runs end to end on llama-3.1-8b and grok-4.3 with a frontier replay on Claude models; headline cells are n=96, and three validators designed to fail against a deterministic fake all pass.
Results Within one conversation there is no wall, only anchoring: a directed correction holds far longer than a generic one (reclaim 0.79 to 0.50 over eight commitment turns) and pushing the error further back lifts reclaim rather than starving it. Across a session boundary the window becomes a wall: once the lossy note drops the source line items, even a directed correction dies, reclaim is 0.00 by measurement, and a lossy memory is worse than an empty one because models that abstain with nothing emit the confident wrong value with a source-less note. The wall sits in the same place from the 8B model to frontier systems. Source-first restores reclaim at equal budget (oracle 1.00; the deployable one-prompt distiller 0.49-0.88, concentrated on compact numeric sources), and the length-matched control rules out added text as the cause. Chained through a memory loop, one dropped-source error corrupts a growing span of downstream steps and stays uncorrectable however late it is caught, while source-first holds to a bounded budget horizon; the wall and the fix replicate on three deployed memory systems and on MultiWOZ, and past the budget where the source no longer fits, the fix fails silently unless the note records its own completeness.
- RECON: Benchmarking Agent Memory for Compositional Reasoning over Long Contexts
Synthesis
Plain-language abstract RECON (Reasoning over Extended Contexts with Obfuscated Narratives) is a benchmark that tests whether an agent's memory can maintain a coherent, evolving understanding over long contexts where facts do not just accumulate but interact, contradict, and cascade. It spans 24 investigative case files across criminal, medical, and financial domains, each 50k to 100k tokens, with 1,604 questions over six memory-intensive tasks, and reports that even the strongest non-Oracle system reaches only 22.4% accuracy.
Motivation Existing memory benchmarks model memory as a state machine: they check whether an agent can retrieve a scattered fact or detect that a fact changed. Real workflows demand more. When a lab result is revised on Day 9, a witness statement is contradicted on Day 5, or a flagged transaction is reversed, an agent must trace which downstream conclusions are affected, which survive on independent support, and how an alternative timeline would have unfolded. RECON targets what happens after a change, not just whether the current value is tracked.
Methodology A deterministic pipeline constructs each case from a provenance DAG, then a question generator traverses the DAG to synthesize questions per task category, with a fixed question matrix enforcing per-task and per-format quotas so the distribution does not drift between runs. The six tasks are chain reconstruction (order 5-15 evidence hops), cascade propagation (which conclusions break versus survive after an invalidation), source-conflict resolution, counterfactual reasoning, temporal-constraint satisfaction, and temporal fact retrieval as a control. Solvers - long-context, RAG, hybrid RAG, Supermemory, Mem0, Mem0-Graph, Hindsight, closed-book, and an Oracle handed the full structured ground truth - share one answering template; freeform answers are graded by two independent LLM judges from different model families and averaged, while other formats are scored deterministically with an explicit abstain option (+1 correct, -0.2 wrong, 0 abstain).
Results Even the Oracle given the ground-truth dependency graph reaches only 54.6% accuracy, and the best non-Oracle system 22.4%; RAG attains 20.6% on full-coverage retrieval hits. Decomposing failures shows roughly four in five persist even when retrieval succeeds, placing the bottleneck in reasoning rather than evidence selection. Human annotators reach 63.0% accuracy, exceeding the Oracle solver by 8.4 points and confirming reasoning, not retrieval, as the residual challenge across long-context, retrieval, and agentic-memory architectures.
- The Regression Tax: Decomposing Why Skills Help and Hurt LLM Agents
Synthesis
Plain-language abstract Procedural skills for LLM agents are normally judged by average improvement in task success, which hides the tasks a skill library breaks. Running the same agent with and without skills across 5,832 paired task-condition runs on two office-automation benchmarks and three model-harness stacks, the paper decomposes each pass-rate change into gains and regressions. Regressions offset 59% of gross gains, and the best libraries lead mainly by regressing less rather than gaining more. Three regression mechanisms are identified from traces - skill-description osmosis, grounding displacement and verification displacement - and the residual failures cluster at grounding and verification, the stages existing skills least often address.
Motivation Systems that generate skills automatically from execution traces are evaluated by average gain, so two libraries with identical averages can differ sharply in how many working tasks they destroy. Methods that detect and drop harmful skills identify which skill to remove but not why it regressed a task, so a mostly useful skill may be discarded wholesale. Those methods also act only when a skill is retrieved or invoked, while a skill's name and description remain in the system prompt at every step and can change behavior without ever being called - a channel selection-based approaches cannot observe.
Methodology Two benchmarks over real artifacts: OfficeQA-Pro (question answering over U.S. Treasury financial documents, where the hard part is finding the right table, vintage and definition rather than the arithmetic) and SpreadsheetBench (workbook manipulation from real Excel-forum problems, graded on exact cell values). Three stacks pair a harness with its usual model: OpenCode / minimax-m2.7, Codex / gpt-5.4-mini, Claude Code / sonnet-4.6. Each stack and benchmark runs under four conditions - none, plus three libraries built by different meta-skill creators from the same analyst-extracted failure signals, so only the library text changes within a stack. Every task falls into gain, regression, residual failure or retained against the no-skill baseline; net effect is gains minus regressions, tested with the exact two-sided McNemar test on discordant pairs with Newcombe 95% intervals. Skill invocation is read from the trajectory so presence-only influence can be separated from body engagement. Each condition is run once per task, so run-to-run variance is not estimated.
Results Regression counts range from 2 to 41 across the eighteen library conditions and never reach zero; 324 regression transitions cancel 59% of 553 gains, with the pattern holding on both benchmarks (66% of gains cancelled on OfficeQA-Pro, 56% on SpreadsheetBench). Even clearly positive cells are close-run: on SpreadsheetBench the openai library broke 41 while gaining 45 on one stack and broke 27 while gaining 30 on another. Five of eighteen conditions reach nominal p < .05, but only three survive Bonferroni correction, all on Claude Code / sonnet-4.6 with SpreadsheetBench - a real but narrow effect. Grounding displacement accounts for 72.8% of the 81 coded OfficeQA-Pro regressions and osmosis for 17.3%; on SpreadsheetBench osmosis accounts for 70 of 243 regressions against 46 with the body engaged and 32 attributable to a grader artifact. Body engagement is set by the harness rather than the skill: the same library is invoked on 73-91% of OfficeQA-Pro tasks but 5-14% of SpreadsheetBench tasks on one stack, and on 99-100% versus 0-1% on another. Correcting the known grader artifact required re-grading 226 treatment task-conditions with a full spreadsheet engine, since the default engine cannot recalculate Excel structured references and scores correct formulas as failures.
- On the Fragility of Self-Improving Agents: Variance, Task Order, and Underspecification
Synthesis
Plain-language abstract A re-evaluation of memory-based self-improving web agents (Agent Workflow Memory, ReasoningBank) across WebArena, VisualWebArena, and SCUBA, adding multiple runs and randomized task ordering to standard single-run, fixed-order evaluation. Both additions expose that reported improvements are considerably less stable than prior single-run reports suggested.
Motivation Self-improving agents that write and reuse a textual memory bank across a stream of tasks are promoted as a path to reliable long-horizon automation, but their reliability under realistic conditions — repeated runs, unordered task streams — had not been stress-tested. In enterprise deployment, tolerance for early failure is low and mistakes compound silently.
Methodology The authors re-run Agent Workflow Memory and ReasoningBank with a stronger base model and harness, then extend evaluation along two axes: multiple runs of the same setting to quantify variance, and randomly shuffled task orders to test sensitivity to the default (often implicitly easy-to-hard) task curriculum. They then manually inspect agent-written memories to identify failure drivers, and test whether adding rubrics and environment feedback to memory construction narrows the gap.
Results Variance across runs increases in 71% of settings when a self-improving loop is stacked on a baseline agent; on WebArena's GitLab subset, the best/worst run gap widens from 4.4% (no memory) to 7.8% (ReasoningBank). Under the default task order, ReasoningBank gains 1.5% on average; under random shuffling, it degrades by 4.5%. Manual inspection attributes much of this to task and environment underspecification, which causes agents to write plausible but inapplicable memories; adding rubrics and environment feedback partially, but not fully, closes the degradation.
- Can Agent Memory Systems Track Evolving State?
Synthesis
Plain-language abstract A benchmark and method for a memory capability separate from recall: keeping track of which version of a fact is currently in force after it has been revised across sessions. The benchmark, StateMemBench, generates each scenario as a symbolic program of state operations so the correct answer is computed by replay and the specific way a lazy reader would get it wrong is known in advance. The method, StateMem, parses each turn into structured state units with typed dependency links, then handles supersession and staleness deterministically rather than with an LLM.
Motivation Existing memory systems and benchmarks optimize recall of relevant facts, but as agents run longer, facts, constraints and decisions get revised, and an answer must reflect the current state rather than a superseded one. The authors call the failure state drift: the relevant fact is present in the assembled context, but the agent acts on a stale or incomplete version of it. This is distinct from dialogue state tracking, which prescribes a slot-value representation and evaluates it directly over cooperative dialogues that accumulate a goal monotonically; here state is whatever a system must maintain to answer correctly, evaluation is purely behavioral, and revisions are adversarial across sessions. Some concurrent work centers state, but the authors argue none cleanly isolates state tracking from the other errors it co-occurs with.
Methodology The authors first define and label drift on existing benchmarks, assigning a failure to drift only after excluding retrieval, comprehension, schema and reasoning readings, dropping unassignable points, and cross-checking with two judge passes, a cross-family judge and two human annotators. They then build StateMemBench: each scenario is a symbolic event program of typed operations over ground, derived and declared state; the gold answer comes from deterministic replay; a family of executable lazy reader policies is run against the replay, and a scenario is admitted as a trap when policies disagree, with the disagreeing set forming its failure-mode signature (status, salience, sequence, compound, plus anti-trap controls). Programs are grounded in public data for surface vocabulary and rendered into multi-session dialogue by a strong LLM, then programmatically verified for fact placement and phrase leakage. Probes are closed-pool: an unseen pool of three to four options holds the gold answer, the targeted policy's drift answer and neutral distractors. StateMem itself runs a per-turn TurnEncoder producing state units (id, content, priority, source, deps), a deterministic update stage applying supersessions and marking dependents needs_recheck by dependency-graph traversal, and a single answer-time call over the assembled active state. A wrapper variant applies the same trace-then-resolve structure as a prompt-level transformation of any backend's answer call, evaluated against a length- and cost-matched generic-extraction control.
Results Drift leads the confirmed failure distribution on several existing benchmarks (63.5% on MemoryArena-shopping, 44.4% on LongMemEval oracle where retrieval is perfect by construction, 10 of 16 on tau-squared-bench-Z) but is not universal, falling to 19.0% on MemoryArena-travel. On StateMemBench, long-context is not the strong baseline it is on recall tasks: the best long-context model reaches 0.277 and same-backbone long-context 0.149. StateMem reaches 0.363 on DeepSeek-V4-Flash, 1.8x the best memory system and 2.4x same-backbone long-context, and 0.233 on Qwen-3.5-9B, 1.6x the best memory system, both significant by paired McNemar at p < 0.001; GraphRAG at 0.224 is statistically level on Qwen. Ablations put supersession marking as the largest single component and show dependency propagation over-fires on Set B anti-traps by 12.5 points, so removing it leaves DeepSeek slightly better. Drift-rate analysis shows the memory layer barely changes outcomes on a weak answerer, where every arm drifts at 61 to 66%, and separates on the stronger backbone, where StateMem's drift rate falls 15 points and correct answers rise by 42 while long-context, Mem0 and BM25 move by 1 to 3 points. The wrapper improves every one of six backends on both benchmarks, adding 31.7 to 66.6 points on StateMemBench with 15.0 to 31.7 attributable to state structure over the matched control, significant in all twelve cells. State tracking does not cost recall: StateMem also leads memory systems on LongMemEval (0.656 on DeepSeek) and LoCoMo (0.592), with margins concentrated on temporal-reasoning and knowledge-update question types. The authors note StateMem mirrors the policy family behind the traps, so its StateMemBench margins should be read as an upper bound.
- Remember, Verify, or Ask? Cross-Family Evaluation of Memory Commitment in LLM Agents
Synthesis
Plain-language abstract A benchmark for the decision an agent makes before it writes to memory: should this piece of interaction-derived information be persisted durably, used only in the current context, re-checked against the world, or clarified with the user. It evaluates three models from two families under three prompt conditions, and separately tests whether the stated decision predicts which memory tool the model actually calls.
Motivation Persistent memory personalizes an agent, but an incorrect durable update silently distorts future behavior. A temporary request should not become a standing preference, a service status can go stale, one tool failure may be noise, and an underspecified correction may need a question before it is generalized. The authors argue the critical capability is not recall but commitment, and that two sources of uncertainty are usually collapsed: verification queries the world, which is authoritative for changing facts, while clarification queries the user, who is authoritative for intent and scope. Prior work covers adjacent targets (binary session-level storage gating, ADD/UPDATE/DELETE/NOOP operations, whether retrieved memory grounds tool parameters, general ambiguity clarification) without jointly distinguishing durable storage, local use, world verification and user clarification at commitment time.
Methodology Each item supplies an acquire context, a candidate update and a later reuse context, with a gold action assigned by released rules and a tie between persist and a weaker action resolved toward the weaker commitment. 140 primary scenarios are split 70/70 by sorted identifier within category, covering stable and episodic preferences, freshness-sensitive facts, one-off corrections, policy constraints, ambiguous updates and noisy failures at 20 items each, with eight lexical traps where a surface cue points to the wrong action. Two non-authors labeled the held-out and contrast items blind to author labels and to each other, with a blind third resolving ties. Claude Haiku 4.5, Claude Sonnet 4.6 and a locally served Qwen3.5-9B (Q4_K_M via Ollama, temperature 0, seed 13, thinking disabled) were each run under three conditions: a bare prompt defining the actions, a policy prompt adding five commitment rules including the tie-breaker, and a four-shot prompt with one development example per action. A separate track, MCB-Act, removes the label vocabulary and requires one structured tool call, scored by mapping the selected tool to an action. Analysis uses accuracy with bootstrap intervals, macro-F1, over-memory, under-memory and per-class recalls, with exact paired McNemar tests and Holm correction within each family of comparisons.
Results Both model families under-ask. Claude label-mode verification recall runs 0.889 to 1.000 while clarification recall runs 0.500 to 0.750; bare Qwen verifies 12 of 18 freshness items and asks on 0 of 12 clarification items. Few-shot prompting lifts Qwen accuracy from 0.557 to 0.771 (paired delta +0.214, p_H = 0.002) and clarification recall from 0 to 0.333, still missing 8 of 12. The policy prompt raises Qwen accuracy by only 0.071 (p_H = 0.539) but cuts erroneous persistence from 0.243 to 0.100 (p_H = 0.038), moving the uncertainty to verification (recall 0.667 to 0.944) rather than to the user (clarification 0 to 0.083). Haiku's policy and few-shot gains survive correction (p_H = 0.002 and 0.047); Sonnet's do not, so the benchmark measures a prompt-conditioned commitment policy rather than a fixed model trait. Label-to-tool agreement is 0.571 for each Claude model and 0.229 for Qwen; Sonnet accuracy falls from 0.814 to 0.529 (p_H < 0.001) and Qwen from 0.557 to 0.343 (p_H = 0.047), with Qwen calling use_now on 54 of 70 items and verification recall collapsing to 0.056. All emitted arguments pass the deterministic well-formedness rules, locating the bottleneck in tool choice. On the combined 140 Qwen items of the contrast extension, bare, policy and few-shot accuracy is 0.614, 0.757 and 0.843, with clarification remaining the weakest class throughout; the authors retain the extension as a controlled sensitivity check rather than a claim of naturalistic external validity, since its rule-authored templates align closely with the explicit policy rules. MCB-Act scores tool-call selection and does not execute downstream effects.
Synthetic Data
Synthetic data generation for agent/memory evaluation: profile-driven dialogue simulation, LLM user simulators, controllable conflict/distractor injection, persona generation, synthetic-vs-real distribution gaps, and data quality/diversity for agentic memory eval
Key threads
- Profile/graph-conditioned generation: synthetic dialogue is increasingly driven by structured persona or knowledge-graph inputs (AgenticAI-DialogGen, Graph2Counsel) so that memory facts, topic continuity, and clinical/behavioral reasoning are controllable rather than emergent.
- Controllable distractor, conflict, and noise injection: benchmarks deliberately inject distractors (UniToolCall Hybrid-20), realistic user noise (VeriSim), and adversarial-abstention queries (EngramaBench) to stress retrieval and memory under non-ideal conditions.
- Synthetic-vs-real distribution gap as a first-class measurement: OmniBehavior and REALTALK frame the central risk that LLM user simulators homogenize personas and lose long-tail behavior; data realism must be measured against real traces, not assumed.
- Generator auditing by data composition: rather than judging generators only by downstream scores, the Quality–Diversity–Complexity framework (Havrilla) measures the synthetic data itself, surfacing quality–diversity trade-offs relevant to eval-set construction.
- Controlled, model-isolating eval protocols: memory benchmarks hold the answering model fixed and vary only the memory architecture (EngramaBench), and decompose scoring to fine-grained levels (UniToolCall call/turn/conversation) to attribute performance cleanly.
- User simulators as the trajectory engine: surveys of conversational user simulation and multi-turn agent evaluation (Ni; Guan) treat the LLM user as the driver of multi-session test trajectories, with the simulator's own fidelity being a separate evaluation problem.
Open gaps
- No standard quantitative fidelity metric ties synthetic memory-eval data back to real distributions; OmniBehavior names biases (persona homogenization, Utopian bias) but there is no agreed score for whether a synthetic multi-session memory set is realistic.
- Controllable conflict/contradiction injection for memory (the base review's MemConflict territory) is largely absent from the generation pipelines surveyed — distractor injection is well developed (UniToolCall, VeriSim) but principled generation of temporally-evolving contradictory facts to test belief updating is not.
- Benchmarks are tiny and persona-thin (EngramaBench: 5 personas / 100 conversations / 150 queries), leaving the scaling question — how to generate thousands of diverse, enterprise-relevant personas without collapsing to the 'average person' — unanswered.
- Procedural and semantic memory are under-covered relative to episodic/conversational recall; tool-use trajectory generation (UniToolCall) and conversational memory (EngramaBench, AgenticAI-DialogGen) are siloed, with no unified synthetic generator spanning semantic/episodic/procedural memory types.
- Contamination/leakage controls for synthetic memory benchmarks are barely addressed; none of the generation pipelines surveyed specify how to guarantee the eval data was not (or cannot be) memorized, despite this being a known agent-eval failure mode.
- REALTALK: A 21-Day Real-World Dataset for Long-Term Conversation
Synthesis
Plain-language abstract REALTALK is a dataset of real conversations collected over 21 days from messaging apps, where pairs of people who initially met through those apps exchanged daily messages. The dataset contains 10 unique conversations totaling more than 16,000 words each, and is used to evaluate whether AI language models can hold long-term, emotionally aware conversations the way humans do.
Motivation Most research on long-term dialogue systems uses synthetic conversations generated by AI models rather than real human exchanges, leaving it unclear whether those simulated dialogues capture the emotional nuance and persona consistency of genuine human interaction. REALTALK was created to fill that gap by providing an authentic benchmark that can be directly compared against LLM-generated conversation datasets.
Methodology Ten participants each engaged in two separate 21-day conversation threads with different partners via messaging apps, producing conversations that span approximately 21 daily sessions per pair. The dataset was analyzed for emotional intelligence attributes and persona consistency, and compared against LLM-generated conversations. Two benchmark tasks were then defined: persona simulation, where a model must continue a conversation on behalf of a specific user given prior dialogue context, and memory probing, where a model must answer questions requiring recall of information from earlier in a long conversation.
Results Analysis showed that real-world conversations contain more diverse emotional expressions and greater variation in persona stability than synthetic LLM-generated dialogues. Benchmark experiments found that models struggle to simulate a specific user's conversational style from dialogue history alone, but fine-tuning on that user's own chat history improves persona emulation. Existing models also faced significant challenges in recalling and leveraging long-term context from real-world conversations.
- AgenticAI-DialogGen: Topic-Guided Conversation Generation for Fine-Tuning and Evaluating Short- and Long-Term Memories of LLMs
Synthesis
Plain-language abstract This paper introduces AgenticAI-DialogGen, a software framework that automatically generates realistic, topic-organized conversations for training and testing AI language models on memory tasks. It also releases a new dataset called TopicGuidedChat (TGC) built from these generated conversations, which encodes both short-term and long-term memory cues for each pair of simulated speakers.
Motivation Existing conversational datasets lack the structure needed to train language models to reliably remember and reference information across a conversation — either they test short question-answering without capturing speaker personality, or they capture free-form dialogue without organizing it around coherent topics or memory. Creating such datasets manually is expensive and hard to do consistently, creating a gap that prevents progress on memory-aware conversational AI.
Methodology The framework takes an unstructured conversational dataset as input — primarily the Multi-Session Chat (MSC) dataset, restricted to 1,001 speaker pairs with four sessions each — and runs it through a pipeline of coordinated LLM-based modules and agents. These components preprocess conversations, extract factual knowledge triples, group them into topics, build per-speaker knowledge graphs, generate speaker personas, simulate multi-turn dialogues using LangGraph-based agents, validate and refine the output for topical adherence and quality, and finally produce memory-grounded question-answer pairs. The resulting TGC dataset stores long-term memory as structured knowledge graphs and short-term memory as simulated conversational turns.
Results Human and automatic evaluations show that AgenticAI-DialogGen improves discourse quality and topic coherence compared to baselines. Lightweight language models fine-tuned on the TGC dataset outperformed larger zero-shot models on memory-grounded tasks, demonstrating that the dataset's structured memory design provides practical utility for training memory-aware conversational systems.
- Evaluating LLM-based Agents for Multi-Turn Conversations: A Survey
Synthesis
Plain-language abstract This paper surveys how researchers evaluate AI chatbots and assistants built on large language models when those systems must hold multi-turn conversations — exchanges that unfold over many back-and-forth messages rather than a single prompt. The authors reviewed nearly 250 published studies to map out what is being evaluated and how, producing two classification frameworks that together cover the full range of current evaluation practice.
Motivation AI conversational agents powered by large language models are increasingly deployed in customer service, personal assistants, and other settings that require sustained, context-aware dialogue. Despite this growth, the field lacked a systematic overview of how such multi-turn systems are evaluated — what dimensions matter and what measurement methods are available — leaving practitioners without a consolidated reference.
Methodology Using a PRISMA-inspired systematic review process, the authors examined nearly 250 scholarly sources from a range of publication venues. From this corpus they constructed two interrelated taxonomy systems: one defining what to evaluate (task completion, response quality, user experience, memory and context retention, planning and tool integration) and one categorizing how to evaluate (annotation-based evaluations, automated metrics such as BLEU and ROUGE, hybrid human-plus-quantitative strategies, and self-judging methods that use LLMs as evaluators).
Results The survey produced a structured, dual-taxonomy framework covering both evaluation dimensions and evaluation methodologies for LLM-based multi-turn conversational agents. The framework captures traditional language-understanding metrics alongside newer techniques suited to the dynamic, interactive nature of multi-turn dialogue, offering a consolidated foundation for researchers and practitioners assessing conversational AI systems.
- Recent Trends in Personalized Dialogue Generation: A Review of Datasets, Methodologies, and Evaluations
Synthesis
Plain-language abstract This paper is a systematic survey of personalized dialogue generation — the field of building conversational AI systems that tailor their responses to individual users. The authors review 22 datasets, analyze 17 research papers published at top NLP conferences between 2021 and 2023, and summarize the evaluation metrics used across this body of work.
Motivation Personalization is increasingly important for conversational agents, especially as large language models can generate fluent but generic responses. The field lacks a unified definition of personalization — it can mean giving an agent a persona, modeling a user's traits, or both — and no comprehensive survey had catalogued the datasets, methods, and evaluation practices across this rapidly growing area.
Methodology The authors conducted a keyword-based literature search of top NLP venues (ACL, NAACL, EMNLP, AAAI, and others) covering 2021 through October 2023, selecting 17 seminal works. They systematically categorized 22 datasets by language, persona representation type (descriptive sentences or key-value pairs), data source (crowdsourcing or social platforms such as Reddit and Weibo), and features such as persona grounding labels and multi-session support. They then identified five distinct problem types across the surveyed methods and compiled a summary of evaluation facets and metrics.
Results The survey identifies five distinct problem formulations within personalized dialogue generation and highlights both benchmark datasets (such as PersonaChat and ConvAI2) and newer datasets with richer features including knowledge graphs, empathy signals, and out-of-distribution personas. The authors note strong language and domain biases across datasets — most are English or Chinese, and several are domain-specific rather than truly open-domain. The paper also surveys recent progress by large language models on personalized dialogue tasks and outlines open challenges and directions for future research.
- Towards Real-world Human Behavior Simulation: Benchmarking Large Language Models on Long-horizon, Cross-scenario, Heterogeneous Behavior Traces
Synthesis
Plain-language abstract This paper introduces OmniBehavior, the first benchmark for testing how well large language models can simulate real human behavior across multiple online scenarios over extended time periods. The benchmark is built from actual user interaction logs on Kuaishou, a major video platform, covering 200 users over three months and spanning actions like browsing, purchasing, searching, and conversing across five distinct contexts. The authors use it to evaluate state-of-the-art LLMs and characterize where and why they fail as user simulators.
Motivation Existing benchmarks for LLM-based user simulation are limited to single scenarios, narrow action spaces, or synthetic data. Real human behavior crosses many contexts over long periods — a purchase decision may stem from a video watched days earlier, and a comment in a live stream may reflect a post-purchase experience. These fragmented benchmarks cause systematic misinterpretation of how capable LLMs actually are at modeling authentic human behavior.
Methodology The authors collected real interaction logs from Kuaishou across five scenarios (video browsing, live streaming, advertising, e-commerce, and customer service). They sampled 200 representative users, aggregated their complete interaction traces with timestamps over a three-month period, applied multi-level cleaning and anonymization, and constructed a benchmark with 22 distinct action types and trace lengths from 50 to over 100,000 actions (averaging around 32,000 tokens). They then evaluated both closed-source models (including Claude-4.5-Opus, GPT-5.2, Gemini-3-Flash) and open-source models (including Qwen3-235B, DeepSeek-V3) on a user-conditioned prediction task requiring the model to predict all user behaviors in a given scenario given the user's profile and history.
Results Even the best-performing model, Claude-4.5-Opus, achieved an overall score of only 44.55, and F1 scores on binary behavior prediction tasks (like, share) did not exceed 40% for most models. Extending context windows beyond 32K tokens did not consistently improve performance. Analysis showed that integrating additional scenarios expands interest coverage by approximately 20–30%, and over 80% of conversion paths span multiple scenarios and days. LLMs exhibited three structural biases: hyper-activity (overestimating action probabilities), persona homogenization (simulated users cluster together while real users are distinct), and a Utopian bias (LLMs produce unrealistically positive and polite behavior, failing to simulate dissatisfied or adversarial users).
- A Survey on LLM-based Conversational User Simulation
Synthesis
Plain-language abstract This paper is a survey of research on using large language models (LLMs) to simulate how users behave in conversations. The authors organize a large body of recent work under a new taxonomy, examine the techniques used to build these simulators, and identify open challenges in the field.
Motivation User simulation has long been important for building and evaluating conversational AI systems, but the arrival of LLMs has rapidly expanded what is possible, creating a fragmented literature with no unified framework. A dedicated survey covering conversational user simulation specifically — as distinct from earlier statistical or task-specific approaches — was absent, leaving researchers without a systematic map of the space.
Methodology The authors conducted a systematic literature survey, collecting and categorizing recent work on LLM-based conversational user simulation. They developed a novel taxonomy organized around three questions: who is being simulated (ranging from general users to persona-level, role-playing, and individual users), what interaction pattern is being simulated (Human–AI, Human–Human, AI–AI, and many-human–AI), and how the simulation is technically implemented. Core techniques and evaluation methodologies across these categories are analyzed and compared.
Results The survey maps the field into a unified framework and identifies key research trends across domains including search, recommendation, task-oriented dialogue, education, and human-computer interaction. The authors find that LLM-generated conversational data can directly improve downstream system performance, and that evaluation remains a major open challenge — human judgment is the gold standard but costly, while LLM-as-judge approaches lack reliability for long or complex conversations. Open challenges including limited user feedback signals, persona fidelity, and scalable evaluation are identified and organized.
- Surveying the Effects of Quality, Diversity, and Complexity in Synthetic Data From Large Language Models
Synthesis
Plain-language abstract This paper surveys how the quality, diversity, and complexity of synthetic training data — data generated by large language models — affect the performance of the models trained on that data. The authors introduce a unified framework called QDC (Quality, Diversity, Complexity) to systematically compare and understand the many synthetic data generation methods that have emerged, and to explain why some methods produce better models than others.
Motivation Synthetic data generation with large language models has become common practice, but existing methods are ad hoc and rarely compared directly. Most approaches focus narrowly on maximizing data quality and quantity while discarding the majority of generated samples, without understanding which intrinsic data characteristics actually drive downstream model generalization. This paper addresses the lack of a principled framework for evaluating and designing synthetic data generation algorithms.
Methodology The authors conduct a structured literature survey organized around three research questions: how to define and measure quality, diversity, and complexity in datasets; how each characteristic affects model generalization; and how existing synthetic data generation algorithms promote each characteristic. They taxonomize synthetic data generation methods by the components they use and their effects on the QDC composition of the resulting data, extending the analysis to implications for reinforcement learning and self-improvement algorithms.
Results The survey finds that data quality is essential for in-distribution generalization, data diversity is essential for out-of-distribution generalization, and complexity is beneficial for both. The authors identify Quality-Diversity trade-offs in training data that directly affect downstream model performance. They also observe that most current models are evaluated and optimized only for output quality, which limits output diversity and constrains the potential for iterative self-improvement — arguing that balancing all three characteristics is essential for future self-improving AI systems.
- EngramaBench: Evaluating Long-Term Conversational Memory with Structured Graph Retrieval
Synthesis
Plain-language abstract EngramaBench is a benchmark for testing how well AI assistants remember and reason across information accumulated over many conversations. The paper introduces the benchmark, presents a graph-structured memory system called Engrama, and compares it against two baselines: simply feeding all prior conversation history into the prompt, and a vector-retrieval memory system called Mem0.
Motivation AI assistants are increasingly used as long-term collaborators, but existing benchmarks do not adequately test whether memory systems can integrate information across distinct areas of a user's life, reason about how things change over time, or correctly refuse to answer fabricated questions. There was also no clear answer to when structured memory architectures outperform brute-force context inclusion.
Methodology The benchmark is built around five synthetic personas, each with 20 timestamped multi-session conversations and 30 queries covering five task types: factual recall within a single topic area, cross-domain integration, temporal reasoning, adversarial abstention (refusing fabricated questions), and emergent synthesis. All three evaluated systems—GPT-4o full-context, Engrama, and Mem0—use the same answering model (GPT-4o) so that score differences reflect only the memory architecture. Engrama organizes memory into a graph of entities, semantic spaces, temporal traces, and cross-space links; Mem0 uses flat vector retrieval over extracted memories; full-context prompting concatenates all prior conversations directly into the prompt.
Results GPT-4o full-context achieved the highest overall composite score (0.6186), followed by Engrama (0.5367) and Mem0 (0.4809). However, Engrama was the only system to outperform full-context prompting on cross-space reasoning queries (0.6532 vs. 0.6291, n=30), which are the queries most diagnostic of structured long-term memory. Engrama reached about 87% of GPT-4o's composite score at roughly 20% of the query-time cost ($0.67 vs. $3.33 for 150 queries). Ablations showed that the components giving Engrama its cross-space advantage actually reduce global composite score, revealing a design tension between specialization for cross-domain reasoning and overall optimization.
- UniToolCall: Unifying Tool-Use Representation, Data, and Evaluation for LLM Agents
Synthesis
Plain-language abstract UniToolCall is a unified framework that standardizes how AI language model agents learn to use tools — that is, how they translate plain-language instructions into executable function calls against external APIs and systems. It provides a consistent way to represent tool interactions, a large curated training dataset, and a common evaluation benchmark, so that researchers can train and compare tool-using agents on equal footing.
Motivation Existing research on tool use for language model agents suffers from fragmentation: different projects use incompatible representations for how agents call tools, datasets are constructed inconsistently and ignore the structural variety of real tool-use trajectories, and evaluation benchmarks cannot be directly compared. This lack of standardization makes it hard to measure progress or build on prior work.
Methodology The framework assembles a tool pool of over 22,000 tools and builds a hybrid training corpus of more than 390,000 instances by combining 10 standardized public datasets with synthetically generated trajectories that are structurally controlled to cover single-hop and multi-hop, single-turn and multi-turn, and both serial and parallel execution patterns. An Anchor Linkage mechanism is introduced to enforce cross-turn dependencies for coherent multi-turn reasoning. For evaluation, seven public benchmarks are converted into a unified Query-Action-Observation-Answer (QAOA) representation with fine-grained scoring at the function-call, turn, and conversation levels.
Results Fine-tuning Qwen3-8B on the UniToolCall dataset substantially improves tool-use performance. Under the distractor-heavy Hybrid-20 evaluation setting, UniToolCall achieves 93.0% single-turn Strict Precision, outperforming leading commercial models including GPT, Gemini, and Claude.
- Graph2Counsel: Clinically Grounded Synthetic Counseling Dialogue Generation from Client Psychological Graphs
Synthesis
Plain-language abstract Graph2Counsel is a framework that automatically generates synthetic mental health counseling dialogues by grounding them in Client Psychological Graphs (CPGs) — structured representations of how a patient's thoughts, emotions, and behaviors interact. The system produces 760 multi-turn counseling sessions from 76 graphs derived from real therapy transcripts, and shows that models fine-tuned on this data outperform those trained on comparable existing datasets.
Motivation Large language models need high-quality counseling dialogue data to be safely adapted for mental health support, but real session transcripts are scarce due to strict privacy and confidentiality constraints. Existing synthetic datasets rely on flat text descriptions — demographics, symptom lists, or questionnaire scores — that miss the functional dependencies among a client's cognitive, emotional, and behavioral states, leading to psychologically inconsistent synthetic interactions.
Methodology The framework extracts CPGs and counselor strategies from anonymized real therapy transcripts using a prompt-based LLM pipeline. CPGs are represented as directed edge lists encoding excitatory and inhibitory relationships among psychological processes. These graphs, combined with CPG-derived client profiles and real counselor strategies, are fed to GPT-4o under four prompting conditions: a baseline, Guided Counseling (GC), GC with Chain-of-Thought reasoning, and a two-stage GC with Multi-Agent critique-and-refinement. Generated sessions are evaluated by LLM-as-a-judge using the Cognitive Therapy Rating Scale and Working Alliance Inventory, by four licensed clinician experts, and through downstream fine-tuning of Llama3-8B-Instruct via QLoRA on two counseling benchmarks.
Results In expert evaluation across five dimensions — specificity, counselor competence, authenticity, conversational flow, and safety — Graph2Counsel ranked first on all metrics compared to three prior synthetic dataset baselines (CACTUS, MAGneT, SQPsychConv), with substantial inter-annotator agreement (Krippendorff's alpha = 0.70). Generated client profiles were rated CPG-aligned in 90% of cases and realistic in 97% of cases. Fine-tuning Llama3-8B on Graph2Counsel data (Llama3-G2C) achieved the highest Few-Shot Chain-of-Thought accuracy on CounselingBench (0.631) among all fine-tuned models, and also improved performance on CounselBench.
- VeriSim: A Configurable Framework for Evaluating Medical AI Under Realistic Patient Noise
Synthesis
A configurable simulation framework that injects realistic patient 'noise' (incomplete, inconsistent, distracting user behavior) into evaluation, exposing that strong static-benchmark scores collapse under realistic interaction.
Why it matters A concrete instance of controllable distractor/noise injection in a user simulator for agent eval, plus evidence of the static-benchmark-vs-realistic-interaction gap — the methodological pattern needed for stress-testing memory systems with adversarial/noisy synthetic users.
- Two Tales of Persona in LLMs: A Survey of Role-Playing and Personalization
Synthesis
Plain-language abstract This paper is a comprehensive survey of how the concept of 'persona' is used in large language models (LLMs). It organizes a fast-growing but scattered body of research into two distinct lines: role-playing, where the LLM itself takes on an assigned persona (such as a doctor, engineer, or judge), and personalization, where the LLM adapts its responses based on a user's persona. The authors also cover methods for evaluating LLM personality.
Motivation Research on using personas to tailor LLM behavior had grown rapidly but remained disorganized, lacking a unified framework or systematic taxonomy. The authors identified this gap and set out to produce the first survey that brings role-playing and personalization together under a single conceptual lens.
Methodology The authors conducted a structured literature review, categorizing existing studies into two main streams: LLM Role-Playing (covering environments such as software development, games, medical applications, and LLM-as-evaluator) and LLM Personalization (covering applications such as recommendation, search, education, healthcare, and dialogue). They further analyzed role-playing schemas (single-agent vs. multi-agent) and emergent social behaviors, and reviewed approaches to LLM personality evaluation using frameworks such as the Big Five and MBTI. A continuously maintained paper collection was released alongside the survey.
Results The survey demonstrates that role-playing enables LLMs to perform better in structured, task-oriented environments—including software development pipelines, medical consultation, and automated evaluation—while personalization approaches allow LLMs to tailor responses across domains such as recommendation and healthcare. The paper establishes a systematic taxonomy covering both lines of research and highlights emergent social behaviors (such as conformity and adversarial debate) that arise under multi-agent role-playing schemas. It had received 44 citations as of the time of indexing.
Architectures
Memory architectures beyond the basics: temporal-KG, hierarchical/tree, hypergraph, tiered/OS-style, routing, parametric vs non-parametric, specialized retrieval, and consolidation/forgetting for LLM-agent memory
Key threads
- Structured memory substrates are proliferating along a spectrum - flat text -> typed/semi-structured entries -> pairwise knowledge graphs (Zep/Graphiti) -> hypergraphs (HyperMem) -> hierarchical trees (MemTree, LinkedIn) - and each structure implies different recall failure modes a benchmark must isolate.
- Temporal validity is becoming a first-class memory primitive: edge time-stamping, event tuples, and change-tracking (Zep, APEX-MEM, GRAVITY, dual-trace) shift evaluation from static fact recall toward time-aware reasoning and obsolescence handling.
- Consolidation-vs-forgetting (stability-plasticity) is emerging as an explicit architectural axis (GAM, SCM sleep-consolidation, ZenBrain) yet remains weakly benchmarked - most metrics still reward pure accumulation rather than correct pruning.
- Retrieval for memory is being specialized away from generic embedding RAG toward information-theoretic scoring (Memanto), iterative memory-as-cognition (MemCog), thought retrieval (Thought-Retriever), and OS-style paging (cooperative paging) - implying recall@k is an insufficient harness metric.
- Architecture-agnostic, cross-system comparative evaluation (GRAVITY across 5 systems; GraphRAG-vs-RAG benchmarking) is becoming the credible methodology, replacing single-system self-reports - directly relevant to building an open eval harness.
- Memory-type taxonomy (semantic/episodic/procedural and proposed extra layers like an explicit Knowledge layer or 7-layer schemes) is contested, meaning benchmarks should instrument per-type probes rather than one aggregate recall score.
Open gaps
- Forgetting and obsolescence are rarely scored: SCM and GAM implement forgetting mechanisms but no shared benchmark rewards correct removal of stale/superseded memories - existing metrics (DMR, LongMemEval, LoCoMo) measure accumulation/recall, not principled deletion.
- Hypergraph and n-ary memory (HyperMem) lack standardized multi-entity/multi-participant recall tasks; current benchmarks are built around pairwise or flat facts, so higher-order structure cannot be credited.
- Procedural-memory evaluation is thin: Thought-Retriever and reasoning-reuse systems have no widely adopted task suite measuring reuse of past reasoning/skills across sessions, unlike the relatively mature semantic-recall benchmarks.
- Retrieval-mechanism ablations are under-reported: papers swap in information-theoretic, iterative, or paging retrieval but seldom isolate the retrieval objective from the storage structure, leaving unclear what drives gains - a harness gap an open eval could fill.
- Temporal-reasoning evaluation is fragmented across system-specific reports (Zep, APEX-MEM, GRAVITY) with no shared multi-session temporal/change-tracking benchmark, so cross-architecture temporal claims are not comparable.
- Almost all reported systems show zero citations and self-defined eval splits, indicating no consolidated leaderboard or reproducible harness for memory-architecture comparison - the core opportunity for this work.
- Zep: A Temporal Knowledge Graph Architecture for Agent Memory
Synthesis
Plain-language abstract Zep is a memory layer service for AI agents built on top of a temporally-aware knowledge graph engine called Graphiti. Unlike standard retrieval systems that work with static document collections, Zep continuously ingests conversational and structured business data, maintains a timeline of facts and relationships, and retrieves relevant context for LLM agents at query time.
Motivation Large language models powering chat agents are constrained by their context windows and static training knowledge, and existing retrieval-augmented generation (RAG) approaches work only with fixed document corpora. Enterprise applications require agents that can integrate and reason over continuously evolving data — including ongoing conversations and business records — but no existing memory system addressed this dynamic, temporally-aware requirement at production scale.
Methodology Zep represents memory as a hierarchical knowledge graph with three tiers: an episodic subgraph storing raw messages, a semantic entity subgraph of extracted entities and facts, and a community subgraph of clustered entity groups. New data is ingested by extracting entities and facts via LLM prompts, resolving duplicates, and invalidating outdated edges using a bi-temporal model. Retrieval combines cosine similarity search, BM25 full-text search, and breadth-first graph traversal, followed by reranking. The system was evaluated on the Deep Memory Retrieval (DMR) benchmark (500 multi-session conversations) and the LongMemEval benchmark (conversations averaging 115,000 tokens), using GPT-4o-mini and GPT-4o for generation and BGE-m3 for embeddings and reranking.
Results On the DMR benchmark, Zep achieved 94.8% accuracy with GPT-4-turbo and 98.2% with GPT-4o-mini, compared to MemGPT's 93.4% with GPT-4-turbo. On the more demanding LongMemEval benchmark, Zep improved accuracy by 15.2% with GPT-4o-mini and 18.5% with GPT-4o over full-context baselines, while simultaneously reducing response latency by approximately 90% and compressing average context from 115,000 tokens to 1,600 tokens. The largest accuracy gains appeared in complex question types such as single-session-preference, multi-session, and temporal-reasoning tasks.
- HyperMem: Hypergraph Memory for Long-Term Conversations
Synthesis
Plain-language abstract HyperMem is a memory system for conversational AI agents that need to remember information across long, extended conversations. Rather than storing conversation history as flat text chunks or simple knowledge graphs, it organizes memory into a three-level hierarchy of topics, episodes, and facts, and uses hyperedges to group related memories that may be spread across many exchanges. When answering a question, it searches this structure from coarse to fine, moving from relevant topics down to specific facts.
Motivation Conversational agents lose access to earlier parts of a conversation as it grows beyond their fixed context window, requiring an external memory system. Existing approaches like chunked retrieval and graph-based memory use pairwise relationships, which cannot capture higher-order associations — cases where three or more pieces of information are jointly relevant but scattered across different time points in the dialogue. This fragmentation causes incomplete or incorrect retrieval when questions require multi-hop reasoning across a long history.
Methodology HyperMem structures memory into topics, episodes, and facts. Dialogue streams are segmented into episodes using LLM-driven boundary detection; related episodes are then linked under shared topic nodes via hyperedges; and fine-grained facts are extracted from each episode. A hybrid lexical-semantic index is built using BM25 and dense embeddings propagated through the hypergraph. At query time, retrieval proceeds coarse-to-fine: first identifying relevant topics via combined reciprocal rank fusion and reranking, then expanding to associated episodes, then selecting the most pertinent facts to assemble the response context. The system was evaluated on the LoCoMo long-term conversation benchmark.
Results HyperMem achieves 92.73% LLM-as-a-judge accuracy on the LoCoMo benchmark, reported as state-of-the-art. In an efficiency comparison, the Episode + Fact retrieval configuration reaches this accuracy using roughly 7.5 times the tokens of a Mem0 baseline, while a Fact Only configuration reaches 89.48% at just 2.5 times the tokens — both substantially outperforming graph-based RAG methods such as GraphRAG (67.60% accuracy at 35.3 times token usage) and HyperGraphRAG (86.49% at 26.3 times). Ablation results show that removing topic-level retrieval causes the largest single accuracy drop (3.76 percentage points), and that episode context consistently adds 3–4% over fact-only retrieval.
- From Isolated Conversations to Hierarchical Schemas: Dynamic Tree Memory Representation for LLMs
Synthesis
Plain-language abstract This paper introduces MemTree, a memory management algorithm for large language models (LLMs) that organizes information in a dynamic tree structure, similar to how human cognitive schemas work. Rather than storing each piece of information as a separate, unconnected entry, MemTree groups and links related memories hierarchically so that LLMs can reason more effectively over long conversations and documents.
Motivation Large language models struggle with long-term memory: even as context windows have expanded to millions of tokens, models rely on key-value caches processed through a fixed number of layers, which cannot effectively aggregate extensive historical data. Existing external memory methods store past experiences as isolated entries in flat lookup tables, losing the interconnected, hierarchical structure that makes human memory efficient for retrieval and reasoning.
Methodology MemTree represents memory as a dynamic tree where each node stores aggregated textual content and semantic embeddings at varying levels of abstraction. When new information arrives, the algorithm traverses the tree from the root, computing semantic similarity between the new content and existing nodes; if similarity exceeds a threshold the information is routed to that branch, otherwise a new leaf node is created. This insertion process runs in O(log N) time where N is the number of conversational interactions. The system was evaluated on benchmarks for multi-turn dialogue understanding and document question answering, including the MultiHop dataset.
Results MemTree significantly enhances performance on benchmarks requiring structured memory management, including multi-turn dialogue understanding and document question answering. The system outperforms methods that rely on flat memory lookup tables, and on tasks involving reasoning over event sequences across multiple documents, MemTree exceeds all offline comparison methods. The work was published as a conference paper at ICLR 2025.
- Hierarchical Long-Term Semantic Memory for LinkedIn's Hiring Agent
Synthesis
Plain-language abstract This paper describes HLTM (Hierarchical Long-Term Semantic Memory), a memory system built for LinkedIn's AI recruiting agent (Hiring Assistant) that lets the agent remember and reason over a recruiter's past projects and preferences across many conversations. Instead of stuffing all past activity into a single context window, HLTM organizes information in a tree structure and retrieves only what is needed at low latency, while respecting data-privacy rules. The system is deployed in production at LinkedIn.
Motivation LLM-based agents used in enterprise products need long-term, personalized memory to be useful, but existing memory systems struggle with five practical challenges at industrial scale: ingesting millions of documents efficiently, retrieving answers within tight response-time budgets, enforcing strict data-privacy isolation between tenants, adapting to new query patterns without hand-crafted rules, and providing transparent provenance so the system can be audited and debugged. No prior system addressed all five challenges together for a live enterprise deployment.
Methodology HLTM organizes memory as a schema-aligned tree whose topology mirrors the enterprise data model — for LinkedIn's hiring domain, leaf nodes represent individual hiring projects, intermediate nodes represent recruiter seats, and root nodes represent organizational accounts. Each tree node stores three complementary memory views extracted offline by LLM agents: key-value facet pairs (for structured filtering), answerable question-answer pairs (for fast serving), and natural-language summaries (for unstructured queries). Retrieval at serving time combines hybrid embedding-based search with an in-context-learning answering step, restricted to the subtree that matches the query's access-control scope. A lightweight adaptation loop mines historical query patterns to continuously refine which facts are extracted and stored.
Results On a benchmark derived from LinkedIn's Hiring Assistant dataset, HLTM achieved the best answer correctness (0.798) at a query latency of roughly 3.4 seconds, outperforming all nine baselines including HippoRAG, RAPTOR, GraphRAG, and conventional RAG. On summary-style queries it improved correctness over the strongest baselines by more than 15%; on retrieval-style queries it exceeded the best baseline in F1 by more than 10%. An ablation study showed that removing tree aggregation caused roughly 12-point and 18-point drops in correctness and retrieval F1 respectively, and that removing the adaptation mechanism degraded correctness by about 10 points. HLTM also reduced query-time token usage by at least 50% relative to graph-based baselines.
- GAM: Hierarchical Graph-based Agentic Memory for LLM Agents
Synthesis
Plain-language abstract This paper introduces GAM, a memory system for AI assistants that need to remember things across long conversations. The key idea is to separate the act of recording new information from the act of integrating it into long-term knowledge, which helps the AI stay coherent over time without getting confused by irrelevant details.
Motivation AI language model agents struggle to maintain coherent long-term interactions because existing memory designs force a trade-off: stream-based systems update easily but are disrupted by noise, while structured memory systems retain knowledge well but cannot adapt as conversations evolve. There was no approach that achieved both rapid context awareness and stable long-term retention simultaneously.
Methodology GAM organizes memory into two hierarchical layers: an event progression graph that captures the current dialogue in fine-grained detail, and a topic associative network that holds stable long-term knowledge. New dialogue is held in the event graph and only merged into the topic network when a semantic shift is detected, limiting interference. A graph-guided, multi-factor retrieval strategy is used to pull relevant context at query time. The framework was evaluated on two long-context dialogue benchmarks, LoCoMo and LongDialQA.
Results GAM consistently outperformed state-of-the-art baselines on both LoCoMo and LongDialQA benchmarks in reasoning accuracy and efficiency. The approach demonstrated that explicitly decoupling memory encoding from consolidation reduces interference from transient noise while preserving long-term consistency across extended agent-user dialogues.
- SCM: Sleep-Consolidated Memory with Algorithmic Forgetting for Large Language Models
Synthesis
Plain-language abstract This paper introduces SCM (Sleep-Consolidated Memory), a memory architecture for large language models that mimics how human brains store and forget information. Rather than growing an ever-larger database of raw conversation text, SCM encodes conversations into structured concepts, selectively strengthens important ones during simulated sleep cycles, and actively prunes low-value memories — enabling persistent, organized memory that stays manageable over time.
Motivation Current LLM memory approaches all have critical gaps: context windows are bounded and degrade with long input, vector databases grow without limit and never forget, and tiered storage systems like MemGPT lack any offline consolidation or biological forgetting mechanisms. None replicate how human memory actually works — a dynamic system that consolidates during sleep, prioritizes by importance, and actively prunes weak associations. SCM was designed to fill this gap by bringing neuroscience-inspired memory management to conversational AI.
Methodology SCM is built from five modules: a MeaningEncoder (using a local Llama 3.2 2B quantized model) that converts text into typed semantic concepts with 384-dimensional embeddings; a ValueTagger that assigns four-dimensional importance scores (novelty, emotional valence, task relevance, repetition frequency); a WorkingMemory buffer capped at seven items; a LongTermMemory stored as a NetworkX semantic graph backed by SQLite; and a SleepCycle module that runs NREM consolidation (Hebbian strengthening plus synaptic downscaling), REM dreaming (novel association generation), and value-based forgetting. The prototype was evaluated on a standardized suite of eight benchmark tests covering memory retention, consolidation, forgetting, graph traversal, latency scaling, and multi-session persistence.
Results Across all eight benchmark tests the prototype achieved perfect scores (1.00). It maintained 100% recall accuracy over ten-turn conversations while reducing memory noise by 90.9% through adaptive forgetting — pruning 45 of 50 noise concepts while preserving all 5 important ones. Memory search latency remained below one millisecond with hundreds of stored concepts. An ablation study showed that disabling the ForgettingModule caused the largest memory bloat (72 stored concepts vs. 24 in full SCM) and that disabling the ValueTagger dropped recall to 81.8%, confirming that multi-dimensional importance tagging is the most critical component for selective retention.
- Cooperative Memory Paging with Keyword Bookmarks for Long-Horizon LLM Conversations
Synthesis
Plain-language abstract This paper proposes 'cooperative paging', a method that helps AI chatbots handle very long conversations without losing track of earlier content. When a conversation grows too long to fit in the model's memory, old sections are replaced with short keyword summaries (about 8 tokens each), and the model is given a tool it can call to retrieve the full text of any summarized section when it needs it. The paper evaluates this approach on a standard benchmark of long real-world conversations and also runs a systematic study of design choices like page size and eviction strategy.
Motivation Large language models have a fixed context window, but multi-turn conversations can grow indefinitely. When old content must be discarded to make room, existing methods either force the model to guess what it is missing (which models do poorly), only work for narrow cases like file reads, or compress content irreversibly losing detail. There was no systematic study of how page boundary detection and eviction policy affect retrieval quality in this setting.
Methodology The authors built a cooperative paging system in which evicted conversation segments are replaced with minimal keyword bookmarks (e.g., '[p3: allergy, peanut, budget]') and the model is given a recall() tool to fetch full content on demand. They evaluated it on the LoCoMo benchmark (10 real multi-session conversations with 300+ turns each) across four models from three provider families (GPT-4o-mini, DeepSeek-v3.2, Claude Haiku, GLM5), comparing against five baselines including truncation, BM25 retrieval, and a search-tool baseline. They also ran a turn-by-turn paging simulator with 3,176 probes on synthetic data and 1,600 probes on LoCoMo to ablate five page-boundary strategies and four eviction policies (FIFO, LRU, LFU, Belady oracle), and tested six bookmark generation strategies.
Results Cooperative paging achieved the highest answer quality among six methods on LoCoMo across all four tested models, with statistical significance (p=0.017 vs. BM25, paired bootstrap). The ablation showed page granularity dominates eviction policy: coarse fixed-size pages (fixed-20) reached 96.7% recall accuracy while content-aware topic-shift paging collapsed to 56.7%. The model triggers recall() correctly 96% of the time, but selects the right page only 57% of the time when bookmarks are insufficiently distinctive, shifting the bottleneck from 'when to recall' to 'which page to recall'. The best bookmark strategy (llm-batch, single-call cross-page non-overlap keywords) improved end-to-end accuracy by 8.7 points on LoCoMo and 50 points on open-domain questions over the heuristic baseline; keyword specificity alone accounted for a 25 percentage-point accuracy difference in controlled probes.
- Memanto: Typed Semantic Memory with Information-Theoretic Retrieval for Long-Horizon Agents
Synthesis
Plain-language abstract Memanto is a memory system for AI agents that need to remember information across many conversations and tasks. Instead of the complex graph-based memory architectures most agent frameworks use, Memanto organizes memory into thirteen typed categories and retrieves relevant memories using a single, fast semantic search query — achieving top benchmark scores while being simpler and cheaper to run.
Motivation As AI agents move from answering single questions to carrying out long, multi-step tasks across many sessions, they need reliable persistent memory. Existing production memory systems — such as Mem0, Zep, and A-MEM — combine knowledge graphs with vector databases, which imposes heavy computational costs: every memory write triggers multi-second pipelines involving LLM-driven entity extraction and graph synchronization. The paper argues this 'Memory Tax' is unnecessary and that simpler architectures can match or beat graph-based systems in accuracy.
Methodology Memanto is built on Moorcheh's Information-Theoretic Search engine, a no-indexing semantic database that provides deterministic (exact-match rather than approximate nearest-neighbor) retrieval with sub-90-millisecond latency and zero ingestion delay. The memory layer uses a typed schema of thirteen predefined semantic categories, an automated conflict-resolution mechanism for contradictory memories, and temporal versioning. The system was evaluated on two established long-term memory benchmarks — LongMemEval and LoCoMo — using a five-stage progressive ablation study that isolated the contribution of retrieval-limit tuning, similarity-threshold calibration, prompt design, inference model selection, and the typed schema.
Results Memanto achieved accuracy scores of 89.8% on LongMemEval and 87.1% on LoCoMo, establishing state-of-the-art results among both vector-based and hybrid graph-plus-vector systems. These results were obtained using only a single retrieval query per lookup, with no ingestion cost and no graph infrastructure — outperforming all evaluated hybrid architectures while requiring substantially lower operational complexity.
- The Missing Knowledge Layer in Cognitive Architectures for AI Agents
Synthesis
Plain-language abstract This paper argues that AI agent memory systems make a fundamental design mistake: they treat factual knowledge and personal experience as the same kind of thing, applying the same forgetting rules to both. The author proposes splitting the cognitive substrate of AI agents into four distinct layers — Knowledge, Memory, Wisdom, and Intelligence — each with its own rules for how information persists and gets updated. Companion implementations in Python and Rust are provided to show the separation is practically feasible.
Motivation The two most influential cognitive architecture frameworks for AI agents, CoALA and JEPA, both lack an explicit Knowledge layer with distinct persistence semantics. Existing systems such as Mem0, NornicDB, and Signet apply cognitive decay (time-based forgetting) equally to factual claims and episodic experiences, which the paper identifies as a category error: a scientific finding does not become less true simply because time has passed, yet current architectures treat it as if it does.
Methodology The paper is a conceptual and analytical work. The author surveys persistence semantics across a range of existing agent memory systems, identifies eight convergence points in the literature and practitioner community pointing to the same architectural gap, and analyzes two dominant frameworks (CoALA and JEPA) in detail. From this analysis, a four-layer decomposition is proposed — Knowledge (indefinite, supersession-based), Memory (Ebbinghaus decay), Wisdom (evidence-gated revision), and Intelligence (ephemeral inference-time) — with each layer defined by its persistence semantics, update mechanism, and ownership scope. The terminology is borrowed from cognitive science as analogy, but the layers are framed as engineering constructs.
Results The paper finds that no current framework or system provides the full four-layer decomposition, and that applying decay to factual knowledge produces demonstrably wrong behavior (e.g., the BEAM benchmark shows near-zero contradiction-resolution scores). A survey of April 2026 community work identified multiple independent systems — including rohitg00's LLM Wiki v2, Hermes Agent, Semantica, and MinnsDB — each converging on one or two components of the four-layer thesis without coordinating, suggesting the architectural pattern is emerging across the community. The correct operation for updating factual claims is supersession (recording the relationship between old and new claims), not forgetting.
- ZenBrain: A Neuroscience-Inspired 7-Layer Memory Architecture for Autonomous AI Systems
Synthesis
Plain-language abstract ZenBrain is a memory architecture for AI agents that draws on 130 years of cognitive neuroscience research to give language-model agents a structured, biologically grounded way to store, consolidate, and forget information across many sessions. It organizes memory into seven distinct layers — working, short-term, episodic, semantic, procedural, core, and cross-context — and coordinates them with fifteen neuroscience-inspired algorithms. The system is open-source and ships as composable npm packages with over 11,500 automated tests.
Motivation Current AI agent memory systems borrow metaphors from computer science — virtual memory paging, flat key-value stores, or structured note-taking — but none incorporate the well-validated principles of memory consolidation, forgetting, and reconsolidation studied in cognitive neuroscience for over a century. Without principled decay and consolidation, agents suffer 'conversational amnesia' and cannot maintain consistent personality or learning across sessions. A 2026 survey explicitly identified deeper neuroscience integration as a key open challenge in the field.
Methodology ZenBrain implements seven memory layers orchestrated by nine foundational algorithms plus six new Predictive Memory Architecture (PMA) components, including a four-channel NeuromodulatorEngine modeling dopamine, norepinephrine, serotonin, and acetylcholine dynamics; a prediction-error-gated ReconsolidationEngine; TripleCopyMemory with divergent decay dynamics; and a four-dimensional PriorityMap with an amygdala fast-path. The system was evaluated across ten experiments covering memory lifecycle management, retrieval benchmarks, and system-level ablation studies using three established benchmarks — LoCoMo, MemoryAgentBench, and MemoryArena — under a 15-algorithm ablation protocol with Wilcoxon tests over 10 seeds.
Results Under challenging conditions (decay=0.20, 50 days), 7 of 15 algorithms became individually significant with quality drops ranging from -25.5% to -93.1%; under stress conditions (decay=0.25, 60 days), 9 became critical (up to -93.7% degradation). The Simulation-Selection sleep loop achieved a 37% stability improvement (p < 0.005) with 47.4% storage reduction. TripleCopyMemory retained 0.912 mean memory strength at 30 days versus near-zero Ebbinghaus baselines, and the PriorityMap achieved NDCG@10 = 0.997 versus 0.680 for chronological ordering. On the LongMemEval-500 benchmark, ZenBrain held the highest mean rank across all 12 judge-system quality cells, with a three-judge mean of 0.545 against competitors letta (0.485), a-mem (0.414), and mem0 (0.394), reaching 91.3% of long-context-oracle accuracy at 1/106th the per-query token budget.
- GRAVITY: Architecture-Agnostic Structured Anchoring for Long-Horizon Conversational Memory
Synthesis
Plain-language abstract GRAVITY is a plug-and-play memory module for AI conversational agents that improves how retrieved memories are presented to a language model at response time. Rather than dumping retrieved text fragments into a prompt, GRAVITY reorganizes that information into three structured forms — entity profiles, timestamped event tuples, and cross-session topic summaries — and injects them as explicit context. It works alongside any existing memory system without modifying it.
Motivation Long-horizon conversational agents increasingly rely on sophisticated retrieval systems, but retrieved memory fragments are fed to language models as flat, unstructured text. This forces the model to silently reconstruct which entities relate to each other, how events are ordered, and what themes connect multiple sessions — a reconstruction that fails on multi-hop and temporal questions. Even when retrieval is perfect and all relevant evidence is present, models achieve only about 80.9% accuracy, and this drops to 75.6% when the evidence is mixed with distractors, confirming the problem lies in how context is structured, not whether the right memories were fetched.
Methodology GRAVITY has two phases. During an offline build phase, raw conversation utterances are processed by batched LLM calls to extract three anchor types: entity anchors (dynamic profiles capturing attributes, relationships, and state changes), event anchors (structured subject-verb-object-time-outcome tuples linked into chronological causal traces), and topic anchors (cross-session thematic summaries). At inference time, given a user query, GRAVITY uses embedding-based reranking to select top-K anchors from each type and injects them into the host system's generation prompt as structured context alongside expanded retrieval queries. Integration requires only prompt augmentation — no changes to the host model or memory architecture. The system was evaluated on five diverse memory systems (including A-Mem, Mem0, ZEP, LiCoMemory, and LightMem) using the LongMemEval and LoCoMo benchmarks.
Results Across five host memory systems, GRAVITY improves LLM-judge accuracy by an average of 9.2% on LongMemEval-Micro, 10.1% on LongMemEval-Macro, and 7.5% on LoCoMo. Per-system gains range from 3.8% to 13.1%, with weaker baselines benefiting most (the weakest host improves by 12.2%) while the strongest still gains 3.8–5.7%. A controlled ablation comparing GRAVITY against an unstructured free-form summary injected in the same prompt position shows +5.7% versus +1.3% on LoCoMo, isolating a 4.4-point advantage attributable specifically to the explicit entity-event-topic structure rather than additional LLM-generated text volume. In the scattered-evidence setting, adding anchors recovers 2.9 percentage points without introducing any new evidence.
- MemCog: From Memory-as-Tool to Memory-as-Cognition in Conversational Agents
Synthesis
Plain-language abstract MemCog is a memory system for conversational AI agents that replaces simple keyword lookups with a structured, multi-step reasoning process. Rather than fetching a flat list of stored facts in response to a user query, the system lets the agent navigate through a hierarchically organized memory store—following associative links across topics—and proactively surfaces relevant context even when the user has not explicitly asked for it.
Motivation Existing agent memory systems treat memory as a passive tool: one query goes in and a flat list of text passages comes out, with no further reasoning over results. This design has three compounding weaknesses—memory is only activated when explicitly queried, the retrieval and reasoning steps are disconnected, and retrieved fragments carry no structural cues to guide further exploration. The paper addresses these limitations by rethinking memory access as an integral part of the agent's reasoning loop.
Methodology MemCog has three core components: a Navigable Memory Store that organizes user knowledge in a three-level hierarchy (dimensions, pages, and sections) with cross-dimensional associative links; a Cross-Dimensional Navigation Interface that exposes multi-step browsing actions (Browse, List, Read, Follow Links) so the agent can iteratively explore the store within a ReAct loop; and a Proactive Reasoning Protocol injected via the system prompt that instructs the agent to spontaneously initiate memory exploration when conversational context suggests relevant stored associations. The authors also construct ProactiveMemBench, a new benchmark of 500 test instances across five topic domains built through a six-step LLM-driven pipeline and validated by human annotators at a 98.4% acceptance rate.
Results MemCog achieves state-of-the-art scores on two established passive question-answering benchmarks: 92.98 on LoCoMo and 95.8 on LongMemEval, outperforming prior systems such as HyperMem and A-Mem. On the new ProactiveMemBench, removing the Proactive Reasoning Protocol alone drops Recall@5 from 59.51 to 44.90, confirming that proactive behavioral guidance is the primary driver of spontaneous memory exploration. Ablation studies show that both the navigable memory structure and the proactive protocol are individually necessary and mutually reinforcing, with neither component producing strong proactive performance on its own.
- APEX-MEM: Agentic Semi-Structured Memory with Temporal Reasoning for Long-Term Conversational AI
Synthesis
Plain-language abstract APEX-MEM is a memory framework for AI conversational agents that enables them to accurately remember and reason about information across long, multi-session conversations. It stores conversational knowledge in a structured property graph using an append-only event log, and retrieves relevant facts at query time using a set of complementary tools that combine entity lookup, graph traversal, and hybrid text search.
Motivation Large language models struggle to maintain coherent memory across extended conversations because simply extending context windows introduces noise and hallucinations, while retrieval-based approaches using unstructured text cannot track how facts evolve over time or resolve contradictions between older and newer information. Existing structured memory approaches that use entity-centric graphs are limited in their ability to represent nuanced attributes and temporal changes, and systems that overwrite facts risk losing context needed for temporal reasoning.
Methodology The authors designed APEX-MEM around three key components: a hybrid entity-event ontology that treats conversational events as first-class citizens alongside entities, an append-only event store that anchors facts to temporally grounded events rather than overwriting them, and a multi-tool retrieval framework comprising an entity lookup tool, a SQL-based graph traversal tool for temporal reasoning, and a hybrid semantic-plus-lexical search tool. The system was evaluated on three benchmarks: LOCOMO (long-term multi-session dialogue), LongMemEval (long-context factual reasoning), and SealQA-Hard (search-augmented fact-seeking questions), using LLM-as-a-Judge scoring for answer quality and factuality.
Results APEX-MEM achieved 88.88% accuracy on the LOCOMO question answering benchmark and 86.2% on LongMemEval, outperforming prior state-of-the-art session-aware memory approaches including Mem0, AMEM, Zep, MemGPT, and MemInsight across single-hop, multi-hop, temporal, open-domain, and adversarial question categories. The results demonstrate that structured property graphs with append-only temporal event storage enable more accurate and temporally coherent long-term conversational reasoning than unstructured retrieval or purely entity-centric graph methods.
- Thought-Retriever: Don't Just Retrieve Raw Data, Retrieve Thoughts for Memory-Augmented Agentic Systems
Synthesis
Plain-language abstract Thought-Retriever is a new method for giving AI language model agents a practical long-term memory. Instead of storing and retrieving raw text chunks from a knowledge base, the system stores the intermediate reasoning and responses the model produced while answering past questions — called "thoughts" — and retrieves those when new, related questions arrive. The authors also introduce AcademicEval, a new benchmark that tests whether a model can correctly answer questions drawn from real academic papers requiring very long context.
Motivation Large language models can only work with a limited amount of text at one time, so standard retrieval systems that pull raw text chunks from large knowledge bases often miss relevant information or return too much irrelevant content. Hierarchical retrieval methods that summarize documents independently of user queries improve recall but hurt precision. There was no good way for an LLM agent to accumulate and reuse knowledge across many interactions without hitting these context-length bottlenecks.
Methodology The paper proposes Thought-Retriever, a model-agnostic algorithm in which an LLM collects its own intermediate responses (thoughts) generated while answering prior user queries, filters out meaningless or redundant ones, organizes them in a thought memory store, and retrieves the most relevant thoughts when handling new queries. This creates a self-evolving long-term memory that grows richer as the agent handles more queries. The method is evaluated on the new AcademicEval benchmark — built from real academic papers requiring faithful use of ultra-long context — as well as two additional public datasets, with all retriever-based methods capped at a maximum context length of 2,000 tokens.
Results Thought-Retriever outperforms state-of-the-art retrieval-augmented baselines across all evaluated datasets, achieving an average improvement of at least 7.6% in F1 score and 16% in win rate. The experiments also demonstrate that the system genuinely self-evolves — performance improves as the agent solves more queries — and that it learns to use higher-level, more abstract thoughts to answer more abstract questions.
- Do We Still Need GraphRAG? Benchmarking RAG and GraphRAG for Agentic Search Systems
Synthesis
Plain-language abstract This paper asks whether modern agentic search systems—where a language model dynamically issues multiple retrieval rounds during reasoning—can replace the expensive graph-structured retrieval pipelines known as GraphRAG. To find out, the authors build RAGSearch, a benchmark that tests both standard dense retrieval and five representative GraphRAG methods as retrieval backends under both training-free and reinforcement-learning-based agentic inference, across six question-answering datasets.
Motivation Most comparisons of dense RAG and GraphRAG use inconsistent evaluation protocols, partial test sets, and uncontrolled computational budgets, making it hard to know when the high preprocessing cost of graph construction is truly justified. At the same time, agentic search—where a model iteratively refines queries across multiple retrieval turns—has shown strong gains over one-shot retrieval, raising the question of whether it can substitute for explicit graph structure rather than simply complement it.
Methodology The authors introduce RAGSearch, a unified benchmark that treats dense RAG and five GraphRAG systems (HypergraphRAG, HippoRAG2, LinearRAG, RAPTOR, and GraphRAG) as interchangeable retrieval infrastructures. They evaluate two training-free agentic workflows (Search-o1 and GraphSearch) and two reinforcement-learning-trained agents (Search-R1 and Graph-R1, using GRPO) over six QA benchmarks spanning single-hop and multi-hop tasks (NQ, PopQA, TriviaQA, HotpotQA, Musique, 2WikiMultiHopQA), with matched retrieval budgets, standardized LLM backbones (Qwen2.5 at 3B, 7B, and 32B scales), and full test-set evaluation. Beyond accuracy they measure offline preprocessing cost, online inference efficiency, and output stability.
Results Agentic search substantially narrows the performance gap between dense RAG and GraphRAG, particularly in RL-based settings, but does not eliminate it. GraphRAG consistently achieves stronger and more stable performance on complex multi-hop reasoning tasks, with lower variance in answer quality across retrieval turns. Scaling the LLM backbone reduces the GraphRAG advantage: in RL-based systems, moving from 3B to 7B parameters cuts the average GraphRAG–Dense gap from 14.70 to 9.75 points. GRPO is the most effective RL training paradigm across both retrieval backends. The findings indicate that agentic search redistributes where structure emerges—shifting some from offline graph construction to online interaction—but explicit graph-based retrieval remains valuable when its offline cost can be amortized.
- Mem0: Building Production-Ready AI Agents with Scalable Long-Term Memory
Synthesis
Plain-language abstract Mem0 is a memory architecture for AI agents that lets them remember and reuse information across separate conversations, instead of forgetting everything once a session ends. The system dynamically extracts key facts from ongoing dialogues, stores them compactly, and retrieves only the most relevant ones when answering a new question. A graph-enhanced variant also tracks relationships between entities for more complex multi-hop reasoning.
Motivation Large language models reset their knowledge at the end of every context window, so they cannot maintain consistent user preferences or prior context across multiple sessions. Longer context windows only delay this problem: even 200K-token windows eventually fill up, attention degrades over distant tokens, and forcing the model to process an entire conversation history for every query is slow and expensive. There was no production-ready system that could selectively persist, consolidate, and retrieve salient facts at scale.
Methodology The authors built Mem0 around two phases: an extraction phase that processes each new message pair alongside a rolling conversation summary and recent message window to identify salient facts, and an update phase that compares newly extracted memories against similar stored ones and applies add, update, or delete operations via a tool-call mechanism. A graph-enhanced variant stores memories as directed labeled graphs with entities as nodes and relationships as edges. Both approaches were evaluated on the LOCOMO long-term conversation benchmark against six baseline categories including RAG with varying chunk sizes and k-values, a full-context baseline (26,000 tokens per query), open-source memory tools, and proprietary systems.
Results Mem0 outperformed all memory-augmented baselines across single-hop, temporal, multi-hop, and open-domain question categories on LOCOMO. Mem0 scored approximately 67% on the LLM-as-a-Judge metric, a 26% relative improvement over the OpenAI baseline and about a 10% relative gain over the best RAG configuration. The graph-enhanced variant reached 68.44%, roughly 2% higher than base Mem0. Compared to the full-context approach (which scored ~73% but at high cost), Mem0 achieved 91% lower p95 latency (1.44 s vs. 17.1 s) and used more than 90% fewer tokens, storing each conversation in approximately 7,000 tokens versus the 26,000-token full-context baseline.
- Position: Episodic Memory is the Missing Piece for Long-Term LLM Agents
Synthesis
Position paper directly on the review's thesis.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- AriGraph: Learning Knowledge Graph World Models with Episodic Memory for LLM Agents
Synthesis
KG world model + episodic memory architecture.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- Engram: A Bi-Temporal Memory Engine Where a Lean Retrieved Context Beats the Full History
Synthesis
Plain-language abstract Engram is an open-source long-term memory engine for LLM agents. Instead of replaying an entire conversation history into the prompt, it stores the past as a bi-temporal knowledge graph and retrieves a small, precisely-targeted slice at answer time. On a standard 500-question memory benchmark that lean ~9.6k-token slice answers more accurately than feeding the model the full ~79k-token history, turning memory from a cost optimization into an accuracy improvement.
Motivation Stateless LLM agents forget across sessions, and the usual fix — concatenating the whole history — grows token cost and latency linearly and loses accuracy as distractors crowd the window ('lost in the middle'). Two gaps stay open: most memory systems are cheaper or faster but not more accurate than full-context, and memory benchmarks run on inconsistent harnesses where one system reports wildly different scores across sources. Engram targets both — beating full-context on accuracy, and shipping a neutral, re-runnable harness.
Methodology A dual-process design. A System-1 hot write path appends lossless episodes with no LLM (sub-50ms) and enqueues them. A System-2 async path extracts atomic (subject,predicate,object) facts, builds a bi-temporal knowledge graph (valid time vs transaction time on every fact and edge), detects conflicts, and resolves them cheap-then-escalate: exact slot match, embedding similarity, and content subsumption handle the common case with no LLM call, invalidating (never deleting) a superseded fact and recording a supersedes chain and provenance, with only ambiguous cases escalated to an LLM adjudicator. The hybrid read path retrieves through four channels (dense, BM25, graph n-hop, recency/salience), fuses them with Reciprocal Rank Fusion, applies an 'as-of' temporal filter and an abstention gate, and assembles a deduplicated, provenance-tagged, token-budgeted context of facts plus raw chunks.
Results On the full 500-question LongMemEval_S under the official category-specific judge, Engram's lean configuration scores 83.6% vs 73.2% for full-context (+10.4 points, McNemar exact p<10^-6) at ~8x fewer tokens (9.6k vs 79k), 0/500 errored. The gain is load-bearing on the read path being hybrid: facts alone lose recall, while facts plus retrieved chunks recover detail. Bi-temporal modeling pays off most on knowledge-update (87.5%) and temporal (81.1%) categories, while multi-session aggregation and preference remain headroom. The paper documents measurement-integrity pitfalls (truncation, home-grown judges, full-history leaks) and ships a neutral in-repo harness with the official judge baked in and raw per-question logs, every number reproducible by command.
- Infini Memory: Maintainable Topic Documents for Long-Term LLM Agent Memory
Synthesis
Plain-language abstract Infini Memory is a long-term memory architecture for LLM agents that stores memory as a library of plain-text 'topic documents' rather than vectors or a knowledge graph. Each document gathers related evidence under a subject and is maintained over time by splitting, merging, and rewriting. At answer time the agent reads memory through iterative tool calls, expanding context around matches instead of taking a single retrieval shot.
Motivation External memory systems that store observations as isolated records, summaries, or indexed fragments hit four recurring failure modes: fragmentation (evidence about one subject scattered across records), conflict (old and new versions of a fact coexisting), compression loss (summaries dropping temporal and source cues), and insufficient retrieval (single-shot top-k returning fragments without enough local context for multi-hop reasoning). Infini Memory reframes persistent memory as a lifecycle maintenance problem — write, maintain, read — and aims for an inspectable, editable state without a mandatory vector or graph backend.
Methodology Memory is a library of topic documents, each a maintenance scope with a summary, body, and entry-level metadata signatures (<seq,time,source>) that preserve order and provenance as content is rewritten. Writes are decoupled from structure: new candidates append to a buffer document, then periodic consolidation rewrites, splits, updates, and merges them into coherent topic documents. Retrieval can run over plaintext via lexical indexing rather than embeddings. At inference an agentic read procedure lets the LLM iteratively choose memory tools, inspect intermediate results, expand local context, and assemble evidence before answering.
Results On MemoryAgentBench the agentic-retrieval variant scores 64.7% overall and 81.2% on Accurate Retrieval, with gains on Factual Recall, Test-Time Learning, and Selective Forgetting. Ablations on LongMemEval_S isolate two complementary sources: holding the hybrid reader fixed, removing structural split-and-merge maintenance drops accuracy 76.0%->69.3% (-6.7, concentrated on knowledge-update and multi-session questions), while upgrading the reader from hybrid to agentic adds 3.3 points (76.0->79.3) — so maintenance matters more than the retrieval upgrade and neither is sufficient alone. A split-threshold sweep shows over-fragmentation is recoverable, but oversized documents that mix subtopics are costly.
- GitOfThoughts: Version-Controlled Reasoning and Agent Memory You Can Replay, Diff, and Merge
Synthesis
Plain-language abstract GitOfThoughts stores an LLM agent's reasoning tree as a git repository — every scored thought is a commit, scores are git notes, validation outcomes are tags, and retrieval is git log over the agent's own history — which makes reasoning replayable, auditable, diffable, and mergeable across agents. The paper then asks the harder question of whether memory, in any substrate, actually improves accuracy, and runs a pre-registered comparison of five substrates (none, markdown, vector, graph, git).
Motivation Reasoning is the last unversioned software process: chains of thought expire with the context window, pruned search branches leave no record, and memory buffers cannot be diffed, merged, or audited. The authors argue this ephemerality is a structural blocker — it prevents reproducibility ('what did the agent think at step 17?'), audit (detecting train–test leakage or gold-answer memorization), memory transfer between agents, and incident review. Code, infrastructure, datasets, and experiments are all version-controlled; reasoning is the remaining outlier.
Methodology A reasoning tree shares git's structural invariants, so the paper maps it one-to-one onto git primitives (node = commit, refinement = parent edge, score = note, outcome = tag, session vs. cross-session = branch, retrieval = git log --grep / -S). A pluggable MemoryBackend routes every read/write through one interface so the same agent can swap substrate with a one-line change. To isolate retrieval from write-path noise, all five backends ingest identical answer-free lessons, then solve held-out, domain-stratified problems read-only; benchmarks are GPQA-Diamond and MATH-500, scored with paired-bootstrap CIs, across two backbones and pre-registered replications, with a similarity sweep to locate when retrieval helps.
Results H-substrate is supported: git delivers auditability, line-level diffs over reasoning text, deterministic replay by SHA, and mergeable memory at accuracy parity, costing ~15 ms/write and ~48 ms/read. H-memory is rejected: across two benchmarks, two backbones, and up to n=500, no substrate reliably improves accuracy on novel problems, and a +15 pp git trend at n=40 collapsed under its pre-registered replication. Memory pays only above a 'copyability threshold' — a near-duplicate retrieved case (cosine ≳ 0.8) lifts accuracy +12 to +13.5 pp, and a 4.5× larger model steepens that step to +22.5–28.5 pp but still extracts no transferable method; the only general accuracy lever is test-time sampling (self-consistency, +3.4 pp at n=500). The authors deliberately document a measurement bug, a retracted result, and a refuted hypothesis as the evaluation standard.
- T-Mem: Memory That Anticipates, Not Archives
Synthesis
Plain-language abstract T-Mem is a long-term conversational-memory architecture for LLM agents that aims to make every stored memory reachable two ways: by surface similarity (descriptive recall) and by latent semantic/causal link (associative recall). It precomputes, at write time, four families of retrieval cues ('triggers'), one per quadrant of a granularity (item vs scene) x orientation (descriptive vs associative) design space, and retrieves via a topic -> scene -> item cascade fused with RRF over lexical and dense indices. It reaches state-of-the-art on LoCoMo (80.26%) and LoCoMo-Plus (74.81%).
Motivation Existing LLM memory systems (flat RAG, graph/temporal-KG, hierarchical, OS-style) all retrieve by projecting query and memory into one similarity space and taking top-K, so they are reachability-bounded by lexical/dense similarity. In long-running dialogue users rarely re-raise old topics with the same wording; they revisit them through indirect situational cues, so the target's surface form has drifted and can never be reached from the same neighbourhood. This associative half of the query-memory relation is a structural blind spot.
Methodology M is a typed tuple of scenes, items, topic labels, four trigger families, and per-speaker Persona, built by a load-bearing four-stage offline pipeline: event-closure scene segmentation, incremental data-grown topic labelling, dual-granularity item extraction (atomic + connected, one LLM call per topic), and trigger instantiation (Entity+Bridge jointly per item; Scene+Horizon per scene). Memory-construction LLM is GPT-4.1-mini, dense encoder bge-m3. Retrieval is a top-down topic -> scene -> item cascade scored by RRF over BM25 + per-type dense rankings; multi-view trigger indices surface host nodes via nan-aware max cosine, and associative triggers bypass the topic prefilter so cues outside the similarity neighbourhood still hit. Triggers stay off the QA evidence path; Persona is ambient context appended after retrieval.
Results On LoCoMo, T-Mem reaches 80.26% LLM-as-judge accuracy (51.96 token-F1), 3.25 pp above the strongest baseline HyperMem and the maximum on five of six columns. On LoCoMo-Plus it scores 74.81%, narrowing the LoCoMo-to-LoCoMo-Plus drop to 5.45 pp, about 5x tighter than HyperMem (28.38 pp) and near an order of magnitude tighter than the Mem0/SeCom/A-Mem cluster (~49 pp). Ablations confirm the scene-level associative triggers drive the associative gain: removing Scene+Horizon collapses LoCoMo-Plus by 22.19 pp (Horizon alone -12.47 pp) while moving LoCoMo by under 0.4 pp. T-Mem also reaches higher accuracy than HyperMem at a lower input-token budget.
- Memory Depth, Not Memory Access: Selective Parametric Consolidation for Long-Running Language Agents
Synthesis
Plain-language abstract Long-running language agents accumulate more history than fits in working context, and the usual fix is retrieval — store past events outside the model and fetch a relevant subset at query time. This paper argues retrieval only answers what can be fetched (memory access) and not what should keep shaping behavior after the working context is unloaded (memory depth). It introduces the loop-drift protocol, a controlled stress test where the retrieval index stays intact but working context is cleared, so goal-conditioned behavior must persist through long-loop interference without the relevant text being reinserted. It evaluates EVAF, a surprise- and valence-gated LoRA consolidation mechanism that writes only behavior-relevant events into a small adapter. Across GPT-2, TinyLlama, and Mistral-7B, retrieval wins shallow factual recall while EVAF wins goal persistence and post-unload recovery with only 2–3 parametric writes per 200 events, and the paper shows selective consolidation factorizes into two separable controls — selection and actuation.
Motivation Memory access and memory depth are different problems. A shallow memory is one the system can retrieve or attend to; a deep memory changes future behavior — it persists through interference, survives context unload, and affects choices without being reinserted as text. Retrieval is indispensable for fetched facts, but a long-running assistant also needs durable goals, preferences, and constraints that are not merely fetched facts. Existing long-memory benchmarks (LongMemEval, LoCoMo) emphasize conversational recall, temporal access, and knowledge updates, and do not isolate the post-unload setting where retrieval remains available but behavior must continue without the relevant text in context. The paper's claim is narrow and explicit: memory depth can be probed by post-unload goal-conditioned behavior, and consolidation factorizes into selection and actuation — it does not claim universal memory accuracy, SOTA retrieval, or complete deletion/update validity.
Methodology Loop-drift protocol: synthetic per-user streams of 200 events (10 users/run) mixing stable goal/preference reminders, off-topic distractors, transient opposite requests, conflicts, sibling-user contamination, and scheduled factual notes; four probe layers — shallow episodic (recent fact), noisy episodic (old fact after same-key interference), parametric tendency (does a stable goal still shape behavior after long interference), and post-unload recovery (re-probe the goal immediately after a context unload, with the retrieval index intact but working context cleared). The RAG baseline stores all events in a durable embedding index (top-3 cosine) that context unload does not clear, so any EVAF goal-layer advantage is not a trivial 'RAG forgot' artifact. EVAF mechanism: per-event surprise (token negative log-likelihood) and valence (embedding similarity to the user's durable goal/preferences) combine into an admission gate; events above threshold enter a buffer, and when the buffer fills a LoRA adapter is updated on the buffer plus replay from prior consolidated events, with an L2 anchor as a drift guard. Model controls: GPT-2 and TinyLlama (four-seed means) plus Mistral-7B. Selection is isolated with a matched-random gate (same write count and online write dynamics, random admitted events). Actuation is isolated with fixed-inner controllers (fixed-1/2/3 inner LoRA steps using the same gate). A routed EVAF+RAG variant routes factual probes to retrieval and goal probes to EVAF. Public Memora event streams serve as an external boundary diagnostic for stale-memory invalidation, tested with McNemar's test.
Results Depth flip: RAG is strongest on recent explicit facts (short-fact accuracy 0.956–0.973) and near-useless on goals; EVAF is near chance on short facts but much stronger on the goal layer — on GPT-2 EVAF reaches 0.904 goal / 0.900 post-unload vs RAG 0.398/0.394, and on TinyLlama 0.833/0.812 vs RAG 0.396/0.394 — at only 2.4–2.6 writes (L2 drift ~21–29) vs RAG's 0 writes. Writing everything is not enough: Naive-LoRA writes all 200 events at far higher drift (~67 TinyLlama, ~119 GPT-2) and still fails the goal layer; at 7B indiscriminate writing is actively harmful — Naive-LoRA goal persistence collapses to 0.333±0.047, below the 0.500 chance baseline. Selection is not sparsity: on GPT-2 EVAF beats a matched-random gate of equal write count on goal and post-unload in all four seeds (mean 0.790/0.763 vs 0.590/0.619); TinyLlama is weak/mixed, so the selection signal is not monotonic in model scale. Actuation is a separable, model-dependent factor: fixed-inner audits show smaller inner steps cut drift and improve goal/post (Mistral-7B five-step 0.354/0.306 -> Fixed-2 0.796/0.775 -> Fixed-1 0.919/0.938), but Fixed-1 contamination saturates at 1.000 on Mistral, so high actuation trades selectivity for goal strength. Asymmetric coupling: under a miscalibrated five-step actuation at 7B the matched-gate comparison reverses, yet EVAF still keeps lowest sibling contamination (0.787±0.041) — selection stays semantically active while its translation into goal behavior fails. Boundary: on Memora, EVAF improves forgetting-absence only 91/222 to 95/222 (p=0.57, not significant), so append-only selective consolidation does not solve stale-memory delete/update validity, which the paper leaves to validity-gating or reconsolidation.
- Temporal Validity in Retrieval Memory: Eliminating Stale-Fact Errors for AI Agents over Evolving Knowledge
Synthesis
Plain-language abstract MemStrata is a memory system for AI agents that keeps track of when facts become outdated. Instead of just retrieving whatever text looks most similar to a query, which fails when an old and a new fact look nearly identical, it uses a deterministic rule to detect when a new fact supersedes an old one and retires the stale version.
Motivation Retrieval-augmented memory has no concept of time: when a fact changes (a renamed function, an updated config value, a new port number), both the old and new versions sit in the store with near-identical embeddings, and the agent can't tell which is current. The authors show this isn't a tuning problem: on a calibrated dataset, cosine similarity separates contradictions from duplicates at only 0.59 AUROC (near chance), because a value-flip edit sits textually closer to the original than a genuine rephrasing does.
Methodology MemStrata's write path first tries a deterministic (subject, relation, object) triple match: if an incoming fact shares a key with a stored one but asserts a different value, the old fact is retired (not deleted) in a bi-temporal ledger and the new one is stored as current. Non-triple prose falls back to a similarity-plus-LLM-judge gate. The system is evaluated on six local, deterministic benchmarks (two static, four marker-free evolving: code mutation, config migration, dependency bumps, API evolution) with a 7B model on consumer hardware.
Results MemStrata matches RAG on static recall (no cost) and reaches 0.95-1.00 accuracy on evolving-knowledge benchmarks where RAG reaches only 0.20-0.47. When forced to answer, plain RAG serves the superseded value 15-40% of the time; MemStrata drives this to ~0%. It also runs at ~2.1s retrieval latency versus ~16-18s for LLM-reranking/verification baselines, since no LLM sits on the read path.
- Ontology-Grounded Project Memory for Coding Agents
Synthesis
Plain-language abstract MOOSEDev gives coding agents ontology-grounded, typed project memory (decisions, constraints, rationales, lessons) in a small knowledge graph rather than flat notes or vector chunks, and shows it dramatically outperforms a production vector-memory tool on questions requiring completeness, negation, or supersession reasoning.
Motivation Coding agents generate most new code in many projects today, but the reasoning behind why changes were made is easy to lose track of; notes files and vector-based retrieval-augmented memory help but don't know what kind of record something is (a decision vs. a lesson vs. an outdated, superseded note) or how records relate to each other, which is fundamentally an ontological modeling problem, not a retrieval problem.
Methodology Two small OWL ontologies (9 and 11 classes) with SHACL-validated typed records, reasoned over by a neurosymbolic engine (MOOSE) that treats the LLM as a narrow, declared-point sensor rather than the primary reasoner, exposed to agents via MCP. Evaluated head-to-head against a production vector-memory tool (mem0) and a BM25 baseline on a neutral 835-record public corpus, using a pre-registered strict LLM judge, plus a live trial bootstrapped from the authors' own repository history.
Results On tasks requiring set-completeness, negation (absence), and supersession-traversal reasoning, MOOSEDev scored 0.98-1.00 versus 6-27% for the vector-memory baseline — a categorical, not incremental, gap. On simple relevance retrieval the two systems tied. In a live trial, the system provided 71 unprompted, relevant assists over the first three weeks against 38 misses, with most misses traced to a thinly-bootstrapped project.
- Can Agent Memory Systems Track Evolving State?
Synthesis
Plain-language abstract A benchmark and method for a memory capability separate from recall: keeping track of which version of a fact is currently in force after it has been revised across sessions. The benchmark, StateMemBench, generates each scenario as a symbolic program of state operations so the correct answer is computed by replay and the specific way a lazy reader would get it wrong is known in advance. The method, StateMem, parses each turn into structured state units with typed dependency links, then handles supersession and staleness deterministically rather than with an LLM.
Motivation Existing memory systems and benchmarks optimize recall of relevant facts, but as agents run longer, facts, constraints and decisions get revised, and an answer must reflect the current state rather than a superseded one. The authors call the failure state drift: the relevant fact is present in the assembled context, but the agent acts on a stale or incomplete version of it. This is distinct from dialogue state tracking, which prescribes a slot-value representation and evaluates it directly over cooperative dialogues that accumulate a goal monotonically; here state is whatever a system must maintain to answer correctly, evaluation is purely behavioral, and revisions are adversarial across sessions. Some concurrent work centers state, but the authors argue none cleanly isolates state tracking from the other errors it co-occurs with.
Methodology The authors first define and label drift on existing benchmarks, assigning a failure to drift only after excluding retrieval, comprehension, schema and reasoning readings, dropping unassignable points, and cross-checking with two judge passes, a cross-family judge and two human annotators. They then build StateMemBench: each scenario is a symbolic event program of typed operations over ground, derived and declared state; the gold answer comes from deterministic replay; a family of executable lazy reader policies is run against the replay, and a scenario is admitted as a trap when policies disagree, with the disagreeing set forming its failure-mode signature (status, salience, sequence, compound, plus anti-trap controls). Programs are grounded in public data for surface vocabulary and rendered into multi-session dialogue by a strong LLM, then programmatically verified for fact placement and phrase leakage. Probes are closed-pool: an unseen pool of three to four options holds the gold answer, the targeted policy's drift answer and neutral distractors. StateMem itself runs a per-turn TurnEncoder producing state units (id, content, priority, source, deps), a deterministic update stage applying supersessions and marking dependents needs_recheck by dependency-graph traversal, and a single answer-time call over the assembled active state. A wrapper variant applies the same trace-then-resolve structure as a prompt-level transformation of any backend's answer call, evaluated against a length- and cost-matched generic-extraction control.
Results Drift leads the confirmed failure distribution on several existing benchmarks (63.5% on MemoryArena-shopping, 44.4% on LongMemEval oracle where retrieval is perfect by construction, 10 of 16 on tau-squared-bench-Z) but is not universal, falling to 19.0% on MemoryArena-travel. On StateMemBench, long-context is not the strong baseline it is on recall tasks: the best long-context model reaches 0.277 and same-backbone long-context 0.149. StateMem reaches 0.363 on DeepSeek-V4-Flash, 1.8x the best memory system and 2.4x same-backbone long-context, and 0.233 on Qwen-3.5-9B, 1.6x the best memory system, both significant by paired McNemar at p < 0.001; GraphRAG at 0.224 is statistically level on Qwen. Ablations put supersession marking as the largest single component and show dependency propagation over-fires on Set B anti-traps by 12.5 points, so removing it leaves DeepSeek slightly better. Drift-rate analysis shows the memory layer barely changes outcomes on a weak answerer, where every arm drifts at 61 to 66%, and separates on the stronger backbone, where StateMem's drift rate falls 15 points and correct answers rise by 42 while long-context, Mem0 and BM25 move by 1 to 3 points. The wrapper improves every one of six backends on both benchmarks, adding 31.7 to 66.6 points on StateMemBench with 15.0 to 31.7 attributable to state structure over the matched control, significant in all twelve cells. State tracking does not cost recall: StateMem also leads memory systems on LongMemEval (0.656 on DeepSeek) and LoCoMo (0.592), with margins concentrated on temporal-reasoning and knowledge-update question types. The authors note StateMem mirrors the policy family behind the traps, so its StateMemBench margins should be read as an upper bound.
Security & Governance
Memory Security, Privacy & Governance for LLM Agents (memory poisoning, indirect prompt injection into persistent stores, adversarial robustness, privacy-preserving memory, access control, auditing/provenance)
Key threads
- Trigger-optimized poisoning of the retrieval substrate (memory or RAG KB) is the dominant attack pattern — measured with a shared RSR@k / ASR / Benign-Accuracy triad — and is migrating from flat vector stores to graph-structured and cross-session shared memory.
- Persistence is the new attack surface: cross-session state and shared/multi-user memory enable contamination, worming, and unintended drift that stateless-LLM threat models do not capture, demanding multi-session-trajectory evaluation.
- Defenses are consolidating around provenance/lineage tagging and post-hoc audit graphs (MemLineage, Agent-BOM, StateGuard write-back auditing) rather than input filtering alone, giving harnesses a memory-metadata schema to attack and score against.
- Privacy evaluation is shifting from data-leakage-at-answer to contextual-integrity-in-action — measuring whether agents disclose confidential memory while taking actions over realistic trajectories (PrivacyLens pattern).
- Synthetic seed-to-trajectory data generation (PrivacyLens, When Routine Chats Turn Toxic) is becoming the standard pipeline for producing privacy/poisoning benchmark cases at scale, often paired with a small real-seed validation set.
- Availability/refusal attacks (RAG jamming, blocker documents) are a recognized but under-evaluated failure mode distinct from integrity poisoning, requiring over-refusal as a measured outcome.
Open gaps
- No standardized, open memory-security harness with shared metrics across attack families: poisoning ASR, induced over-refusal/jamming rate, cross-user leakage, and provenance-violation detection are each measured in bespoke per-paper setups.
- Defenses (MemLineage lineage enforcement, Agent-BOM auditing, StateGuard) are reported on their own attacks; there is little head-to-head benchmarking of detection/enforcement defenses against a common, adaptive poisoning suite.
- Episodic/procedural memory security is largely unaddressed — almost all attacks target semantic/retrieval memory; poisoning of stored procedures, skills, or episodic trajectories (cf. BadSkill) lacks dedicated benchmarks.
- Privacy and poisoning are evaluated separately; few benchmarks jointly test access-control/contextual-integrity violations and integrity poisoning within the same multi-session deployed-agent trajectory.
- Edge-cloud / federated memory governance is essentially untouched in this corpus — no benchmark models access control, leakage, or poisoning across a split on-device/cloud memory boundary despite on-device-LLM momentum.
- AgentPoison: Red-teaming LLM Agents via Poisoning Memory or Knowledge Bases
Synthesis
Plain-language abstract This paper introduces AgentPoison, a method for attacking AI agents that rely on external memory or knowledge bases to answer questions and take actions. By inserting a small number of specially crafted malicious examples into an agent's memory, an attacker can reliably steer the agent into harmful behavior whenever a hidden trigger phrase appears in user input — while the agent behaves normally the rest of the time.
Motivation Large language model agents increasingly use retrieval-augmented generation, pulling past examples or knowledge from an external store to guide their decisions. This creates a new attack surface: existing threats like jailbreaking or backdoor attacks were designed for standalone models and do not reliably cause malicious examples to be retrieved from a diverse knowledge base, leaving this vulnerability largely unexplored.
Methodology AgentPoison poisons an agent's memory or RAG knowledge base with a very small number of malicious demonstrations, each pairing a user query containing an optimized trigger with a prescribed harmful action. The trigger is crafted through iterative gradient-guided discrete optimization that maps trigger-containing queries into a compact, unique region of the embedding space, maximizing the chance that poisoned examples are retrieved while keeping the trigger coherent and stealthy. The attack was evaluated on three real-world agent types: an autonomous driving agent, a knowledge-intensive question-answering agent, and a healthcare EHR agent.
Results AgentPoison achieved an average attack success rate of 80% or higher across all three agent types, with a poison rate below 0.1% of the knowledge base and a degradation in normal benign performance of 1% or less. The optimized trigger also showed strong transferability across different LLM backbones without requiring model training or fine-tuning.
- Hijacking Agent Memory: Stealthy Trojan Attacks Through Conversational Interaction
Synthesis
Plain-language abstract This paper presents MemPoison, an attack method that lets an adversary secretly implant backdoors into the long-term memory of an AI agent simply by chatting with it. When a specific trigger phrase later appears in a conversation, the poisoned memory causes the agent to give misleading or malicious responses, while the attack remains hidden from standard defenses.
Motivation AI agents that use long-term memory to remember past interactions are increasingly common, but their memory systems create a new security weak point. Prior work on memory poisoning assumed injected content would be stored as-is, ignoring the fact that modern memory pipelines selectively extract and rewrite what gets remembered — making older attacks ineffective in realistic deployments.
Methodology MemPoison combines three technical components to survive the selective memory pipeline: a semantic relational bridge that binds a trigger and a malicious payload into a single coherent statement so both are extracted into memory together; entity masquerading that optimizes the trigger to resemble named entities, making it resistant to the rewriting step; and joint embedding optimization that clusters trigger-injected texts tightly in the embedding space while keeping them isolated from normal content for stealth. The attack is delivered through ordinary dialogue interactions rather than direct memory writes.
Results Evaluated across multiple agent application domains and memory mechanisms, MemPoison achieved attack success rates of up to 0.95, outperforming existing baseline attacks. Mechanistic analysis showed the attack works by exploiting embedding-space anisotropy and shifting the agent's attention patterns. Multiple evaluated defense strategies were found to have fundamental limitations and could not fully mitigate the attack.
- When Routine Chats Turn Toxic: Unintended Long-Term State Poisoning in Personalized Agents
Synthesis
Plain-language abstract This paper identifies and studies a security vulnerability in AI assistants that remember things about you over time: normal, everyday conversations can gradually corrupt an agent's stored state, quietly loosening the safety guardrails that govern what the agent is allowed to do on your behalf. The authors build a benchmark to measure the problem and propose a lightweight defense to catch and roll back dangerous memory updates before they take hold.
Motivation Personalized LLM agents maintain persistent cross-session memory so they can act as long-term collaborators, but that same persistence creates a new attack surface. Prior security research focused on explicit adversarial injections; this paper asks whether ordinary, benign-looking interactions can accumulate over time to shift an agent's stored defaults in harmful directions — weakening confirmation requirements, expanding tool-use permissions, or increasing autonomous behavior — without any explicit attacker.
Methodology The authors introduce ULSPB (Unintended Long-Term State Poisoning Bench), a bilingual (English and Chinese) benchmark of 350 conversation settings spanning five assistance categories and seven interaction patterns, each instantiated as a 24-turn simulated routine conversation, with matched 25-turn single-injection variants for comparison. They define the Harm Score (HS), a deterministic diff-level metric that scores three dimensions of state drift — authorization drift, tool-use escalation, and unchecked autonomy — weighted by the sensitivity of the affected state component. Experiments run on the OpenClaw personalized agent framework with four backbone LLMs. The proposed defense, StateGuard, audits state diffs at the writeback boundary and selectively rolls back dangerous edits; it is evaluated in single-auditor and majority-vote ensemble configurations and compared against a perplexity-based baseline.
Results Routine conversations alone induced substantial long-term state drift across all four backbone models, not just explicit single-injection attacks, with poisoning primarily occurring in memory-centric artifacts such as MEMORY.md. StateGuard reduced HS to near zero across all models: the Targeted-Ensemble configuration achieved HS scores of 0.06, 0.05, 0.14, and 0.03 on the four tested models, compared to baseline scores above 4.0 for the perplexity-based defense. StateGuard's auditing cost averaged below $0.004 per interaction run. Evaluations seeded with real-world user interactions confirmed that the risk is not an artifact of synthetic prompt construction.
- ShadowMerge: A Novel Poisoning Attack on Graph-Based Agent Memory via Relation-Channel Conflicts
Synthesis
Plain-language abstract ShadowMerge is a cyberattack designed to poison the memory of AI agents that use knowledge graphs to store and recall information. By injecting a carefully crafted false relationship into shared graph memory, an attacker can cause the agent to retrieve and act on corrupted information in future interactions — all without any special access beyond ordinary user interactions.
Motivation AI agents increasingly use graph-based memory systems to store structured facts and reason across sessions, but the security of this memory type has not been studied. Existing poisoning attacks target flat text records and fail against graph memory because malicious content must survive graph extraction, entity merging, and retrieval steps — each of which can silently discard a naive attack payload.
Methodology The authors developed ShadowMerge, a black-box attack requiring only query-level access to the target agent. Its core primitive, Channel-Aligned Relational Competition (CARC), crafts a poisoned relation that shares the same anchor entity and relation channel as legitimate graph evidence while carrying a conflicting value. A three-stage pipeline called AIR — Anchor, Inscribe, and Render — constructs the payload so it survives graph extraction, merges into the correct entity neighborhood, and is retrieved for the target query. The attack was evaluated on the Mem0 memory framework and three public datasets: PubMedQA, WebShop, and ToolEmu.
Results ShadowMerge achieved an average attack success rate (ASR) of 93.8% across the three datasets, a 50.3 percentage-point absolute gain over the best baseline attack, while having negligible impact on unrelated benign tasks. A mechanism study confirmed the attack overcomes all three limitations of prior work: relation extraction, anchor-neighborhood merging, and target-query retrieval. Analysis of representative input-side defenses found them insufficient to mitigate ShadowMerge.
- MemLineage: Lineage-Guided Enforcement for LLM Agent Memory
Synthesis
Plain-language abstract MemLineage is a security system for AI agents that tracks the origin and derivation history of everything stored in an agent's long-term memory. Because modern agents accumulate chat logs, ingested documents, and tool outputs across sessions, an attacker can plant malicious content that later gets summarized by the agent itself into an authentic-looking memory entry—a chain-of-custody failure. MemLineage prevents such laundered memory entries from authorizing sensitive actions by tagging every memory with cryptographic signatures and a lineage graph showing which prior entries influenced it.
Motivation LLM agents that persist memory across sessions are vulnerable to a subtle attack: an adversary injects untrusted content that the agent's own retrieval-and-summarization loop transforms into a new entry committed under the agent's own identity. Existing defenses—signature-only layers, information-flow control planners, and retrieval-stage filters—cannot distinguish a benign summary from a laundered payload arriving through an authentic principal, leaving a gap between useful long-term memory and prevention of untrusted ancestry from authorizing sensitive actions.
Methodology MemLineage is implemented as a Python library integrating with LangGraph and consists of six modules around a single memory store. Each memory entry is signed with per-principal Ed25519 keys anchored in an RFC 6962 Merkle log; a weighted directed acyclic graph records LLM-mediated derivation links between entries. A max-of-strong-edges propagation rule enforces that any chain descending from an external ancestor with strong attribution edges inherits an untrusted label, which the sensitive-action gate refuses to act on. Three attribution algorithms are compared (uniform-weight, secondary-LLM judge with prompt-injection hardening, and white-box attention), and a tau-by-K ablation sweeps the lineage threshold against derivation chain length. Evaluation uses a deterministic mechanism-isolation harness that pins attacker behavior without real LLM API calls, plus a Codex-backed AgentDojo bridge under an intentionally vulnerable tool-output profile.
Results On the deterministic harness comparing three defense configurations against three attack families (AgentPoison-style, MemoryGraft-style, and sleeper-via-derivation), the no-defense baseline fails all three columns and the signature-only baseline fails two of three, while MemLineage drives all three attack success rates to zero. The tau-by-K ablation reveals that allowing K=5 derivation hops requires a threshold of tau <= 0.10 rather than the tau <= 0.30 that a K=1 measurement would suggest. Per-operation overhead is sub-millisecond on the hot path, well below the noise floor of any LLM call. On the AgentDojo bridge under a vulnerable tool-output profile, no-defense and signature-only baselines fail on all six banking task pairs, while all MemLineage configurations reduce strict AgentDojo attack success rate to zero.
- Towards Security-Auditable LLM Agents: A Unified Graph Representation
Synthesis
Plain-language abstract This paper introduces Agent-BOM (Agent Bill of Materials), a structured representation designed to make the behavior of AI agent systems auditable from a security perspective. It models an agentic system as a hierarchical graph that captures both the static components (models, tools, memory stores) and the dynamic runtime states (goals, reasoning steps, actions), then provides a graph-query framework for tracing how security threats enter, propagate, and cause harm.
Motivation Modern LLM-based agents autonomously invoke tools, maintain persistent memory across sessions, and collaborate with other agents — creating a large semantic gap between low-level system events and high-level execution intent. Existing security representations such as software bills of materials and runtime logs record what happened but cannot explain how a goal was formed, how context was contaminated, or how a malicious instruction propagated across agents and sessions, leaving post-incident auditing fundamentally incomplete.
Methodology The authors define Agent-BOM as a hierarchical attributed directed graph with two layers — a static capability base (models, tools, long-term memory) and a dynamic semantic-state layer (goals, context, reasoning trajectories, decisions, actions) — connected by typed semantic edges carrying security attributes. On top of this representation they develop a four-stage graph-query auditing paradigm: entry localization, backward tracing, forward tracing, and attribute adjudication. They instantiate and validate the framework against the OWASP Agentic Top 10 threat list, deploying an auditing plugin in the OpenClaw environment to construct Agent-BOM graphs from live agent executions.
Results Evaluation on representative real-world agentic attack scenarios showed that Agent-BOM accurately reconstructed stealthy attack chains across four threat classes: cross-session memory poisoning and tool misuse, capability supply-chain hijacking and unexpected code execution, multi-agent ecosystem hijacking, and privilege and trust abuse. In each case the graph-query paradigm successfully traced the full causal path from the malicious entry point through intermediate semantic-state changes to the realized harmful action, demonstrating that Agent-BOM can support root-cause analysis and security adjudication in complex multi-agent ecosystems.
- From Stateless Queries to Autonomous Actions: A Layered Security Framework for Agentic AI Systems
Synthesis
Plain-language abstract This paper proposes a structured security framework for agentic AI systems — AI that does not just answer questions but plans across long horizons, remembers past interactions, calls external tools, and coordinates with other agents. The authors introduce the Layered Attack Surface Model (LASM), which maps security threats to seven distinct architectural layers, and add a temporal dimension to capture how some attacks unfold slowly across sessions rather than in a single moment. The work is anchored by a systematic review of 94 papers published between 2021 and 2025.
Motivation Existing security analyses of AI systems organize threats by attack type (prompt injection, jailbreaking) without specifying which architectural component is vulnerable or how quickly a threat manifests. This leaves system designers unable to determine where to place security controls. The problem is compounded by the fact that agentic systems introduce genuinely new threat classes — such as long-term memory poisoning and multi-agent collusion — that have no direct analogues in classical LLM safety or traditional software security.
Methodology The authors conducted a systematic literature review following a PRISMA-inspired protocol, searching IEEE Xplore, ACM Digital Library, arXiv, and Google Scholar for papers from January 2021 to April 2025. From an initial pool of 1,247 records, 94 papers were retained after deduplication and full-text screening. Each paper was coded into one or more cells of a LASM-layer by attack-temporality matrix (7 layers × 4 temporal classes, yielding 120 paper-cell assignments), enabling a coverage heatmap that reveals which threat combinations are well-studied and which are neglected.
Results The analysis shows that the most dangerous emerging threats concentrate at the intersection of high-layer attacks (layers 5–7: multi-agent coordination, ecosystem supply chain, and governance) and slow-burn temporality (cross-session and weight-level threats): specifically covert agent collusion, long-term memory poisoning, MCP supply-chain compromise, and alignment failure as an insider threat. Only 8 of 120 paper-cell assignments (7%) fall in this high-risk zone, confirming it is severely under-studied. The paper identifies five research gaps in this zone, notes that two (emergent misalignment detection and steganographic collusion detection) have no near-term solution path, and provides a cross-layer defense taxonomy showing which threat classes existing defenses leave unaddressed.
- Phantom: General Trigger Attacks on Retrieval Augmented Language Generation
Synthesis
Plain-language abstract This paper introduces Phantom, an attack framework that can compromise AI chatbots built with Retrieval Augmented Generation (RAG) — systems that answer questions by pulling in relevant documents from a knowledge base. By injecting a single carefully crafted document into that knowledge base, an attacker can manipulate the chatbot's responses in targeted ways whenever a victim's query contains a specific trigger word or phrase.
Motivation RAG systems are increasingly used in commercial applications such as search engines, customer service bots, and personal assistants, and their knowledge bases often draw from large, hard-to-verify sources. This creates a security gap: a malicious actor who can insert even one document into the knowledge base can potentially steer the system's outputs, but prior work had not systematically studied or demonstrated such targeted backdoor poisoning attacks against RAG.
Methodology Phantom uses a two-stage optimization process. In the first stage, a poisoned document is optimized in embedding space so that it is retrieved only when the victim's query contains a chosen trigger token sequence, keeping the attack dormant otherwise. In the second stage, an adversarial string is appended to the document using a Multi-Coordinate Gradient (MCG) optimization strategy to induce specific harmful outputs — including refusal to answer, biased opinions, harmful content, private data exfiltration, and unauthorized API calls. Attacks were evaluated across three datasets, three retriever architectures, and seven LLM generators (Gemma-2B through GPT-4), using thirteen distinct triggers.
Results Phantom achieved high attack success rates across all tested objectives and model families. For the refusal-to-answer objective, all four tested generators (Gemma-2B, Vicuna-7B, Gemma-7B, Llama3-8B) were manipulated with high success rates without needing the MCG optimization step. For biased opinion generation, adding MCG yielded improvements of roughly 38–39 percentage points for models that resisted the command alone. Attacks transferred to GPT-3.5 Turbo and GPT-4 without white-box access to those models, and the researchers successfully executed a Phantom attack on NVIDIA's production black-box RAG system, Chat with RTX.
- PrivacyLens: Evaluating Privacy Norm Awareness of Language Models in Action
Synthesis
Plain-language abstract PrivacyLens is a benchmark framework for testing whether AI language models respect privacy norms when acting as agents on behalf of users — for example, drafting emails or posting to social media. It generates realistic test scenarios from privacy principles, then measures whether a model leaks sensitive information in its actual outputs, not just in how it answers abstract questions about privacy.
Motivation Language models increasingly act as agents with access to sensitive personal data such as calendars and emails. Prior evaluations of privacy awareness relied on asking models direct questions, but there is a growing gap between how models answer those questions and what they actually do when executing real tasks. No existing framework captured this behavioral gap in realistic, agentic communication settings.
Methodology The authors built PrivacyLens by grounding a set of privacy norms in academic privacy literature and crowdsourced real-world seeds. Each seed was expanded into a detailed vignette describing a data type, subject, sender, recipient, and transmission context, then further extended into full agent trajectories — sequences of tool calls and observations an LM agent would produce when completing a communication task. Models were evaluated both on probing questions (do they know the norm?) and on their actual agent behavior (do they follow it?), enabling direct comparison between stated awareness and in-action behavior.
Results State-of-the-art models leaked sensitive information in a substantial fraction of cases: GPT-4 leaked in 25.68% of agent trajectories and Llama-3-70B in 38.69%, even when prompted with privacy-enhancing instructions. The study also revealed a consistent discrepancy between models' high performance on privacy probing questions and their much weaker privacy behavior when executing user instructions as agents.
- Not what you've signed up for: Compromising Real-World LLM-Integrated Applications with Indirect Prompt Injection
Synthesis
Plain-language abstract This paper identifies and demonstrates a new class of security attack called Indirect Prompt Injection, where malicious instructions are hidden inside content that an AI assistant retrieves from the web or other sources. When the AI reads that content, the hidden instructions hijack its behavior—without the user or attacker ever typing anything directly into the chat. The authors show these attacks work against real deployed systems and can cause the AI to steal user data, spread misinformation, or act as an automated social engineer.
Motivation Prior work on prompt injection assumed an attacker had direct access to the AI's input. As AI assistants began integrating with search engines, email clients, and code tools—routinely ingesting untrusted external data—a new and largely unexamined attack surface opened up. The paper argues that the rapid deployment of LLM-integrated applications outpaced safety evaluations, leaving millions of users potentially exposed to adversaries who never interact with the system directly.
Methodology The authors developed a comprehensive threat taxonomy mapping classic computer-security concepts (intrusion, persistence, malware, denial of service, data exfiltration) to the novel LLM-integrated application setting. They then constructed and tested concrete attack prompts against both synthetic GPT-4-based applications with controlled functionality and real-world systems including Bing Chat (GPT-4 powered) and GitHub Copilot. For Bing Chat, injections were delivered by embedding instructions in HTML comments on pages read via the Edge sidebar feature, allowing local testing without public poisoning. Attack scenarios covered information gathering, fraud, malware spreading, prompt-worm propagation, and code-completion manipulation.
Results The attacks proved practically viable across all tested systems. Indirectly injected prompts successfully steered model behavior in ways that direct-interface jailbreak filters blocked: Bing Chat halted sessions for directly entered jailbreaks but obeyed the same instructions when they arrived via retrieved content. The compromised model retained injected instructions across multiple conversation turns, used conversation context to augment persuasion, and could exfiltrate user-disclosed information (such as a journalist's identity) through markdown hyperlinks or search queries to attacker-controlled URLs. GitHub Copilot was also shown to be susceptible to injections placed in retrieved code. The authors conclude that effective mitigations for these attacks are currently lacking.
- Here Comes The AI Worm: Unleashing Zero-click Worms that Target GenAI-Powered Applications
Synthesis
Plain-language abstract This paper demonstrates a new class of cyberattack called Morris-II, a computer worm that can spread automatically through networks of AI-powered applications. When these apps share information using a technique called Retrieval-Augmented Generation (RAG), a specially crafted malicious prompt can replicate itself from one app to the next, stealing private data and infecting other apps along the way — all without any user clicking anything.
Motivation AI-powered applications like email assistants increasingly rely on RAG-based inference, where models retrieve external data to answer queries. Prior security research focused on attacks against single AI applications, leaving open whether attackers could scale such attacks across entire interconnected ecosystems of GenAI apps. This paper addresses that gap by asking whether a worm-like chain reaction could propagate malicious behavior across a whole GenAI ecosystem.
Methodology The researchers designed adversarial self-replicating prompts — the core mechanism of Morris-II — and conducted an end-to-end evaluation against RAG-based GenAI-powered email assistants using the Enron email dataset. Each employee's personal RAG database was built from 100 of their emails (2,000 emails total). The study tested how worm performance varied across five embedding algorithm types and sizes, context window sizes, GenAI engine types (including GPT and Gemini variants), and number of propagation hops. They also developed and evaluated a guardrail called the Virtual Donkey to detect and block worm propagation.
Results The evaluation showed that attackers can craft emails that extract sensitive user data from the RAG context and embed it into AI-generated replies, which then propagate the worm to new recipients and compromise their assistants. The proposed Virtual Donkey guardrail achieved a perfect true-positive rate of 1.0 with a false-positive rate of only 0.015, and remained robust against out-of-distribution worms using unseen jailbreaking commands, a different email dataset, and various attack scenarios.
- Machine Against the RAG: Jamming Retrieval-Augmented Generation with Blocker Documents
Synthesis
Plain-language abstract This paper introduces a new type of attack on AI question-answering systems that use retrieval-augmented generation (RAG), where a language model looks up documents from a database before responding. The authors show that an attacker who can add just one specially crafted document — called a "blocker" document — to the database can cause the system to refuse to answer specific questions, claiming it lacks information or that the answer is unsafe.
Motivation RAG systems are widely used but are exposed to adversarial content whenever their underlying databases contain user-contributed or externally sourced documents. Existing safety evaluations for large language models do not assess this kind of denial-of-service risk, leaving a gap where an attacker can silently suppress specific information — for example, hiding negative reviews, concealing legal facts, or blocking regulatory disclosures — without producing obviously toxic output that would trigger standard safety checks.
Methodology The authors developed and compared several methods for generating blocker documents, including a black-box optimization approach that requires only query-level access to the RAG system — no knowledge of the embedding model or the underlying language model, and no auxiliary LLM. They evaluated these jamming attacks across multiple LLMs and embedding models, and also examined whether existing safety and trustworthiness metrics for LLMs capture vulnerability to this kind of attack. Potential defenses against blocker documents were also analyzed.
Results A single blocker document added to a RAG database is sufficient to cause the system to refuse to answer a targeted query. The paper demonstrates that resistance to jamming is a novel safety property distinct from those measured by current LLM safety benchmarks — meaning models that score well on standard safety evaluations can still be successfully jammed. The black-box optimization method for generating blocker documents works without knowledge of the target system's internals.
- The Emerged Security and Privacy of LLM Agent: A Survey with Case Studies
Synthesis
Plain-language abstract This paper is a survey of the security and privacy risks that arise specifically in LLM-based AI agents — systems that go beyond static language models to take actions, use tools, and interact dynamically with users and other agents. The authors categorize threats, analyze real-world impacts, review defensive strategies, and use case studies to make the material accessible.
Motivation LLM agents are being deployed widely in customer service, virtual assistants, and other high-value settings, yet security research has focused almost entirely on the underlying language models. The agents introduce new attack surfaces because their dynamic capabilities — tool use, multi-step reasoning, persistent memory — mean a single compromised action can cascade into broader harm. A comprehensive threat taxonomy covering both inherited LLM weaknesses and agent-specific vulnerabilities was missing.
Methodology The authors conducted a structured literature survey organized around the LLM agent workflow of thought, action, and perception. They classified threats into two top-level categories: threats inherited from LLMs (technical vulnerabilities such as hallucinations and catastrophic forgetting, plus intentional attacks such as data extraction and instruction-tuning attacks) and threats unique to agents (knowledge poisoning, functional manipulation, and output manipulation). They supplemented the taxonomy with case studies illustrating each threat type in realistic scenarios.
Results The survey identifies and categorizes a broad set of emerging threats, showing that agent-specific attacks — particularly functional manipulation via compromised tools and knowledge poisoning of training or memory data — pose risks that static LLM defenses do not address. The authors also map impacts across three dimensions: harm to human users, harm to the operating environment, and harm propagated to other interacting agents. Existing defensive strategies are reviewed and gaps for future research are outlined.
- A Practical Memory Injection Attack against LLM Agents
Synthesis
Concrete memory-injection attack.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- Unveiling Privacy Risks in LLM Agent Memory
Synthesis
Privacy leakage from agent memory stores.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- Episodic memory in AI agents poses risks that should be studied and mitigated
Synthesis
Risk framing for episodic agent memory.
Why it matters Surfaced by the 2026-06-11 dense-lane rerun (missed in the lexical-only window).
- SkillResolve-Bench: Measuring and Resolving Same-Capability Ambiguity in Agent Skill Retrieval
Synthesis
Plain-language abstract A benchmark and method for a specific skill-retrieval failure: the retriever finds the right capability family but surfaces the wrong member of it, one that shares the vocabulary and procedure shape while pointing at a stale resource, skipping a precondition, or applying the wrong check. The benchmark pairs each query's helpful skill with that query-specific risky sibling inside a large public candidate pool and scores helpful ranking alongside a harmful sibling rate. The method resolves candidates into capability families, scores query-conditioned utility, and exposes one representative per family before the final top-K list.
Motivation Skills have become loadable operational artifacts carrying instructions, scripts, resources and metadata, so the retrieval layer decides which procedural context enters an agent before planning or execution. That makes retrieval failures more specific than broad irrelevance. Public skill audits find weak routing metadata, non-actionable bodies, reusable-artifact defects and technical debt, and gains from curated skills weaken when agents must retrieve from large real collections. Related work has shown top-K skill quality cannot be reduced to independent query-skill relevance because the retrieved set must be compatible as a set, and security work has established that loaded skill packages affect planning, context, permissions, scripts and local resources. Existing positive-skill retrieval benchmarks identify useful or gold skills but assign no query-specific execution-risk siblings, while malicious-skill detection and permission enforcement act after admission rather than at the retrieval-time choice of representative.
Methodology The setting is formalized as same-capability execution-risk retrieval: a collection of queries, each with a candidate pool, an admitted helpful skill, a query-specific execution-risk sibling, and a released family relation. Construction starts from a task-facing skill admitted for a query, and the paired sibling changes exactly the condition that makes the procedure usable, keeping the sibling plausible under ordinary semantic retrieval. Candidate pools add library pressure by ranking the pair among unrelated and partially related public skills drawn from a public SkillRet corpus, so a system must both recover active capability families and choose the right representative within each. Evaluation reports Recall@K and NDCG@K for the helpful skill together with HSR@K, the rate at which the risky sibling appears in the final top-K. The release records source role and admission evidence, risk taxonomy, cue and leakage checks, hashes, query-disjoint splits and held-out outputs. The method, SkillResolve, has three components: a Capability Resolver returning active candidate groups that should compete as alternative representatives (singleton groups allowed, which recovers ordinary ranking); a query-conditioned Utility Scorer trained with admitted helpful skills as positives and confusable library alternatives mined under the same query and pool protocol as negatives, using ordinary retrieval signals plus contract-profile cues; and a Representative Selector keeping the highest-utility member of each resolved group before final ranking. Family sources can also be derived from public metadata or skill text, which trades exposure against recall.
Results Same-capability ambiguity is prevalent in public libraries: 4,716 of 4,997 audited SkillRet queries have at least one non-gold skill in the gold skill's domain/action/object family, and across seven standard retrievers a top-three list surfaces such a sibling for 47.3% of queries, with 36.6% containing both the gold skill and a strict same-family sibling. Generic lexical retrieval, SkillRouter and BGE reranking retrieve relevant skills but expose risky siblings, while an attribution-listwise baseline suppresses them at the cost of helpful retrieval quality. SkillResolve reaches Recall@3 0.766, NDCG@3 0.699 and HSR@3 of 0 under the released family relation, improving over SkillRouter by 0.112 Recall@3 and 0.165 NDCG@3 while reducing HSR@3 from 0.693. Component analysis identifies representative selection as the controlling mechanism: with the same utility scorer but no representative selection, HSR@3 rises to 0.236. The recall-exposure tradeoff depends on the quality of the family source, since a resolver that splits a helpful skill and its risky sibling into different groups lets both survive into the final ranking. Note on versions: SciX holds the June 2026 v1 of this arXiv entry, titled SkillResolve-Bench with 661 helpful/risky pairs and a 7,982-candidate pool; a later revision circulates as SameCapRisk-Bench with a larger unit count and a different baseline table. The mechanism and the metric are unchanged across both; the figures above are the v1 body.
- Auto-Policy, not Auto-Skill: Compiled Agent Skills for the Physical World
Synthesis
Plain-language abstract Agent Skills package procedural knowledge as markdown plus scripts, and that format describes how an agent should behave without deciding which behavior may become an action. As Skills move to settings that drive relays and locks, the gap becomes a physical one. The paper names Borrowed Authority: an inter-agent message carrying an instruction plus an unverifiable permission claim, which the receiving agent has no typed way to reject. Edge Skillguard answers it with a typed authority layer inside the Skill artifact - guard predicates over world state, leases and sensor evidence, expressed as a schema-validated policy file with a pure-function evaluator. On a live edge control plane it rejects 60/60 attacks across five variants while preserving all benign requests, holding at 5x scale and across hosts.
Motivation Self-evolving Skill harnesses generate orchestration automatically and report efficiency gains, not safety ones, so generating more Skills scales the advisory layer and leaves the authority decision to the model. Two adjacent attacks are already public: malicious skills distributed through community registries, plus a Claude Code project-file misconfiguration (CVE-2026-21852) that routed a session's API tokens to an attacker before trust was established, and jailbreaks of LLM-controlled robots reaching up to 100% success against deployed commercial platforms including a self-driving LLM, a wheeled UGV and a quadruped. Their intersection - a compromised skill artifact causing physical-state harm - is the open cell of the paper's attack table, and the authors construct and defend it before an in-the-wild incident rather than after.
Methodology An Edge Skillguard artifact is a tuple of orchestration states, typed world state (sensors, user identity, leases, device state, time, shared-state commit), typed envelope events, deterministic actions, guard predicates over state and event, a transition relation, bounded LLM holes, and inter-agent contracts incoming messages must satisfy. Guards are seven typed operators over dot-separated paths into envelope or state, shipped as a JSON-Schema-validated policy plus a pure-function evaluator that emits either an inbox publish or a structured policy_block log naming the failed predicates. It sits on a messaging substrate providing schema-validated typed envelopes, broker-attested sender_id from the connection token, durable per-agent FIFO inboxes, an audit-mirror outbox, and boundary rejection of malformed envelopes. Four conditions are compared - plain Skill, natural-language machine-to-machine with no receiver guard, a lease-only ablation, and the full policy - over 60 Borrowed Authority requests across five variants (stale presence, missing presence source, wrong-grantee lease, expired lease, lease-scope mismatch), 12 each, plus 60 benign requests, run in-process, on a live NATS broker against a Home Assistant deployment of 148 entities, and cross-host over Tailscale. Test subjects are isolated so no device adapter fires; the measurement is whether an unauthorized transition reaches the adapter boundary.
Results The full typed policy rejects 60/60 Borrowed Authority requests and preserves 60/60 benign ones, versus 60/60 wrongful actuation for both the plain Skill and the natural-language machine-to-machine baselines. The 5x run holds 300/300 attack rejection and 300/300 benign success at p95 399 microseconds on the live broker, and the cross-host Tailscale run holds the same correctness at p95 7.9 ms. Median latency is 3.2 microseconds in-process, 273 microseconds on the local broker, 5.7 ms over the mesh, with 0 LLM calls per decision against 1 for the advisory baselines. The lease-only ablation catches 36/60, covering the three lease-bound variants and letting both sensor-bound variants through, so freshness and source predicates carry the remainder. Blocked requests surface the failed predicates rather than a model rationale. The authors do not claim automated policy synthesis; hand-authored guards are the supported workflow, and the attack class is constructed rather than observed in the wild.
Applications & Personalization
Applications & Personalization of Agentic Memory: long-horizon user modeling, personalized assistants, multimodal memory, and domain deployments (coding, healthcare, GUI/computer-use, embodied)
Key threads
- Personalization is moving from static profiles to EVOLVING per-user memory with self-learning/context-distillation loops (TSUBASA, Reflective Memory Management, situational/persona steering), shifting eval from one-shot recall toward measuring preference accumulation, revision, and drift over many sessions.
- Procedural/experience memory is the dominant memory type in deployment domains: coding agents transfer memory across domains (Memory Transfer Learning), self-evolving agents distill experience into reusable capabilities (Mem2Evolve), and GUI/visual agents compile traces into reusable skills (SkillDroid, MMSkills). Eval must score reuse quality AND efficiency, not just task success.
- Multimodal memory is emerging as a distinct frontier (PersonaVLM, MMSkills) — memory keyed on images/perception+action, not just text logs — yet benchmarks and synthetic pipelines remain overwhelmingly text-conversation-based.
- Domain deployments demand domain-grounded evaluation frameworks rather than generic recall QA: healthcare proposes longitudinal coherence/continuity/adaptation/agency layers (longitudinal health agent) and clinical world models (Clinical World Model + Skill-Mix), which generic memory benchmarks do not capture.
- Memory enables a shift from reactive recall to PROACTIVE, intent-aware action (PASK) and to multi-user isolation (Multi-User LLM Agents) — production axes (proactivity, per-user partitioning, cross-user leakage) that current single-user recall benchmarks largely ignore.
- The 'harness' itself is becoming the unit of engineering and study for personal/deployed agents (SemaClaw harness engineering, M*'s per-task memory harness), aligning the application literature with the open-source eval-harness focus of this work.
Open gaps
- Almost no standardized, multi-session benchmark targets MULTIMODAL personalized memory; PersonaVLM and MMSkills introduce methods but the field lacks a shared multimodal long-horizon eval set with synthetic-data generation recipes.
- Domain deployments (healthcare, coding, GUI) propose bespoke evaluation frameworks (continuity/adaptation layers, clinical world models, skill-reuse efficiency) but there is no cross-domain harness that lets the same memory system be scored under each domain's specific longitudinal criteria.
- Multi-user / per-user memory isolation and cross-user leakage (Multi-User LLM Agents) is essentially unbenchmarked — no synthetic adversarial test set probes whether one user's memory contaminates another's responses.
- Procedural-memory transfer and reuse are claimed to generalize across domains (Memory Transfer Learning, Mem2Evolve) but evaluations rarely separate in-domain reuse from genuine out-of-distribution transfer, leaving the transfer claim under-measured.
- Proactive use of memory (acting on remembered intent unprompted, PASK) lacks evaluation methodology — recall-style benchmarks score retrieval accuracy but not whether/when an agent should surface remembered information without being asked, including false-proactivity costs.
- Memory Transfer Learning: How Memories are Transferred Across Domains in Coding Agents
Synthesis
Plain-language abstract This paper studies whether AI coding agents can benefit from memories collected in one programming domain when working on tasks in a different domain. The authors introduce Memory Transfer Learning (MTL), which pools experiences from heterogeneous coding tasks—such as software engineering, machine learning development, and competitive programming—and makes them available to agents tackling new problems. They test this idea across six coding benchmarks and four different ways of representing memories, from raw execution traces to high-level abstract insights.
Motivation Most memory-augmented coding agents are restricted to reusing experiences from the same task domain, ignoring the fact that diverse programming problems share common infrastructure like Linux shells and programming languages. As gains from scaling training data plateau, self-evolution through accumulated experience offers a path to further improvement, but existing systems fail to exploit knowledge across domain boundaries—leaving a large pool of potentially transferable experience untapped.
Methodology The researchers evaluated MTL across six coding benchmarks spanning software engineering (SWE-level), machine learning, and competitive coding tasks. They used four memory representations of varying abstraction: concrete execution trajectories, code snippets, experiential planning and debugging traces, and high-level abstract insights. A unified memory pool drawn from all heterogeneous domains was made available during retrieval, and performance was compared against single-domain memory baselines.
Results Cross-domain memory transfer improved average performance by 3.7% across the six benchmarks. The primary source of benefit was meta-knowledge—operational know-how such as validation routines and structural inspection strategies—rather than task-specific code. The paper found that abstraction level determines transferability: high-level abstract insights generalize well across domains, while low-level execution traces often cause negative transfer by introducing excessive task-specific detail. Performance gains also scaled with the size of the memory pool and the number of contributing domains, and memory was shown to transfer effectively even between different underlying models.
- SkillDroid: Compile Once, Reuse Forever
Synthesis
Plain-language abstract SkillDroid is an Android automation system that learns from a task the first time an AI completes it, then replays that learned sequence on later requests without involving the AI again. Instead of reasoning through every step of a repeated task from scratch, it stores a reusable action template and replays it at machine speed, falling back to AI assistance only when something unexpected occurs.
Motivation Current AI-based mobile agents treat every task execution as an independent reasoning episode, calling the language model at each action step. This means a task completed successfully yesterday is re-derived entirely from scratch today, with no gain in speed or reliability. LLM calls account for 75-94% of total agent execution time, and in testing a stateless agent's success rate degraded from 80% to 44% over 150 rounds as instruction phrasing became more varied, because past successes provide no benefit to future attempts.
Methodology SkillDroid uses a three-layer architecture running on top of an open-source Android automation framework. In Layer 1, an LLM guides task execution step by step and, on success, a skill compiler extracts a parameterized template — a sequence of UI actions with weighted element locators and typed parameter slots — stored in a local SQLite database. In Layer 2, a matching cascade using regex patterns and embedding-based semantic similarity routes new instructions to stored skills for replay via Android's accessibility interface with zero LLM calls, using a state verifier to detect UI deviations and gracefully fall back when needed. In Layer 3, a failure-learning component tracks skill reliability and triggers recompilation when a skill's failure rate exceeds 50%, progressively replacing noisy initial compilations with cleaner versions.
Results Over a 150-round longitudinal evaluation spanning 15 task types across diverse Android applications with systematic instruction variation and controlled perturbations, SkillDroid achieved an 85.3% success rate — 23 percentage points above a stateless LLM baseline — while using 49% fewer LLM calls. The skill replay mechanism achieved a perfect 100% success rate across 79 replay rounds at 2.4 times the speed of full LLM execution. Critically, the system's success rate converged upward from 87% to 91% across experimental phases, while the baseline degraded from 80% to 44%, demonstrating that SkillDroid improves with use while stateless agents become less reliable as task variation grows.
- In Prospect and Retrospect: Reflective Memory Management for Long-term Personalized Dialogue Agents
Synthesis
Plain-language abstract This paper introduces Reflective Memory Management (RMM), a system that helps AI dialogue agents remember and retrieve relevant information across many conversations over time. Because large language models are stateless — they forget everything between sessions — the authors built an external memory mechanism with two complementary parts that work together to store and recall user information more accurately and adaptively.
Motivation AI assistants used in customer service, healthcare, or education need to remember what individual users have told them across many past conversations, not just the current session. Existing external memory systems for language models suffer from two problems: they store information at rigid, pre-defined chunk sizes (such as per conversation turn or per session) that do not match natural topic boundaries, and they rely on fixed retrieval mechanisms that cannot adapt to different users or dialogue styles, making personalized long-term interaction difficult.
Methodology The RMM framework combines two mechanisms. Prospective Reflection dynamically decomposes dialogue history into topic-based memory units across multiple granularities — individual utterances, turns, and whole sessions — so that semantically related content is grouped together regardless of where session or turn boundaries fall. Retrospective Reflection treats retrieval improvement as an online reinforcement learning problem: as the language model generates responses, it cites which retrieved memories were useful, and those citation signals are used as unsupervised reward feedback to iteratively refine the retriever without requiring any labeled training data. The system was evaluated on two benchmarks, MSC and LongMemEval, using Contriever and GTE retrievers with Gemini-1.5-Flash and Gemini-1.5-Pro as generators.
Results RMM achieves more than 10% accuracy improvement over a no-memory baseline on LongMemEval, and more than 5% improvement over the strongest prior baseline across memory retrieval and response generation metrics on both benchmarks. The full RMM framework reaches a METEOR score of 30.8% on MSC and Recall@5 of 60.4% on LongMemEval. Citation-based scoring used in Retrospective Reflection was validated as reliable, achieving an overall F1 of 86.7% for identifying useful versus non-useful retrieved memories. Experiments also show that flexible topic-based granularity from Prospective Reflection approaches oracle-level performance compared to any single fixed granularity strategy.
- TSUBASA: Improving Long-Horizon Personalization via Evolving Memory and Self-Learning with Context Distillation
Synthesis
Plain-language abstract This paper introduces TSUBASA, a framework for making AI language models better at personalizing their responses over long stretches of time—for example, tracking a user's preferences and history across many conversations. It combines two components: one that maintains and updates a structured memory of the user, and one that trains the model to internalize that memory more effectively so it can answer personal questions without needing to look up everything at retrieval time.
Motivation Personalized language models struggle with long-horizon tasks—situations where they must reason across a user's extensive history of interactions. Existing memory systems grow linearly and fail at tasks requiring implicit temporal reasoning; retrieval-augmented approaches face a quality-efficiency tradeoff where better answers require retrieving more context at prohibitive cost; and fine-tuning approaches are held back by a train-inference gap because raw conversation data does not prepare models well for the complex personalization tasks they face at evaluation time.
Methodology TSUBASA uses a two-wing design. The first wing handles dynamic memory writing: core factual observations are extracted from raw conversations and a memory manager applies structured operations (ADD, UPDATE, RECONCILE, IGNORE) to keep the memory store compact and conflict-free. The second wing handles internalized memory reading through a self-learning pipeline that applies a teacher-student context distillation objective on synthetic question-answer pairs: a frozen teacher model sees the full session context, while a trainable student model sees only the question, and the distillation loss trains the student to internalize user-specific knowledge parametrically. Evaluations were conducted on long-horizon personalization benchmarks using the Qwen-3 model family ranging from 4B to 32B parameters, compared against memory-augmented baselines including Mem0 and Memory-R1.
Results TSUBASA surpasses competitive memory-augmented systems that rely primarily on memory writing, such as Mem0 and Memory-R1, on long-horizon benchmarks. The framework achieves Pareto improvements over prior approaches—delivering higher personalization fidelity while using a reduced token budget—effectively breaking the quality-efficiency tradeoff. The approach also preserves user privacy by avoiding cross-user training.
- Mem2Evolve: Towards Self-Evolving Agents via Co-Evolutionary Capability Expansion and Experience Distillation
Synthesis
Plain-language abstract This paper introduces Mem2Evolve, a framework for building AI agents that can improve themselves over time by combining two types of memory: a store of past task experiences and a store of dynamically created tools and specialist sub-agents. Rather than treating these two growth processes separately, the system makes them work together so each one reinforces the other.
Motivation Existing self-evolving agent frameworks either let agents learn from experience but keep them locked to a fixed set of tools, or let agents create new tools and sub-agents but do so blindly without drawing on past experience. Both approaches are limited: the first cannot expand what the agent is capable of doing, while the second produces unreliable results because it ignores proven strategies and known pitfalls.
Methodology Mem2Evolve maintains two memory components — an Experience Memory that stores trajectories from past task executions, and an Asset Memory that stores dynamically created tools and expert agents. When a new task arises, the system retrieves relevant past experience to guide the creation of new tools or specialist agents, then stores the resulting execution trajectory back into experience memory, enabling a continuous co-evolutionary loop. The framework was evaluated across 6 task categories and 8 benchmarks.
Results Mem2Evolve achieves an 18.53% improvement over standard large language models, an 11.80% improvement over agents that evolve only through experience accumulation, and a 6.46% improvement over agents that evolve only through asset creation, demonstrating that the co-evolutionary approach is more effective and stable than either strategy in isolation.
- PersonaVLM: Long-Term Personalized Multimodal LLMs
Synthesis
Plain-language abstract PersonaVLM is an agent framework that turns a general-purpose multimodal AI assistant into a long-term personalized one. It gives the model three abilities it currently lacks: proactively building and updating a memory of the user across many sessions, reasoning over that memory to answer new questions, and continuously inferring the user's personality so replies stay in tune with who they actually are.
Motivation Current multimodal AI assistants treat every interaction as if it were the first — they have no mechanism to remember that a user's preferences have changed, or to learn personality traits that emerge gradually across many unrelated conversations. Prior personalization work addressed only static, single-session scenarios through input augmentation or output alignment, leaving the fundamental challenge of evolving preferences and personality unmet.
Methodology PersonaVLM introduces a structured memory architecture with a personality profile component (PEM) and four memory types — core, semantic, procedural, and episodic — that are proactively updated after each interaction. A two-stage process handles each turn: in the response stage the model performs multi-step reasoning with memory retrieval before replying; in the update stage new information is extracted and consolidated into the memory database. The authors also created Persona-MME, a new benchmark with over 2,000 curated interaction cases covering seven aspects and 14 fine-grained tasks, and tested PersonaVLM and more than 10 proprietary and open-source models on it.
Results Under a 128k-context setting PersonaVLM improved over the baseline by 22.4% on Persona-MME and 9.8% on the PERSONAMEM benchmark. It also outperformed GPT-4o by 5.2% on Persona-MME and 2.0% on PERSONAMEM, with further gains confirmed in open-ended evaluations.
- MMSkills: Towards Multimodal Skills for General Visual Agents
Synthesis
Plain-language abstract MMSkills is a framework that gives AI agents reusable, visually grounded knowledge packages for operating graphical user interfaces and game environments. Each package pairs a written procedure with structured state cards that say when the procedure applies and what visual cues confirm it, plus multi-view screenshot keyframes. A temporary 'branch' process inspects the package evidence, aligns it with the live screen, and returns compact guidance to the main agent rather than flooding its context with raw screenshots.
Motivation AI agents that navigate GUIs and games must act on visual evidence, yet existing skill libraries store reusable knowledge only as text or code. A text-only skill can describe the correct steps but cannot tell the agent whether a dialog is ready, which sheet is active, or whether a goal has been visually confirmed. This gap between verbal instructions and visual state recognition causes agents to repeat actions, lose track of context, or fail tasks that require recognizing subtle on-screen conditions.
Methodology The authors define a multimodal skill package format containing a textual procedure, runtime state cards encoding when-to-use and when-not-to-use conditions with verification cues, and multi-view keyframes covering full-frame, focused, and before/after views. An automated trajectory-to-skill Generator processes public, non-evaluation interaction trajectories through workflow grouping, procedure induction, visual grounding, and meta-skill-guided auditing to produce these packages without storing raw demonstrations. At inference time a two-stage branch-loading mechanism selects relevant state cards and keyframe views in a temporary branch, aligns them with the live observation, and returns structured planning guidance to the main agent. The framework was evaluated on OSWorld, macOSWorld, VAB-Minecraft, and Super Mario Bros in LMGameBench across six multimodal model families including Gemini 3 Flash, Qwen3-VL-235B, GLM-5V, Kimi-K2.6, and Qwen3-VL-8B-Instruct.
Results MMSkills consistently improve success rates over both no-skill and text-only baselines across all evaluated benchmarks and model families. On OSWorld, overall success rates rise substantially for every tested model: for example, Gemini 3 Flash improves from 36.65% (no skill) to 47.97% (MMSkills), and the smaller Qwen3-VL-8B-Instruct improves from 10.78% to 25.40%. On VAB-Minecraft, Qwen3-VL-8B-Instruct success rate rises from 23.28% to 38.79%. Ablations confirm that both state cards and visual keyframes contribute independently, and that branch loading outperforms inserting skill content directly into the main context.
- A longitudinal health agent framework
Synthesis
Plain-language abstract This paper proposes a design framework for AI agents that support people's health over extended periods of time — across multiple conversations and weeks or months — rather than treating each interaction as a standalone event. The authors identify what such a longitudinal health agent needs to do, define four core properties it must embody, and illustrate the framework with representative use cases from clinical, preventive, and self-management settings.
Motivation Most current AI health agents respond to single queries and treat each interaction independently, which limits their usefulness for ongoing health challenges like chronic symptom management or behavior change that require follow-up, evolving goals, and accountability over time. No general framework existed for designing agents capable of maintaining coherent, goal-directed support across multiple sessions when health objectives remain unmet or change.
Methodology The authors conducted a perspective synthesis, drawing on approximately 40 prior studies spanning human-computer interaction, personal health informatics, and clinical care. Through iterative discussion within an interdisciplinary team of experts in HCI, AI, health informatics, and clinical care, they synthesized continuity-of-care and personal health informatics principles into a multi-layer framework, then demonstrated the framework's application through representative use cases.
Results The framework comprises four interdependent layers — coherence (stable memory, roles, and relationships across sessions), continuity (active stewardship of health goals through follow-up and accountability), adaptation (flexible personalization and reflexive reassessment as goals evolve), and agency (transparent negotiation of authority between user and system, including proactive intervention and user override). The authors show through use cases that applying these layers enables longitudinal agents to maintain meaningful engagement and support safe, personalized decision-making over time, and they identify open challenges including consistent longitudinal reasoning and dynamic alignment with clinical guidelines.
- Grounding Clinical AI Competency in Human Cognition Through the Clinical World Model and Skill-Mix Framework
Synthesis
Plain-language abstract This paper introduces the Clinical World Model and Clinical AI Skill-Mix, a conceptual framework that gives clinical AI a formal account of the medical world in which it must operate. It formalizes clinical care as an interaction among patients, providers, and the broader care ecosystem, and organizes AI competency into eight dimensions that together define billions of distinct "competency coordinates" — each specifying a unique combination of clinical condition, care phase, setting, provider role, task, and how the AI engages human reasoning.
Motivation Clinical AI systems perform well on benchmarks and medical licensing exams but routinely fail when deployed in real settings: fewer than 6% of externally validated radiology models maintain their original performance, and large language models that pass licensing exams still falter under the uncertainty of authentic clinical reasoning. The field lacks a shared formal model of the clinical world that connects evaluation, regulation, and system design, leaving no principled way to specify where AI reliability has actually been demonstrated.
Methodology Rather than empirical experiments, the paper develops a theoretical framework. The authors synthesize established traditions in clinical AI — sociotechnical systems research, regulatory science, evaluation benchmarks, and agentic architectures — and identify three structural gaps none of them address alone. They then construct the Clinical World Model as a tripartite structure (Patient, Provider, Ecosystem) with ten views and thirteen dimensions, and develop parallel decision-making architectures for human and AI agents grounded in validated principles of clinical cognition. The Clinical AI Skill-Mix operationalizes competency through five dimensions defining the clinical space and three specifying how AI engages human reasoning.
Results The framework establishes that the combinatorial product of its eight competency dimensions yields a space of billions of distinct competency coordinates, and that validation within one coordinate provides minimal evidence of performance in another — making the competency space irreducible. This structural implication reframes the field's central question from whether AI works to in which competency coordinates reliability has been demonstrated, and for whom, supplying a common grammar for specifying, evaluating, and bounding clinical AI across stakeholders.
- PASK: Toward Intent-Aware Proactive Agents with Long-Term Memory
Synthesis
Plain-language abstract This paper introduces Pask, a proactive AI assistant that monitors ongoing user activity in real time and offers help without being asked. Rather than waiting for a user to type a question, Pask continuously senses context, infers what the user likely needs, and delivers assistance at the right moment. The system is built around a new model called IntentFlow for detecting user needs, a three-layer memory system for building up a persistent understanding of each person over time, and a full software infrastructure that ties everything together.
Motivation Most AI systems today operate in a purely reactive mode: a user asks a question and the system answers. This works poorly when users are busy, in meetings, or watching video and cannot stop to type a prompt. The paper argues that this creates both a usability gap and a fundamental barrier to deeper human-AI understanding. Existing research on proactive AI was limited to narrow scenarios and controlled settings, with no unified framework and no mechanism for the AI to accumulate knowledge about a user across many sessions.
Methodology The authors propose DD-MM-PAS, a three-component paradigm covering Demand Detection (DD), Memory Modeling (MM), and a Proactive Agent System (PAS). IntentFlow, built on top of the Qwen3-30B-A3B base model, is trained first with supervised fine-tuning on a 102,000-sample dataset of synthetic and real-world examples, then refined with reinforcement learning to improve intent alignment under streaming, low-latency conditions. The memory system uses three tiers: a User Memory cache for stable user traits and recent signals, a Workspace Memory implemented via the model context window for within-session continuity, and a Global Memory LLM-RAG store for long-term accumulation across sessions. Evaluation uses LatentNeeds-Bench, a new benchmark of 100 real sessions (3,936 annotated turns) spanning Work, Learning, and Daily domains, constructed from user-consented speech transcriptions and refined through thousands of rounds of human editing.
Results IntentFlow achieves an overall balanced accuracy of 83.3% on LatentNeeds-Bench, matching or exceeding leading commercial models under latency constraints. Most baseline language models struggle with demand detection: Gemini-2.5-Flash-Lite scores 18.8 on demand turns, Claude-Haiku-4.5 reaches 38.9, and even GPT-5-Mini only achieves 66.5, while Gemini-3-Flash is the strongest baseline at 83.3. A key finding is that targeted training substantially improves proactive capability beyond what general-purpose instruction-following achieves. In multi-turn analysis, IntentFlow maintains above 80% balanced accuracy across all conversation depth buckets, whereas the strongest baseline drops from 85.6% to 70.8% over long interactions, a decline of 17.3 percentage points.
- Multi-User Large Language Model Agents
Synthesis
Plain-language abstract This paper studies what happens when a single AI assistant must serve multiple users at the same time — each with different goals, levels of authority, and private information. The authors formalize this as a multi-principal decision problem, build a protocol for multi-user interaction, design three test scenarios, and run frontier language models through them to see where they break down.
Motivation Most language models are trained and evaluated assuming a single user whose instructions the model obeys without qualification. As these systems are embedded in team workflows and organizational tools, they must handle multiple simultaneous users who may have conflicting instructions, different authority levels, and information that should not be shared across users. No systematic framework or benchmark existed for this setting.
Methodology The authors formalized multi-user LLM interaction using a multi-principal decision framework borrowed from economics, then introduced a unified interaction protocol that explicitly encodes user identity, roles, and visibility constraints. They designed three stress-test scenarios: multi-user instruction following under conflicting objectives, cross-user access control and privacy preservation across multiple conversation rounds, and sequential multi-user coordination for meeting scheduling under partial information disclosure. They evaluated roughly twenty frontier LLMs — including GPT-5, Claude, Gemini, Grok, LLaMA, Qwen, and DeepSeek variants — across these scenarios.
Results Frontier models fail systematically on all three dimensions. Instruction-following performance degrades substantially when two users issue conflicting directives. Privacy scores drop significantly as interaction rounds increase, with most models showing measurable degradation by round ten, indicating that access control breaks down under sustained interaction. In the coordination task, models with higher success rates resolved meeting scheduling within fewer than four turns, while weaker models needed one to two additional rounds; full-information settings consistently outperformed partial-information settings, and Llama-3-70B exhibited a distinct failure of committing to incorrect answers prematurely rather than asking clarifying questions.
- SemaClaw: A Step Towards General-Purpose Personal AI Agents through Harness Engineering
Synthesis
Plain-language abstract SemaClaw is an open-source multi-agent application framework designed to make personal AI agents more reliable, safe, and capable of learning across sessions. The paper introduces a set of engineering components — an orchestration method, a safety system, a context management architecture, and a knowledge-building tool — that together form the infrastructure layer between a capable AI model and a production-ready agent system.
Motivation When millions of users began deploying personal AI agents for tasks like travel planning and multi-step research, three system-level gaps became clear: existing frameworks lacked structured yet adaptive task orchestration, had no robust runtime safety enforcement for consequential actions like file modification or API calls, and provided only log-oriented memory that could not consolidate knowledge across sessions. These gaps define the difference between a capable model and a dependable agent, which the authors call the 'harness engineering' problem.
Methodology The authors designed and implemented SemaClaw as a two-layer architecture separating a reusable agent runtime from a configurable application harness. Key components include: DAG Teams, a two-stage hybrid orchestration method that combines LLM-based dynamic task decomposition with deterministic directed-acyclic-graph execution; PermissionBridge, a runtime safety system that treats authorization checkpoints as first-class control primitives for explicit user approval of high-risk actions; a three-tier context management architecture unifying working context, long-term memory retrieval, and per-agent persona partitioning; a four-layer plugin system covering MCP tools, subagents, skills, and hooks; a four-mode scheduled task system scaling token use to task complexity; and an agentic wiki skill for automated personal knowledge base construction that externalizes session-derived insights into a durable, user-owned format.
Results The paper presents SemaClaw as an open-source framework (released on GitHub at midea-ai/SemaClaw) with the stated contributions demonstrably instantiated in the system design. The work is primarily architectural and system-design in nature; the paper describes the framework's components and their rationale rather than reporting benchmark numbers or comparative experiments. The authors argue that the combination of DAG-based orchestration, runtime permission enforcement, structured context management, and knowledge sedimentation collectively addresses the production-reliability gap that prior open-source agent frameworks left open.
- From Storage to Experience: A Survey on the Evolution of LLM Agent Memory Mechanisms
Synthesis
Plain-language abstract This paper is a survey of how memory systems in AI agents powered by large language models (LLMs) have developed over time. The authors propose a three-stage evolutionary framework — Storage, Reflection, and Experience — to organize and explain the progression of memory designs, and use it to identify the core technical drivers and open challenges in the field.
Motivation LLMs are stateless by nature, meaning they cannot retain information across interactions on their own. This makes it hard for LLM-based agents to stay consistent over long, multi-step tasks or to learn from past mistakes. Prior survey work on agent memory was fragmented, split between engineering-oriented and cognitive-science-oriented perspectives, with no unified framework explaining why and how memory mechanisms have evolved.
Methodology The authors conduct a systematic literature survey organized around a novel three-stage taxonomy they formally define: Storage (faithful recording of interaction trajectories), Reflection (dynamic evaluation and refinement of stored records), and Experience (cross-trajectory abstraction of generalized behavioral patterns). They analyze the field using a 'Why-How-What' structure addressing three research questions about the drivers, path, and outcomes of memory evolution, and they also catalog relevant benchmarks across each stage.
Results The survey maps existing memory mechanisms onto the three-stage framework and identifies the core catalysts driving evolution: the need for long-range consistency, the challenges of dynamic environments, and the goal of continual learning. It highlights that the frontier Experience stage — characterized by active exploration and cross-trajectory abstraction using techniques such as Minimum Description Length compression of trajectory clusters — addresses bottlenecks in agent adaptability. The authors also identify gaps in benchmark coverage, particularly for the Experience stage, and call out distributed shared memory and multimodal memory fusion as critical directions for future work.
- StreamMemBench: Streaming Evaluation of Agent Memory for Future-Oriented Assistance
Synthesis
Plain-language abstract StreamMemBench is a streaming benchmark that tests whether a personal-agent memory system can turn what it observes and how users interact with it into future-oriented assistance. Built on EgoLife egocentric lifelogs, it anchors each evaluation on a hidden piece of user-specific evidence and wraps a two-step task around it: an initial task that depends on the evidence, then a follow-up task that tests whether the agent reused both the evidence and the user's feedback. Four metrics diagnose evidence retention, feedback incorporation, initial evidence use, and follow-up reuse.
Motivation A central job of personal-agent memory is to carry stored observations and prior interactions forward into later, similar tasks, but existing memory benchmarks test dialogue recall or task improvement in isolation and usually rely on scripted or synthesized dialogues whose feedback is not tied to verifiable observations. That leaves the trajectory from streaming observations to later assistance largely untested — and even commercial assistants such as ChatGPT and Gemini store information that fails to help when it is actually needed.
Methodology In the construction stage an anchor agent processes five-minute EgoLife segments in stream order and extracts a user-specific evidence anchor plus two application-oriented queries, and a review agent retains a candidate only if both queries satisfy Leak=0 (the query does not reveal the evidence), Need=1 (ignoring the anchor yields a wrong or generic answer), and Natural=1 (it reads as a plausible request). In the evaluation stage the memory system ingests the lifelog chronologically, answers the initial task, receives confirming or correcting feedback from a user simulator, commits that interaction to memory, and then answers a follow-up task grounded in the same anchor; an evaluation agent scores Fidelity, Feedback Incorporation, Initial Evidence Use, and Follow-up Reuse against atom-level checklists, and the Fidelity−IEU / Fidelity−FUR gaps localize failures.
Results Across eight systems — two retrieval baselines (RAGraw, RAGext) and six memory systems (A-Mem, Mem0, EverMemOS, MemOS, MemoryOS, MemSkill) — on two backbones, current memory systems are not yet reliable for future-oriented assistance: they often fail to use evidence from egocentric observations in the initial task and to turn interaction feedback into reusable follow-up behavior. The failures are not explained by storage alone — systems frequently retain the evidence (with some Fidelity inflated by raw-text retention) yet do not use it — which motivates evaluation that traces each piece of evidence from its first appearance in the stream through initial use, feedback incorporation, and follow-up reuse.
Forgetting & Consolidation
Forgetting & consolidation metrics in agentic memory systems (catastrophic forgetting, negative transfer, memory consolidation incl. sleep-consolidation, algorithmic forgetting/pruning/eviction, stale-memory obsolescence, knowledge-update/belief-revision, stability-plasticity) — and how, or whether, any of it is measured.
Key threads
- Neuroscience-grounded consolidation (sleep-consolidation, synaptic-tagging-and-capture, hippocampal-cortical metaphors) is the dominant framing for 2026 forgetting work: SCM, Evolve, ZenBrain, Adaptive Memory Crystallization.
- Obsolescence / stale-memory and belief-revision over time is emerging as its own evaluable problem (STALE benchmark, Time-is-Not-a-Label temporal KGs, NeuSymMS self-curation), distinct from static fact retrieval.
- Eviction/pruning is increasingly designed as forget-with-recall or utility-driven retention (Cooperative Memory Paging, Learning to Forget/H2-EMV, Memanto information-theoretic scoring) rather than hard deletion.
- Self-evolving stores raise the negative-transfer/forgetting risk explicitly, and a small set of multi-episode benchmarks (SEA-Eval) now try to measure accumulation-vs-amnesia beyond single-episode scoring.
- Continual-RL forgetting machinery (forward transfer, forgetting%, stability-plasticity at neuron level) is being imported into agent memory (Adaptive Memory Crystallization, Neuron-level Balance, Lifelong-Learning roadmap).
Open gaps
- No shared/standardized forgetting metric for textual agent memory: continual-RL borrows forward-transfer and forgetting% (AMC), STALE uses bespoke 3-dimensional accuracy, but there is no common retention-curve or forgetting-rate protocol across LLM-agent memory papers.
- Most self-evolving / consolidating stores (A-MEM, EvolveMem, NeuSymMS, ZenBrain) report only downstream task quality and never quantify negative transfer or capability lost during self-modification — consolidation is asserted, not measured.
- Stability-plasticity is invoked rhetorically in LLM-agent memory but quantified only in RL/neuromorphic settings (Neuron-level Balance, probabilistic metaplasticity); no agent-memory paper reports a stability-plasticity operating point.
- Obsolescence detection is benchmarked almost solely by STALE; there is little work measuring whether deletion/pruning policies remove the RIGHT stale items (precision/recall of obsolescence decisions) rather than just shrinking the store.
- Sleep-consolidation systems (SCM, Evolve) describe consolidation mechanisms but the searches surfaced no ablation isolating the consolidation step's effect on long-horizon retention vs a no-consolidation control.
- SEA-Eval: A Benchmark for Evaluating Self-Evolving Agents Beyond Episodic Assessment
Synthesis
Plain-language abstract This paper introduces SEA-Eval, the first benchmark designed to evaluate AI agents that improve themselves over repeated tasks. Most current benchmarks treat each task in isolation, resetting the agent's memory each time — which makes it impossible to measure whether an agent is genuinely learning from experience or just repeatedly solving problems from scratch. SEA-Eval is built around a new category of agent called a Self-Evolving Agent (SEA), which maintains persistent memory across tasks and uses past experience to get faster and cheaper over time.
Motivation Existing AI agent benchmarks evaluate each task as an isolated episode, resetting memory at every task boundary. This design structurally prevents them from detecting cross-task learning. Two agent frameworks can achieve identical success rates while differing dramatically in whether they are genuinely evolving — one accumulating efficient strategies, the other simply re-doing zero-shot reasoning every time. Current benchmarks produce a 'capability illusion' and cannot distinguish these fundamentally different behaviors.
Methodology The authors formalize the Self-Evolving Agent concept and its core architecture — the Evolutionary Flywheel, a closed loop of execution, experience distillation, and augmented re-execution. They construct a dataset of 32 atomic tasks across three difficulty tiers, composed into three types of sequential task streams (correlated, orthogonal, and implicit intent) under two noise conditions. Two primary metrics are used: success rate (SR) and token consumption (T), where the trajectory of T across sequential task repetitions is the key signal of genuine evolution. They then empirically evaluate two leading agent frameworks, OpenClaw and GenericAgent, using this benchmark.
Results Both frameworks achieved 100% task success rate in static evaluation, but their token consumption differed by roughly sevenfold in aggregate — OpenClaw consumed 27,364K tokens across all tasks while GenericAgent consumed only 3,918K tokens, with differences reaching up to 31.2x on individual tasks. In sequential task analysis, GenericAgent showed genuine evolution: token consumption for one academic database retrieval task fell monotonically from 520K to 117K tokens. OpenClaw showed pseudo-evolution: its token consumption fluctuated without converging and collapsed on certain sequential tasks. These results confirm that success rate alone is insufficient and that sequential convergence of token consumption is the necessary criterion for detecting real learning.
- SCM: Sleep-Consolidated Memory with Algorithmic Forgetting for Large Language Models
Synthesis
Plain-language abstract This paper introduces SCM (Sleep-Consolidated Memory), a memory architecture for large language models that mimics how human brains store and forget information. Rather than growing an ever-larger database of raw conversation text, SCM encodes conversations into structured concepts, selectively strengthens important ones during simulated sleep cycles, and actively prunes low-value memories — enabling persistent, organized memory that stays manageable over time.
Motivation Current LLM memory approaches all have critical gaps: context windows are bounded and degrade with long input, vector databases grow without limit and never forget, and tiered storage systems like MemGPT lack any offline consolidation or biological forgetting mechanisms. None replicate how human memory actually works — a dynamic system that consolidates during sleep, prioritizes by importance, and actively prunes weak associations. SCM was designed to fill this gap by bringing neuroscience-inspired memory management to conversational AI.
Methodology SCM is built from five modules: a MeaningEncoder (using a local Llama 3.2 2B quantized model) that converts text into typed semantic concepts with 384-dimensional embeddings; a ValueTagger that assigns four-dimensional importance scores (novelty, emotional valence, task relevance, repetition frequency); a WorkingMemory buffer capped at seven items; a LongTermMemory stored as a NetworkX semantic graph backed by SQLite; and a SleepCycle module that runs NREM consolidation (Hebbian strengthening plus synaptic downscaling), REM dreaming (novel association generation), and value-based forgetting. The prototype was evaluated on a standardized suite of eight benchmark tests covering memory retention, consolidation, forgetting, graph traversal, latency scaling, and multi-session persistence.
Results Across all eight benchmark tests the prototype achieved perfect scores (1.00). It maintained 100% recall accuracy over ten-turn conversations while reducing memory noise by 90.9% through adaptive forgetting — pruning 45 of 50 noise concepts while preserving all 5 important ones. Memory search latency remained below one millisecond with hundreds of stored concepts. An ablation study showed that disabling the ForgettingModule caused the largest memory bloat (72 stored concepts vs. 24 in full SCM) and that disabling the ValueTagger dropped recall to 81.8%, confirming that multi-dimensional importance tagging is the most critical component for selective retention.
- Cooperative Memory Paging with Keyword Bookmarks for Long-Horizon LLM Conversations
Synthesis
Plain-language abstract This paper proposes 'cooperative paging', a method that helps AI chatbots handle very long conversations without losing track of earlier content. When a conversation grows too long to fit in the model's memory, old sections are replaced with short keyword summaries (about 8 tokens each), and the model is given a tool it can call to retrieve the full text of any summarized section when it needs it. The paper evaluates this approach on a standard benchmark of long real-world conversations and also runs a systematic study of design choices like page size and eviction strategy.
Motivation Large language models have a fixed context window, but multi-turn conversations can grow indefinitely. When old content must be discarded to make room, existing methods either force the model to guess what it is missing (which models do poorly), only work for narrow cases like file reads, or compress content irreversibly losing detail. There was no systematic study of how page boundary detection and eviction policy affect retrieval quality in this setting.
Methodology The authors built a cooperative paging system in which evicted conversation segments are replaced with minimal keyword bookmarks (e.g., '[p3: allergy, peanut, budget]') and the model is given a recall() tool to fetch full content on demand. They evaluated it on the LoCoMo benchmark (10 real multi-session conversations with 300+ turns each) across four models from three provider families (GPT-4o-mini, DeepSeek-v3.2, Claude Haiku, GLM5), comparing against five baselines including truncation, BM25 retrieval, and a search-tool baseline. They also ran a turn-by-turn paging simulator with 3,176 probes on synthetic data and 1,600 probes on LoCoMo to ablate five page-boundary strategies and four eviction policies (FIFO, LRU, LFU, Belady oracle), and tested six bookmark generation strategies.
Results Cooperative paging achieved the highest answer quality among six methods on LoCoMo across all four tested models, with statistical significance (p=0.017 vs. BM25, paired bootstrap). The ablation showed page granularity dominates eviction policy: coarse fixed-size pages (fixed-20) reached 96.7% recall accuracy while content-aware topic-shift paging collapsed to 56.7%. The model triggers recall() correctly 96% of the time, but selects the right page only 57% of the time when bookmarks are insufficiently distinctive, shifting the bottleneck from 'when to recall' to 'which page to recall'. The best bookmark strategy (llm-batch, single-call cross-page non-overlap keywords) improved end-to-end accuracy by 8.7 points on LoCoMo and 50 points on open-domain questions over the heuristic baseline; keyword specificity alone accounted for a 25 percentage-point accuracy difference in controlled probes.
- Memanto: Typed Semantic Memory with Information-Theoretic Retrieval for Long-Horizon Agents
Synthesis
Plain-language abstract Memanto is a memory system for AI agents that need to remember information across many conversations and tasks. Instead of the complex graph-based memory architectures most agent frameworks use, Memanto organizes memory into thirteen typed categories and retrieves relevant memories using a single, fast semantic search query — achieving top benchmark scores while being simpler and cheaper to run.
Motivation As AI agents move from answering single questions to carrying out long, multi-step tasks across many sessions, they need reliable persistent memory. Existing production memory systems — such as Mem0, Zep, and A-MEM — combine knowledge graphs with vector databases, which imposes heavy computational costs: every memory write triggers multi-second pipelines involving LLM-driven entity extraction and graph synchronization. The paper argues this 'Memory Tax' is unnecessary and that simpler architectures can match or beat graph-based systems in accuracy.
Methodology Memanto is built on Moorcheh's Information-Theoretic Search engine, a no-indexing semantic database that provides deterministic (exact-match rather than approximate nearest-neighbor) retrieval with sub-90-millisecond latency and zero ingestion delay. The memory layer uses a typed schema of thirteen predefined semantic categories, an automated conflict-resolution mechanism for contradictory memories, and temporal versioning. The system was evaluated on two established long-term memory benchmarks — LongMemEval and LoCoMo — using a five-stage progressive ablation study that isolated the contribution of retrieval-limit tuning, similarity-threshold calibration, prompt design, inference model selection, and the typed schema.
Results Memanto achieved accuracy scores of 89.8% on LongMemEval and 87.1% on LoCoMo, establishing state-of-the-art results among both vector-based and hybrid graph-plus-vector systems. These results were obtained using only a single retrieval query per lookup, with no ingestion cost and no graph infrastructure — outperforming all evaluated hybrid architectures while requiring substantially lower operational complexity.
- ZenBrain: A Neuroscience-Inspired 7-Layer Memory Architecture for Autonomous AI Systems
Synthesis
Plain-language abstract ZenBrain is a memory architecture for AI agents that draws on 130 years of cognitive neuroscience research to give language-model agents a structured, biologically grounded way to store, consolidate, and forget information across many sessions. It organizes memory into seven distinct layers — working, short-term, episodic, semantic, procedural, core, and cross-context — and coordinates them with fifteen neuroscience-inspired algorithms. The system is open-source and ships as composable npm packages with over 11,500 automated tests.
Motivation Current AI agent memory systems borrow metaphors from computer science — virtual memory paging, flat key-value stores, or structured note-taking — but none incorporate the well-validated principles of memory consolidation, forgetting, and reconsolidation studied in cognitive neuroscience for over a century. Without principled decay and consolidation, agents suffer 'conversational amnesia' and cannot maintain consistent personality or learning across sessions. A 2026 survey explicitly identified deeper neuroscience integration as a key open challenge in the field.
Methodology ZenBrain implements seven memory layers orchestrated by nine foundational algorithms plus six new Predictive Memory Architecture (PMA) components, including a four-channel NeuromodulatorEngine modeling dopamine, norepinephrine, serotonin, and acetylcholine dynamics; a prediction-error-gated ReconsolidationEngine; TripleCopyMemory with divergent decay dynamics; and a four-dimensional PriorityMap with an amygdala fast-path. The system was evaluated across ten experiments covering memory lifecycle management, retrieval benchmarks, and system-level ablation studies using three established benchmarks — LoCoMo, MemoryAgentBench, and MemoryArena — under a 15-algorithm ablation protocol with Wilcoxon tests over 10 seeds.
Results Under challenging conditions (decay=0.20, 50 days), 7 of 15 algorithms became individually significant with quality drops ranging from -25.5% to -93.1%; under stress conditions (decay=0.25, 60 days), 9 became critical (up to -93.7% degradation). The Simulation-Selection sleep loop achieved a 37% stability improvement (p < 0.005) with 47.4% storage reduction. TripleCopyMemory retained 0.912 mean memory strength at 30 days versus near-zero Ebbinghaus baselines, and the PriorityMap achieved NDCG@10 = 0.997 versus 0.680 for chronological ordering. On the LongMemEval-500 benchmark, ZenBrain held the highest mean rank across all 12 judge-system quality cells, with a three-judge mean of 0.545 against competitors letta (0.485), a-mem (0.414), and mem0 (0.394), reaching 91.3% of long-context-oracle accuracy at 1/106th the per-query token budget.
- STALE: Can LLM Agents Know When Their Memories Are No Longer Valid?
Synthesis
Plain-language abstract This paper introduces STALE, a benchmark that tests whether AI language model assistants can recognize when something they "remember" about a user is no longer true. The authors identify a specific failure mode called an implicit conflict, where a new piece of information makes an old memory invalid without directly contradicting it, and show that current AI systems handle this poorly.
Motivation Existing benchmarks for AI memory mostly test whether a model can retrieve a stored fact, not whether it can recognize when that fact has been superseded. Real assistant interactions unfold over time and a user's circumstances change; a model that confidently acts on stale beliefs can give harmful or irrelevant advice. No prior benchmark systematically evaluated this implicit-conflict failure mode, especially cases where one life change cascades to invalidate a structurally related but unstated belief.
Methodology The authors built STALE, a benchmark of 400 expert-validated conflict scenarios producing 1,200 evaluation queries across over 100 everyday topics, with dialogue contexts up to 150,000 tokens. Scenarios cover two conflict types: co-referential (the same attribute is updated) and propagated (a change in one attribute cascades to invalidate a different one). Each scenario is probed along three dimensions: State Resolution (does the model detect the outdated belief?), Premise Resistance (does it reject a query that presupposes the stale state?), and Implicit Policy Adaptation (does it act correctly without being told there was a conflict?). They evaluated frontier closed-source LLMs, open-source LLMs, and five memory-augmented frameworks, and proposed a prototype system called CUPMEM that performs explicit write-side state adjudication and propagation-aware memory search.
Results Even the best-performing evaluated model, Gemini-3.1-pro, achieved only 55.2% overall accuracy. Models frequently accepted outdated assumptions embedded in user queries and struggled especially with propagated (Type II) conflicts, where Premise Resistance scores were near zero across nearly all systems. Memory-augmented frameworks did not solve the problem: the strongest baseline (LightMem) scored 17.8% overall, and diagnostic analysis showed that updated evidence was retrieved 77.5% of the time yet still failed to govern the final answer, a gap the authors call the current-state adjudication gap. The prototype CUPMEM substantially outperformed all baselines, reaching 91% on State Resolution and 78% on Premise Resistance for Type I conflicts, demonstrating that explicit write-side state adjudication is a viable design direction.
- Adaptive Memory Crystallization for Autonomous AI Agent Learning in Dynamic Environments
Synthesis
Plain-language abstract This paper introduces Adaptive Memory Crystallization (AMC), a new framework for helping AI agents learn continuously across changing tasks without forgetting what they already know. It models each stored experience as being in one of three memory states — liquid (flexible), glass (transitional), or crystal (stable) — and uses a mathematically rigorous process to decide which memories to keep and which to let go.
Motivation AI agents deployed in open-ended settings like robotics or autonomous driving must keep learning new skills while retaining old ones, a challenge known as the stability-plasticity dilemma. Existing deep reinforcement learning agents use fixed-size experience-replay buffers that, when tasks shift, cause catastrophic forgetting as new learning overwrites prior knowledge. No principled framework had linked the dynamics of memory consolidation to formal guarantees on agent performance.
Methodology AMC models memory consolidation as a continuous stochastic process governed by an Itô stochastic differential equation (SDE) in which each experience's crystallization state evolves based on a multi-objective utility signal combining temporal-difference error, state-action novelty, and downstream value. The population-level behavior is captured by a Fokker-Planck equation with a closed-form Beta stationary distribution. The framework organizes memory into three buffers (Liquid, Glass, Crystal) with capacity fractions and phase-modulated learning rates derived from the SDE dynamics. Formal proofs establish well-posedness, convergence, Q-learning error bounds, and memory-capacity lower bounds. The system was evaluated on Meta-World MT50, Atari 20-game sequential learning, and MuJoCo continual locomotion benchmarks using 50-seed statistics with Holm-Bonferroni-corrected significance tests.
Results AMC consistently outperformed the strongest baselines across all three benchmark suites, achieving 34-43% improvements in forward transfer, 67-80% reductions in catastrophic forgetting, and a 62% decrease in memory footprint.
- Learning to Forget -- Hierarchical Episodic Memory for Lifelong Robot Deployment
Synthesis
Plain-language abstract This paper presents H2-EMV, a system that gives humanoid robots a manageable long-term memory of their own experiences so they can answer questions like 'Where did you put my keys?' or 'Why did the task fail?' The system learns over time which memories matter most to a particular user, selectively discards less relevant ones, and improves its recall accuracy based on user feedback.
Motivation Robots that operate continuously accumulate vast streams of sensory and event data that quickly exceed storage and compute limits, making real-time question answering over past experiences impractical. Existing episodic memory systems for robots either grow without bound or use fixed relevance criteria, neither of which adapts to what individual users actually care about remembering.
Methodology The authors build on a prior hierarchical tree-based episodic memory representation, extending it with three additions: online incremental construction of the memory tree as new events arrive, a decay-based forgetting mechanism in which each memory node is assigned a lifetime and an LLM judges its relevance for retention when it expires, and feedback-driven learning of natural-language relevance rules that update when a user asks about something that was already forgotten. The system is evaluated on simulated household task recordings from the TEACh dataset and on 20.5 hours of real-world recordings from the humanoid robot Armar-7.
Results H2-EMV reduces memory size by 45% and query-time compute by 35% compared to a non-forgetting baseline while maintaining question-answering accuracy. Performance improves substantially across interaction rounds: accuracy in second-round queries increases by 70% relative to the first round, showing that the system successfully adapts to user-specific priorities after only one or a few feedback instances.
- Evolve: A Persistent Knowledge Lifecycle for Small Language Models
Synthesis
Plain-language abstract Evolve is a system that pairs a small (2–7 billion parameter) local language model with an external knowledge store that persists, grows, and improves over time. Rather than fetching raw document chunks at query time, Evolve builds a store of semantically coherent knowledge sections compiled by larger teacher models; those sections are staged, consolidated offline, and refreshed when they become stale. The result is a small model that answers questions far more accurately than it could from its own training weights alone.
Motivation Large language models bake factual knowledge into their parameters during training, making that knowledge frozen, impossible to selectively update, and prone to hallucination. Standard retrieval-augmented generation (RAG) partly addresses this but still suffers from chunk-boundary mismatch, static corpora that fail on out-of-distribution queries, retrieval noise, and an opaque entanglement between what the model knows internally and what was retrieved—making the knowledge base impossible to audit or update independently of the model weights.
Methodology Evolve externalizes all factual knowledge into a persistent store of semantically bounded sections compiled by large teacher models at natural conceptual boundaries. Newly acquired sections enter a staging buffer, are consolidated offline via teacher-mediated merging and pruning (analogous to biological sleep consolidation), and are refreshed inline when they expire. A 2B-parameter local model handles classification and retrieval-augmented generation; large teacher models are invoked only for knowledge operations. The system supports two generation modes—suppress (strict grounding on retrieved sections only, for auditability) and augment (sections plus parametric fallback). Evaluation used 750 benchmark queries spanning custom specialist questions, NaturalQuestions, and TriviaQA.
Results Augmenting the 2B model with Evolve raised accuracy from a 20–33% parametric baseline to 60–84%, a gain of 40–52 percentage points across benchmarks. Teacher model invocations were reduced by more than 50% through cross-query knowledge reuse. Post-consolidation compressed the knowledge store by 31–33.5% across three independent benchmarks while preserving accuracy. Section-based retrieval outperformed conventional chunk-based retrieval by 5–9 percentage points across every lifecycle condition tested.
- Time is Not a Label: Continuous Phase Rotation for Temporal Knowledge Graphs and Agentic Memory
Synthesis
Plain-language abstract This paper introduces RoMem, a plug-in module that gives AI agents better long-term memory by treating time as a geometric property rather than just a timestamp. Instead of erasing old facts or asking a language model to decide what to keep, RoMem rotates outdated facts out of alignment in a mathematical space so that current information naturally rises to the top without deleting history.
Motivation Knowledge graph memory systems used by AI agents face a fundamental problem when facts change over time: they either overwrite old information and lose historical context, or rely on expensive language-model calls at every update to decide what to discard. A simpler recency-sorting fallback silently buries permanently true facts (such as a person's birthplace) beneath newer but irrelevant entries, creating what the authors call the static-dynamic dilemma.
Methodology RoMem models time as a continuous phase rotation in complex vector space rather than a discrete timestamp. A pretrained Semantic Speed Gate reads each relation's text embedding and outputs a per-relation volatility scalar between 0 and 1, learned from data so that evolving relations rotate fast while persistent ones remain stable. As time passes, dynamic facts rotate out of geometric alignment with the query vector, causing temporally correct facts to outrank contradictions without any deletion. The memory is strictly append-only, and the language model receives a clean context window ranked by geometric proximity.
Results On the temporal knowledge graph completion benchmark ICEWS05-15, RoMem achieves 72.6 MRR, a state-of-the-art result. Applied to agentic memory, it delivers 2 to 3 times higher MRR and answer accuracy on heavy temporal reasoning (MultiTQ), dominates a hybrid reasoning benchmark (LoCoMo), preserves static memory with zero degradation (DMR-MSC), and generalizes zero-shot to unseen financial domains (FinTMMBench).
- A-MEM: Agentic Memory for LLM Agents
Synthesis
Plain-language abstract This paper introduces A-MEM, a memory system for AI agents powered by large language models that can dynamically organize and update its own knowledge without needing predefined rules or structures. Instead of storing memories in a fixed schema, A-MEM creates richly annotated notes for each new experience and automatically links them to related past memories, allowing the memory network to evolve over time.
Motivation Existing memory systems for LLM agents require developers to hardcode when and how memories are stored and retrieved, which limits how well they adapt to new tasks or long-running interactions. Even systems that use graph databases rely on rigid, predefined schemas that cannot forge new connections as an agent's knowledge grows, leaving a gap for a flexible, self-organizing memory architecture.
Methodology A-MEM represents each memory as a structured note containing the original interaction content, a timestamp, LLM-generated keywords, tags, a contextual description, a dense embedding vector, and a set of links to related memories. When a new memory is added, the system uses an LLM to generate semantic attributes for it, retrieves the top-k most similar historical memories via cosine similarity, and autonomously decides whether to create links and whether to update the contextual representations of existing memories. The system was evaluated on the LoCoMo long-term conversational dataset using six foundation models (including GPT-4o, GPT-4o-mini, Llama 3.2 1B/3B, and Qwen2.5 1.5B) across five question-answering categories (single-hop, multi-hop, temporal, open-domain, and adversarial), with F1 and BLEU-1 as metrics and four competitive baselines for comparison.
Results A-MEM consistently achieved the best average ranking across all six foundation models tested, outperforming baselines including LoCoMo, ReadAgent, MemoryBank, and MemGPT on the LoCoMo dataset. For example, with Llama 3.2 3B, A-MEM reached an F1 of 45.85 on multi-hop questions compared to the next-best baseline score of 25.52, and achieved top-1 average ranking across most model configurations while using substantially fewer tokens than full-context approaches. T-SNE visualizations further showed that A-MEM produces more coherent, clustered memory embeddings compared to a baseline without link generation or memory evolution.
- EvolveMem: Self-Evolving Memory Architecture via AutoResearch for LLM Agents
Synthesis
Plain-language abstract EvolveMem is a memory system for AI agents that can improve its own retrieval strategy over time, without human intervention. Most existing memory systems update what they remember but keep the rules for finding relevant memories fixed forever. EvolveMem breaks that limitation by treating the retrieval configuration itself as something that can be automatically researched and improved.
Motivation Long-running AI agents need persistent memory across sessions, but all existing systems freeze their retrieval infrastructure at deployment — the scoring functions, fusion strategies, and answer-generation policies never change even as the stored memory grows from dozens to hundreds of heterogeneous records. Different types of questions require different retrieval strategies, and a fixed configuration cannot optimally serve factual lookups, temporal reasoning, and multi-hop inference simultaneously.
Methodology EvolveMem runs a four-step closed-loop evolution cycle: Evaluate, Diagnose, Propose, and Guard. In each round, an LLM-powered diagnosis module reads per-question failure logs, identifies root causes, and proposes targeted adjustments to a structured action space covering scoring weights, fusion modes, context budgets, and answer-generation style. A guarded meta-analyzer applies accepted changes with automatic revert-on-regression and explore-on-stagnation safeguards. The underlying memory store combines lexical (BM25), semantic, and structured-metadata retrieval views, and the system was evaluated on the LoCoMo and MemBench benchmarks using GPT-4o as the backbone.
Results On LoCoMo, EvolveMem outperforms the strongest published baseline by 25.7% relative and improves 78.0% relative over the minimal baseline (F1 rising from 30.5% to 54.3% across seven evolution rounds). On MemBench it exceeds the strongest baseline by 18.9% relative. Configurations evolved on LoCoMo transfer zero-shot to MemBench and, when continued there, reach 79.2% F1 — outperforming a natively evolved MemBench configuration by 16.6% relative, with positive rather than catastrophic transfer. Three new configuration dimensions (entity-swap retrieval, query decomposition, and answer verification) were discovered autonomously by the diagnosis module from failure logs, not pre-specified by the researchers.
- Lifelong Learning of Large Language Model based Agents: A Roadmap
Synthesis
Plain-language abstract This paper is a survey that maps out how to give AI language model agents the ability to keep learning over time — accumulating new knowledge without forgetting what they already know. It organizes the key building blocks of such agents into three parts: how they take in information from the world, how they store and retrieve what they have learned, and how they act on that knowledge in changing environments.
Motivation Current large language model agents are static after training: their knowledge is frozen, and they cannot adapt to new tasks or environments without being retrained from scratch. This is a critical gap because real-world applications — from household robots to interactive assistants — require agents that can continuously encounter new situations, integrate new knowledge, and still remember prior experience. The core technical obstacle is the stability-plasticity dilemma: systems either forget old knowledge when learning something new (catastrophic forgetting) or become too rigid to learn at all (loss of plasticity).
Methodology The authors conducted a systematic literature survey, organizing techniques for lifelong learning in LLM-based agents around three modules: a perception module for integrating multimodal inputs (text, images, sensory data), a memory module for storing and retrieving evolving knowledge, and an action module for grounded interactions with dynamic environments. The survey is structured around seven research questions covering architectures, forgetting mitigation strategies, evaluation benchmarks, real-world application scenarios, and open challenges. Relevant literature is collected and made available through an accompanying GitHub repository.
Results The survey is the first to systematically cover the intersection of lifelong learning and LLM-based agents. It provides a roadmap identifying how perception, memory, and action components collectively enable continuous adaptation, outlines evaluation metrics and benchmarks for assessing lifelong performance, catalogs real-world application domains including gaming, web browsing, household tasks, and autonomous robotics, and highlights key open problems and future research directions in this rapidly growing field.
- Neuron-level Balance between Stability and Plasticity in Deep Reinforcement Learning
Synthesis
Plain-language abstract This paper addresses how AI agents trained with deep reinforcement learning can learn new tasks without forgetting old ones. The authors identify individual neurons in the neural network that encode task-specific skills, and use this insight to build a method that selectively protects those neurons during learning. The approach, called NBSP (Neuron-level Balance between Stability and Plasticity), is tested on standard robotics and game-playing benchmarks.
Motivation Deep reinforcement learning agents struggle when they need to learn a sequence of tasks: improving at a new task tends to overwrite knowledge needed for prior tasks, a problem known as catastrophic forgetting. Existing methods that try to balance stability (retaining old skills) and plasticity (acquiring new ones) operate at the network level without fine-grained control over which neurons matter most, leaving the dilemma largely unresolved.
Methodology The authors first observed that after training, specific neurons in the network show activation patterns that reliably predict task success, identifying them as carriers of task-specific skill knowledge. NBSP builds on this by defining and detecting these 'RL skill neurons' through a goal-oriented criterion, then applying gradient masking to protect those neurons from being overwritten and using experience replay to reinforce existing skills while the agent adapts to new tasks. Experiments were conducted on the Meta-World robotic manipulation benchmark and Atari games, using a cycling task setup to evaluate both retention of old skills and acquisition of new ones.
Results NBSP significantly outperforms existing approaches at balancing stability and plasticity on the Meta-World and Atari benchmarks. The paper also introduces the concept of RL skill neurons as a contribution, providing a principled, neuron-level mechanism for continual learning in deep reinforcement learning agents.
- NeuSymMS: A Hybrid Neuro-Symbolic Memory System for Persistent, Self-Curating LLM Agents
Synthesis
Plain-language abstract NeuSymMS is a memory system for AI assistants that lets them remember and reason about users across multiple conversations. It combines a neural language model for extracting facts from dialogue with a rule-based expert system (CLIPS) that organizes, deduplicates, and updates those facts automatically. The result is a compact, auditable memory layer that avoids flooding the AI with raw chat history while still keeping track of what it knows about each user.
Motivation Most deployed AI assistants treat conversation history as temporary context that is discarded after each session, or they naively accumulate ever-growing logs. Existing approaches such as full-log retrieval, periodic summarization, and simple key-value stores handle contradictions poorly and cannot gracefully update beliefs when a user's job, location, or preferences change. There was no practical, production-ready system that combined the language understanding of neural models with the deterministic consistency rules needed for trustworthy, auditable long-term memory.
Methodology NeuSymMS sits between user conversations and the language model. On the write path after each turn, a lightweight LLM (such as gpt-4.1-mini) extracts candidate facts as subject-relation-value triples from the dialogue at low temperature. These candidates are then passed to a CLIPS-based expert system that classifies them into nine semantic categories, detects contradictions with stored facts, retracts stale beliefs, and decides whether each fact belongs in short-term or long-term memory based on explicit lifecycle rules and access counts. Facts are stored in a PostgreSQL database with three-tier scoping (user, agent, flow) to prevent cross-entity contamination. On the read path, relevant user-scoped facts are formatted into a concise text block and injected into the LLM's system prompt. The system is implemented using Django, CLIPSPy (Python bindings for CLIPS 6.4), and LiteLLM as a provider-agnostic gateway.
Results The paper presents a working architecture deployed inside the Nexa platform, with a REST API and a user-facing Memory UI for viewing, editing, and clearing stored facts. The design achieves zero-cost, low-latency classification by running the CLIPS engine in-process with millisecond overhead and no external dependencies, and avoids expensive vector search at inference time by injecting directly formatted text. The system degrades gracefully if any component fails—agents continue without memory rather than crashing. A full quantitative evaluation against benchmarks such as LoCoMo and LongMemEval and baselines such as Mem0 and MemGPT is planned as future work; no benchmark numbers are reported in the current paper.
- Learning What to Remember: Observability-Safe Memory Retention via Constrained Optimization for Long-Horizon Language Agents
Synthesis
Plain-language abstract OSL-MR is a framework for deciding which memories a long-horizon language agent should keep when its storage budget is smaller than everything it has seen. It poses the choice as an optimization problem that weighs the future value of evidence against the cost of losing it, and learns the policy from logged interactions using only signals that would actually be available when the agent runs.
Motivation Long-horizon agents accumulate more observations, reasoning traces, and retrieved facts than fit in context, so retention is a resource-allocation problem. Prior systems score memories with heuristics, retrieval objectives, or learned compression, but treat each retention decision locally and never model its long-term consequences — and many depend on signals such as gold evidence or answer correctness that are only knowable after the fact and so would not exist at deployment.
Methodology Retention is cast as a constrained multi-step stochastic optimization: at each step the agent selects a subset of memories under a hard size budget, and a per-step reward credits covered evidence while charging storage, miss penalty, reacquisition delay, and stale-information use. A strict online/offline split separates online-observable inputs (query, memory metadata, interaction history) from offline-available supervision (gold evidence, answer text, freshness) used only for training. OSL-MR pairs a Mixed-Score heuristic — a deployable cold-start baseline and inductive prior — with an evidence learner trained offline on gold-evidence membership labels, then frozen and deployed on online features alone.
Results On LoCoMo and LongMemEval, OSL-MR beats recency, Generative-Agents-style scoring, behavior cloning, and the Mixed-Score heuristic across budgets, with the largest gains under tight budgets (LoCoMo budget 128: F1 0.302 and reward 305 vs 0.069/132 for Mixed-Score). It uses the budget more efficiently, running well below full occupancy while baselines saturate it, and reward rankings track precision and F1 exactly. Ablating the Mixed-Score prior cuts precision (0.529→0.421 on LongMemEval budget 256) while leaving recall nearly unchanged, showing the prior steers the learner away from low-utility memories.
- TokenPilot: Cache-Efficient Context Management for LLM Agents
Synthesis
Plain-language abstract TokenPilot is a context-management framework for LLM agents in long-horizon sessions that reconciles cutting token count with preserving backend KV prompt-cache continuity. The authors observe that prior pruning, compaction, and memory-eviction methods mutate the prompt layout, which shatters prefix continuity and triggers cache-miss pre-fill penalties that override the financial savings from text reduction. TokenPilot operates at two granularities: a global Ingestion-Aware Compaction harness that stabilizes the prompt prefix and strips open-world tool-output noise at the ingestion gate, plus a local Lifecycle-Aware Eviction that defers purging context segments until their residual task utility expires, on a conservative batch-turn schedule.
Motivation Continuous multi-turn agent interactions accumulate verbose execution traces that inflate sequence length and per-turn inference cost. Existing content-reduction methods reduce tokens but constantly mutate input boundaries, causing prefix mismatches and KV cache invalidation; the resulting pre-fill penalties can exceed the text-reduction savings. The core insight is a trade-off between text sparsity and prompt-cache continuity that must be reconciled, by safeguarding physical prefix continuity during observation ingestion and deferring structural eviction until residual utility expires.
Methodology Messages are partitioned into internal intentional messages (high utility) and open-world environmental feedback (lower density unless content-hash access frequency exceeds a threshold). A canonicalization operator enforces a byte-identical prefix across turns; environmental messages are reduced to structural previews with full payloads stored in a content-hash-indexed artifact registry and recallable via a recovery tool. Lifecycle-Aware Eviction tracks segments through active/completed/evictable states using a zero-shot estimator run every B=3 turns over a compressed history view; only evictable segments (zero residual utility) are purged in a single pass. Evaluation is on PinchBench and Claw-Eval in isolated and continuous modes with GPT-5.4-mini as backbone, against compression baselines (LLMLingua-2, SelectiveContext, Keep-Last-N) and paging/summarization baselines (MemoBrain, MemOS, others); cache hit/miss token counts are read directly from provider API metadata.
Results TokenPilot achieves the lowest inference cost while maintaining competitive accuracy: isolated mode $3.22 on PinchBench and $2.27 on Claw-Eval (61% and 56% reductions vs Vanilla); continuous mode score 81.3 at $2.79 on PinchBench and $10.58 vs Vanilla's $81.52 on Claw-Eval (61% and 87% reductions). Ablation on continuous PinchBench: Ingestion-Aware Compaction cuts cost $7.24 -> $4.22 (cache-miss tokens 5.943M -> 1.589M); adding Lifecycle-Aware Eviction reaches $2.79 (cache-read tokens 26.716M -> 8.551M, a 65% drop). Prefix stabilization raises macro cache hit rate from 38.7% to 79.2% on PinchBench and 67.2% to 83.1% on Claw-Eval. Removing the recovery tool drops accuracy 80.9 -> 77.1; B=1 eviction is too aggressive, B=infinity bloats context, B=3 is the chosen balance.
- Memory Depth, Not Memory Access: Selective Parametric Consolidation for Long-Running Language Agents
Synthesis
Plain-language abstract Long-running language agents accumulate more history than fits in working context, and the usual fix is retrieval — store past events outside the model and fetch a relevant subset at query time. This paper argues retrieval only answers what can be fetched (memory access) and not what should keep shaping behavior after the working context is unloaded (memory depth). It introduces the loop-drift protocol, a controlled stress test where the retrieval index stays intact but working context is cleared, so goal-conditioned behavior must persist through long-loop interference without the relevant text being reinserted. It evaluates EVAF, a surprise- and valence-gated LoRA consolidation mechanism that writes only behavior-relevant events into a small adapter. Across GPT-2, TinyLlama, and Mistral-7B, retrieval wins shallow factual recall while EVAF wins goal persistence and post-unload recovery with only 2–3 parametric writes per 200 events, and the paper shows selective consolidation factorizes into two separable controls — selection and actuation.
Motivation Memory access and memory depth are different problems. A shallow memory is one the system can retrieve or attend to; a deep memory changes future behavior — it persists through interference, survives context unload, and affects choices without being reinserted as text. Retrieval is indispensable for fetched facts, but a long-running assistant also needs durable goals, preferences, and constraints that are not merely fetched facts. Existing long-memory benchmarks (LongMemEval, LoCoMo) emphasize conversational recall, temporal access, and knowledge updates, and do not isolate the post-unload setting where retrieval remains available but behavior must continue without the relevant text in context. The paper's claim is narrow and explicit: memory depth can be probed by post-unload goal-conditioned behavior, and consolidation factorizes into selection and actuation — it does not claim universal memory accuracy, SOTA retrieval, or complete deletion/update validity.
Methodology Loop-drift protocol: synthetic per-user streams of 200 events (10 users/run) mixing stable goal/preference reminders, off-topic distractors, transient opposite requests, conflicts, sibling-user contamination, and scheduled factual notes; four probe layers — shallow episodic (recent fact), noisy episodic (old fact after same-key interference), parametric tendency (does a stable goal still shape behavior after long interference), and post-unload recovery (re-probe the goal immediately after a context unload, with the retrieval index intact but working context cleared). The RAG baseline stores all events in a durable embedding index (top-3 cosine) that context unload does not clear, so any EVAF goal-layer advantage is not a trivial 'RAG forgot' artifact. EVAF mechanism: per-event surprise (token negative log-likelihood) and valence (embedding similarity to the user's durable goal/preferences) combine into an admission gate; events above threshold enter a buffer, and when the buffer fills a LoRA adapter is updated on the buffer plus replay from prior consolidated events, with an L2 anchor as a drift guard. Model controls: GPT-2 and TinyLlama (four-seed means) plus Mistral-7B. Selection is isolated with a matched-random gate (same write count and online write dynamics, random admitted events). Actuation is isolated with fixed-inner controllers (fixed-1/2/3 inner LoRA steps using the same gate). A routed EVAF+RAG variant routes factual probes to retrieval and goal probes to EVAF. Public Memora event streams serve as an external boundary diagnostic for stale-memory invalidation, tested with McNemar's test.
Results Depth flip: RAG is strongest on recent explicit facts (short-fact accuracy 0.956–0.973) and near-useless on goals; EVAF is near chance on short facts but much stronger on the goal layer — on GPT-2 EVAF reaches 0.904 goal / 0.900 post-unload vs RAG 0.398/0.394, and on TinyLlama 0.833/0.812 vs RAG 0.396/0.394 — at only 2.4–2.6 writes (L2 drift ~21–29) vs RAG's 0 writes. Writing everything is not enough: Naive-LoRA writes all 200 events at far higher drift (~67 TinyLlama, ~119 GPT-2) and still fails the goal layer; at 7B indiscriminate writing is actively harmful — Naive-LoRA goal persistence collapses to 0.333±0.047, below the 0.500 chance baseline. Selection is not sparsity: on GPT-2 EVAF beats a matched-random gate of equal write count on goal and post-unload in all four seeds (mean 0.790/0.763 vs 0.590/0.619); TinyLlama is weak/mixed, so the selection signal is not monotonic in model scale. Actuation is a separable, model-dependent factor: fixed-inner audits show smaller inner steps cut drift and improve goal/post (Mistral-7B five-step 0.354/0.306 -> Fixed-2 0.796/0.775 -> Fixed-1 0.919/0.938), but Fixed-1 contamination saturates at 1.000 on Mistral, so high actuation trades selectivity for goal strength. Asymmetric coupling: under a miscalibrated five-step actuation at 7B the matched-gate comparison reverses, yet EVAF still keeps lowest sibling contamination (0.787±0.041) — selection stays semantically active while its translation into goal behavior fails. Boundary: on Memora, EVAF improves forgetting-absence only 91/222 to 95/222 (p=0.57, not significant), so append-only selective consolidation does not solve stale-memory delete/update validity, which the paper leaves to validity-gating or reconsolidation.
- Temporal Validity in Retrieval Memory: Eliminating Stale-Fact Errors for AI Agents over Evolving Knowledge
Synthesis
Plain-language abstract MemStrata is a memory system for AI agents that keeps track of when facts become outdated. Instead of just retrieving whatever text looks most similar to a query, which fails when an old and a new fact look nearly identical, it uses a deterministic rule to detect when a new fact supersedes an old one and retires the stale version.
Motivation Retrieval-augmented memory has no concept of time: when a fact changes (a renamed function, an updated config value, a new port number), both the old and new versions sit in the store with near-identical embeddings, and the agent can't tell which is current. The authors show this isn't a tuning problem: on a calibrated dataset, cosine similarity separates contradictions from duplicates at only 0.59 AUROC (near chance), because a value-flip edit sits textually closer to the original than a genuine rephrasing does.
Methodology MemStrata's write path first tries a deterministic (subject, relation, object) triple match: if an incoming fact shares a key with a stored one but asserts a different value, the old fact is retired (not deleted) in a bi-temporal ledger and the new one is stored as current. Non-triple prose falls back to a similarity-plus-LLM-judge gate. The system is evaluated on six local, deterministic benchmarks (two static, four marker-free evolving: code mutation, config migration, dependency bumps, API evolution) with a 7B model on consumer hardware.
Results MemStrata matches RAG on static recall (no cost) and reaches 0.95-1.00 accuracy on evolving-knowledge benchmarks where RAG reaches only 0.20-0.47. When forced to answer, plain RAG serves the superseded value 15-40% of the time; MemStrata drives this to ~0%. It also runs at ~2.1s retrieval latency versus ~16-18s for LLM-reranking/verification baselines, since no LLM sits on the read path.
- Can Agent Memory Systems Track Evolving State?
Synthesis
Plain-language abstract A benchmark and method for a memory capability separate from recall: keeping track of which version of a fact is currently in force after it has been revised across sessions. The benchmark, StateMemBench, generates each scenario as a symbolic program of state operations so the correct answer is computed by replay and the specific way a lazy reader would get it wrong is known in advance. The method, StateMem, parses each turn into structured state units with typed dependency links, then handles supersession and staleness deterministically rather than with an LLM.
Motivation Existing memory systems and benchmarks optimize recall of relevant facts, but as agents run longer, facts, constraints and decisions get revised, and an answer must reflect the current state rather than a superseded one. The authors call the failure state drift: the relevant fact is present in the assembled context, but the agent acts on a stale or incomplete version of it. This is distinct from dialogue state tracking, which prescribes a slot-value representation and evaluates it directly over cooperative dialogues that accumulate a goal monotonically; here state is whatever a system must maintain to answer correctly, evaluation is purely behavioral, and revisions are adversarial across sessions. Some concurrent work centers state, but the authors argue none cleanly isolates state tracking from the other errors it co-occurs with.
Methodology The authors first define and label drift on existing benchmarks, assigning a failure to drift only after excluding retrieval, comprehension, schema and reasoning readings, dropping unassignable points, and cross-checking with two judge passes, a cross-family judge and two human annotators. They then build StateMemBench: each scenario is a symbolic event program of typed operations over ground, derived and declared state; the gold answer comes from deterministic replay; a family of executable lazy reader policies is run against the replay, and a scenario is admitted as a trap when policies disagree, with the disagreeing set forming its failure-mode signature (status, salience, sequence, compound, plus anti-trap controls). Programs are grounded in public data for surface vocabulary and rendered into multi-session dialogue by a strong LLM, then programmatically verified for fact placement and phrase leakage. Probes are closed-pool: an unseen pool of three to four options holds the gold answer, the targeted policy's drift answer and neutral distractors. StateMem itself runs a per-turn TurnEncoder producing state units (id, content, priority, source, deps), a deterministic update stage applying supersessions and marking dependents needs_recheck by dependency-graph traversal, and a single answer-time call over the assembled active state. A wrapper variant applies the same trace-then-resolve structure as a prompt-level transformation of any backend's answer call, evaluated against a length- and cost-matched generic-extraction control.
Results Drift leads the confirmed failure distribution on several existing benchmarks (63.5% on MemoryArena-shopping, 44.4% on LongMemEval oracle where retrieval is perfect by construction, 10 of 16 on tau-squared-bench-Z) but is not universal, falling to 19.0% on MemoryArena-travel. On StateMemBench, long-context is not the strong baseline it is on recall tasks: the best long-context model reaches 0.277 and same-backbone long-context 0.149. StateMem reaches 0.363 on DeepSeek-V4-Flash, 1.8x the best memory system and 2.4x same-backbone long-context, and 0.233 on Qwen-3.5-9B, 1.6x the best memory system, both significant by paired McNemar at p < 0.001; GraphRAG at 0.224 is statistically level on Qwen. Ablations put supersession marking as the largest single component and show dependency propagation over-fires on Set B anti-traps by 12.5 points, so removing it leaves DeepSeek slightly better. Drift-rate analysis shows the memory layer barely changes outcomes on a weak answerer, where every arm drifts at 61 to 66%, and separates on the stronger backbone, where StateMem's drift rate falls 15 points and correct answers rise by 42 while long-context, Mem0 and BM25 move by 1 to 3 points. The wrapper improves every one of six backends on both benchmarks, adding 31.7 to 66.6 points on StateMemBench with 15.0 to 31.7 attributable to state structure over the matched control, significant in all twelve cells. State tracking does not cost recall: StateMem also leads memory systems on LongMemEval (0.656 on DeepSeek) and LoCoMo (0.592), with margins concentrated on temporal-reasoning and knowledge-update question types. The authors note StateMem mirrors the policy family behind the traps, so its StateMemBench margins should be read as an upper bound.
No papers match this search and theme.
A reading path
Start here and read in order; the path moves from foundations toward the open edge.
Foundations
Forgetting
Companion podcast
11 episodes walking this map as an argument: what each study measured, where they disagree, and what that leaves open. Listen inline or read the transcript.
The Agentic Memory Reading Path
- 1. Foundations
The field had a vocabulary problem: everyone was building agents, nobody agreed on what the parts were called. A shared framework for what agent memory actually is.
Read transcript
The agentic memory reading path, one of five. In 2023, a group of researchers at Princeton noticed that the field of language agents had a vocabulary problem.
Everyone was building agents. Nobody agreed on what the parts were called. One team’s memory was another team’s context, was a third team’s scratch pad. So they did something unfashionable in a field obsessed with the next benchmark. They stopped and they drew a map. That map is where this series begins.
Welcome to a five-part deep dive on agentic memory, following a reading path that runs from the founding taxonomy through the systems people actually deploy into procedural skills, the measurement crisis, and finally forgetting.
This is episode one, Foundations. How we learn to talk about memory, why the field keeps splitting into camps, and what it even means to evaluate an agent that remembers. A quick orientation, because the shape of this series matters.
We are walking… We are walking a curated reading path through the agentic memory literature, 13 papers in six stages, cross-checked against the primary sources and against what is actually shipping in industry right now.
Today, Foundations, we lean on three works. The CoALA Taxonomy from 2023, a 2026 survey called From Storage to Experience, and a 2025 survey on how we evaluate agents at all. Three papers, one job, give you the scaffolding so the rest of the series has somewhere to hang. And here is the thing to hold onto from the start.
Memory is not a feature you bolt onto an agent. It is the thing that turns a stateless text generator into something that accumulates. A model without memory answers each question as if it were the first.
A model with memory has a past, and a past is what makes planning, personalization, and learning possible. The whole field is an argument about how to give an agent a past it can actually use.
Let us start with the math. The founding document for this series is a 2023 paper by Theodore Sumers, Shunyu Yao, Karthik Narasimhan, and Thomas Griffiths titled Cognitive Architectures for Language Agents. CoALA, for short. It has accumulated something like 160 citations, which in this field is a landmark, and its move is clever. Instead of inventing a new framework from scratch, the authors reached back into the history of cognitive science and symbolic artificial intelligence, the production systems, and cognitive architectures of the 1980s and 90s, and they used that older, richer tradition to organize the chaos of modern language agents. CoALA describes any language agent with three pieces. First, modular memory components.
Second, a structured action space, split into internal actions that operate on the agent’s own memory and external actions that operate on the world. And third, a generalized decision-making procedure, a loophole, a loop that chooses which action to take next.
That sounds simple. The power is in the memory decomposition, because this is where the vocabulary of the whole field comes from.
CoALA borrows the classic cognitive science split, working memory, the live information for the current decision, what is in the context window right now. Episodic memory, the agent’s record of specific past experiences, what happened, when, in what order.
Semantic memory, general knowledge and facts, decoupled from any single episode. And procedural memory, the skills and routines the agent knows how to execute, including, in a nice twist, the agent’s own code and prompts. Those four categories, working, episodic, semantic, procedural, are the words you will hear in every paper in this series.
When a vendor tells you their product has episodic and semantic memory, they are speaking CoALA, whether they cite it or not. It is worth dwelling on working memory specifically, because it is the hub every time you use CoALA. In CoALA’s framing, working memory is the central exchange. The decision procedure reads from it, the long-term stores write into it, and get read back through it, and the action space operates on it. Episodic, semantic, and procedural memory are the long-term stores. Working memory is the desk where the agent actually does its thinking. That distinction, a small live workspace versus large, persistent archives, is the same one that operating memory actually does its thinking. That distinction is what operating systems make between RAM and disk, and it is no accident that one whole culture in this field, the one we’ll meet in the next segment, thinks about memory in exactly those operating system terms. The second half of CoALA is just as important and gets cited less, the structured action space and the decision procedure. CoALA splits an agent’s actions into two kinds. Internal actions operate on memory, retrieval, which reads from long-term stores into working memory, reasoning, which processes what’s in working memory and writes results back, and learning, which writes new content into the long-term stores. External actions operate on the world, calling tools, hitting APIs, moving in an environment, and wrapping all of it is a generalized decision-making loop that each cycle chooses the next action, internal or external. Why does this matter for memory? Because it tells you memory is not a passive database the agent occasionally queries. Reading and writing memory is one of the most obvious actions the agent decides to take on the same footing as calling a tool. The agent has to learn when to remember and when to retrieve, not just how. That reframing memory operations as deliberate actions is the seed of the agentic memory idea we’ll see become a whole research direction in episode 2. The choice to reach back into symbolic AI was not nostalgia, and it’s worth understanding why. In the 1980s and 90s, there were many new architectures, systems like SOAR and ACT-R that tried to model general intelligence as an explicit machine, a long-term memory of production rules, a working memory of current state, and a cycle that matched rules against state and fired the best one. Those systems were brittle and hand-built, and the deep learning wave largely swept them aside. But they had spent decades thinking rigorously about exactly the questions language agents are now rediscovering. How do you analyze different kinds of memory? How do you decide what to do next? How does new knowledge get written down? CoALA’s insight was that language models had quietly solved the part the old systems were worst at while reintroducing the parts the old systems had carefully worked out in an ad hoc, reinvented-every-paper form. So the move is take the hard-won structure of cognitive architectures and drop a language model in the old skeleton, the new muscle. What CoALA gave the field was a shared coordinate system. You could now look at any agent and ask precise questions. Where does this system keep episodic traces? How does it move something from working memory into long-term semantic memory? What are the internal actions that read and write each store? The paper used its own framework to survey the existing work and the grid, the things nobody had built yet. That is what a good taxonomy does. It does not just describe, it reveals the gaps. A taxonomy tells you the parts. It does not tell you the story of how the field is moving. For that, jump forward to 2026 and a survey by Jinghao Luo and colleagues with a title that is itself a thesis, From Storage to Experience A Survey on the Evolution of LLM Agent Memory Mechanisms. This is a survey translating between two cultures that barely talk to each other. One culture treats memory as an operating systems problem. Paging, caching, eviction, context windows as RAM, external stores as disk. This is the MemGPT lineage, memory as systems engineering. The other culture treats memory as a cognitive science problem. Consolidation, forgetting curves, the hippocampus, how human remembering actually works. Because each camp keeps reinventing the other’s ideas under different names. So they propose a single evolutionary arc. Three stages. And it is genuinely useful for thinking about where any given system sits. Stage one is storage. Trajectory preservation. You just keep the record of what happened. Raw logs, full transcripts, the agent’s history written down somewhere it can be retrieved. Stage two is reflection. Trajectory refinement. The agent does not just store the raw trace, processes it, summarizes it, extracts what mattered, critiques its own past behavior. Stage three, the frontier, is experience. Trajectory abstraction. The agent generalizes across many past trajectories into reusable, transferable knowledge that changes how it acts in genuinely new situations. Storage to reflection to experience. And the survey names three forces driving systems up that ladder. The need for long-range consistency so the agent does not contradict itself across a long interaction. The challenge of dynamic environments where the world changes and yesterday’s fact is today’s error. And the ultimate goal of continual learning, an agent that actually gets better the longer it runs, rather than just accumulating a bigger pile of logs. Make each stage concrete because the difference is easy to blur. Stage one, storage, is a chatbot that saves your past conversations and can quote them back. The information is preserved, and the data is shared. Stage two, reflection, is an agent that, after a session, writes itself a note. The user prefers terse answers and dislikes when I over-explain, distilling the raw trace into something more useful than the trace itself. Stage three, experience, is an agent that, having handled fifty support tickets, induces a general procedure for a whole class of problem and applies it to a ticket unlike any it has seen. The survey singles out two mechanisms as the frontier of that experience stage, and they’re worth naming because they recur through this series. The first is proactive exploration, an agent that doesn’t just passively record what happens to it, but deliberately seeks out experiences that will make its memory more useful, the way Voyager, which we’ll meet in episode three, sets its own curriculum. The second is cross-trajectory abstraction, pulling a reusable pattern out of many separate episodes, rather than readapting a single remembered episode each time. That second one is subtle, and it is the crux of the hardest debates in the field because, as we’ll see in episode three, abstracting across trajectories is exactly where systems both gain the most and lose the most. What I like about this framing is that it gives you a diagnostic. Most production systems today are honestly still at stage one or stage two. Maybe they reflect. The experience stage, real cross-trajectory abstraction, is where the research excitement is and where the hard, unsolved problems live. When you hear a vendor claim their agent learns from experience, the useful question is, which stage are you actually at? Are you abstracting across trajectories or are you just keeping good logs and calling it learning? Here is the uncomfortable third leg of the foundations. This is a revolutionary story and I still have no idea whether any of it works because evaluation is genuinely hard. The third paper on our reading path is the 2025 Survey on Evaluation of LLM-Based Agents by Asaf Yehudai and colleagues, the first comprehensive survey of how the field measures agents at all. They organize agent evaluation along four dimensions. First, fundamental capabilities. Planning, tool use, self-reflection, and crucially for us, we need to know what is the best way to evaluate an agent. Second, application-specific benchmarks for web agents, software engineering agents, scientific agents, conversational agents. Third, benchmarks for generalist agents that have to do a bit of everything. And fourth, the frameworks and tooling for running evaluations in the first place. And their read on where evaluation is heading is one of the most important threads in this whole series. So let me state it plainly. The trend is toward more realistic, updated benchmarks, and away from the static, single-number leaderboard. Why continuously updated? Because static benchmarks rot. They leak into training data, they saturate, and a frozen benchmark slowly stops measuring capability and starts measuring contamination. We will see exactly this happen to the dominant memory benchmark in a later episode. Ground those four dimensions under application-specific, web agents are measured on WebArena and Mind2Web, which we’ll dig into in episode 3, software engineering agents on SWE-bench, where the oracle is whether the code actually passes the tests, conversational and memory agents on LoCoMo and LongMemEval, which become central in episodes 2 and 4. Under fundamental capabilities sits memory itself, and the survey’s point is that memory is consistently the under-evaluated leg in tool use, precisely because it’s the hardest to isolate. You can check whether a tool call succeeded. Checking whether the agent remembered the right thing for the right reason at the right time is genuinely harder. The survey is also blunt about the gaps, and the gaps are telling. The field undermeasures cost efficiency. It’s not just about the benchmark’s tidy setup, and it lacks fine-grained, scalable evaluation methods. The ability to say not just did the agent get the right answer, but where in its reasoning did it go wrong. That last gap, fine-grained failure attribution, is the seed of the entire measurement crisis we will spend a full episode on. For now, just plant the flag. It provides more than it reveals. Now step back and look at the meta-signal, because it tells you something about the moment we are in. In just the last few months, the research community has produced a small flood of agent memory survey papers. From storage to experience, which we just covered. Another titled, Memory in the Age of AI Agents, a sprawling multi-author effort. Another, Memory for Autonomous LLM Agents, more are landing on the pre-print servers every few weeks. When a field produces multiple large surveys in a single quarter, that is not a coincidence. It is the field reaching a level of fragmentation where no single researcher can hold it in their head anymore, and several teams independently decide the most valuable thing they can do is impose order. The surveys themselves say this out loud. They describe a field where the same words mean different things, where every system invents its own evaluation protocol. Where results cannot be compared across papers because nothing is held constant. Make the fragmentation concrete, because it is not abstract hand-wringing. Take the word memory across three systems we’ll meet next episode. In Zep, memory is a temporal knowledge graph with typed entities and time-stamped edges. In A-MEM, memory is a self-organizing web of notes that rewrite each other. In Mem0, memory is a complex log of facts optimized to minimize tokens. Same word. Three incompatible data models, three different retrieval strategies, three different evaluation setups, and no way to move your data from one to another. Or take evaluation. One paper scores whether the final answer was right, another scores whether the correct memory was retrieved, a third scores both and finds they disagree. When the surveys say the field is fragmented, this is what they mean. Not that there are many ideas, in identical vocabulary while being fundamentally different underneath, which makes honest comparison nearly impossible. This is the central tension of the foundations, and it will echo through every remaining episode. The conceptual vocabulary converged early, thanks to CoALA, but the implementations diverged wildly. We agreed on the words episodic, semantic, procedural, retrieval, consolidation, and then everyone built something different underneath those words. So you get the strange situation where two products both claim long-term memory with knowledge graphs and share almost no actual design decisions. For anyone building on this stuff, the practical takeaway from the foundations is to start from a survey taxonomy before you pick a tool. The CoALA grid and the storage reflection experience ladder are not academic decoration.
They are the cheapest way to make the design space legible before you commit to a vendor whose vocabulary is hiding a very specific, very opinionated set of choices. Pick the abstraction first, then go shopping.
Before we tally up what the foundations settle, sit with the strangest recurring feature of this field, its obsession with the human brain. CoALA reached back to cognitive architectures from the 1980s. The storage-to-experience survey keeps invoking consolidation and the hippocampus. And as we’ll see in the final episode, the 2026 forgetting literature is a full-on neuroscience gold rush. Why does a field built on transformers keep reaching for neuroscience? The honest answer is that human memory is the only existence proof we have. It is the one system, anywhere, that remembers across a lifetime, forgets gracefully without catastrophic loss, generalizes from a handful of examples, stays coherent for decades, and runs on a power budget of more than $1 billion. The CoALA grid is the only system that remembers across a lifetime, and runs on a power budget smaller than a light bulb.
Every architecture in this series is, at bottom, a wager about which features of human memory are worth copying, and which are accidents of wet biology you should ignore. The features the field has bet on copying are clear. The multi-store model, the idea that short-term working memory and several distinct long-term stores are different systems with different dynamics, that’s the CoALA split. And it traces straight back to the Atkinson-Shiffrin model from 1990. Consolidation. The idea that memories are not written once, but reprocessed and stabilized over time, often offline. That’s the inspiration behind the reflection stage, and the sleep mechanisms we’ll meet later. And the episodic semantic distinction between remembering a specific event and knowing a general fact comes from the psychologist Endel Tulving in the 1970s, and it is now load-bearing in production systems like Zep.
But there’s a real risk. And the careful papers flag it. The brain is not a transformer. Borrowing a mechanism because it sounds biologically plausible is not the same as showing it works. And a beautiful neuroscience metaphor can paper over the absence of an actual measured result. This tension, biological inspiration racing ahead of engineering evidence, is going to be the central drama of the final episode. For now, hold both halves. The cognitive science framing is genuinely general. It has produced most of the field’s best ideas, and it is also where a lot of hand-waving hides.
The job, across this whole series, is to keep asking which biological metaphor actually earns its keep with a number behind it. So what do we actually know, standing on the foundations, before we go deeper? We know the parts. Working, episodic, semantic, procedural memory, plus the internal and external actions that read and write them, plus a decision loop. That is CoALA.
That is the lingua franca. We know the trajectory. Systems evolve from storing raw experience to reflecting on it, to abstracting it into transferable knowledge. That is the storage to experience arc. And most of what ships today is still climbing the first two rungs.
We know the central anxiety. Evaluation is immature, single numbers mislead, benchmarks rot, and the field cannot yet attribute failures to the right stage of the memory pipeline. And we know the meta-fact. The field is fragmented enough that imposing order has become a research contribution in its own right. Notice what is not settled. Nobody has agreed on the right data structure for memory. That fight is the next episode. Nobody has agreed on how to evaluate procedural skill reuse. That is two episodes away. And the entire question of forgetting, of when an agent should let go of a memory, is so underdeveloped that it gets the final episode mostly to itself. The foundations give us the map. They do not give us the data. The field is fragmented enough that imposing order is not a good idea. We know the central anxiety. Evaluation is immature, single numbers mislead, benchmarks rot, and the field cannot yet attribute failures to the right stage of the memory pipeline. And we know the central anxiety. The field is fragmented enough that imposing order is not the only one. Nobody has agreed on how to evaluate procedural skill reuse. That is two episodes away. And the entire question of forgetting, of when an agent should let go of a memory pipeline. That is two episodes away. And the entire question of forgetting, of when an agent should let go of a memory pipeline. And the entire question of forgetting, of when an agent should let go of a memory pipeline. The reason cognitive science keeps showing up here, the reason CoALA reached back to the 80s, and the storage to experience survey keeps invoking the hippocampus, is that human memory is the one existence proof we have of a system that remembers across a lifetime, forgets gracefully, generalizes from a handful of examples, and stays coherent for decades. Every architecture in this series is, in some sense, a hypothesis about which parts of human memory are worth copying and which are accidents of biology. Keep that question live. It is the through line under all the engineering. That is the foundation. CoALA gave us the vocabulary. From storage to experience, gave us the trajectory. The evaluation survey gave us the central anxiety. And the wave of new surveys tells us the field knows it has outgrown its own coherence. Next episode, we get concrete. We open up three real systems that people actually deploy, Zep with its temporal knowledge graph, A-MEM with its self-organizing notes, and Mem0 with its production focus. And we look at the build versus buy decision and the vendor landscape that formed around them. We go from the map to to the machines. I will see you there.
- 2. The Memory Stack
Why a plain baseline can beat a fancy memory system on its own benchmark, and what a real memory stack actually needs.
Read transcript
The agentic memory reading path, 2 of 5. Here is a number that should make you suspicious.
On the benchmark that the MemGPT team built to prove their memory system worked, a plain, dumb baseline, just stuffing the entire conversation into the context window, scored 94.4%. The fancy memory system scored 94.8. Four-tenths of a point, for all that machinery. That number is not an embarrassment. It is a clue. It tells you that the benchmark was too easy, that the real problem lives somewhere the benchmark wasn’t looking, and that to build memory that earns its keep, you have to be ruthless about what you are actually measuring. This episode is about the systems people deploy to give agents a memory,
the three architectures on our reading path, and the industry that has grown up around them. Welcome back to the agentic memory deep dive. This is episode 2, the memory stack. Last episode, we built the scaffolding, the CoALA vocabulary, the storage-to-experience arc, the evaluation anxiety.
Today we get our hands dirty with three real systems, in roughly the order our reading path presents them. Zep, a temporal knowledge graph from a commercial vendor. A-MEM, a research system built on an unlikely inspiration, a German note-taking method from the 20th century. And Mem0, a system built explicitly for production deployment at scale. Then we widened out the scope of the system, and we went out to the vendor landscape and the build versus buy decision that every team building agent now has to make.
The through line for this episode is a tension you will feel in all three systems and in the market around them. On one axis, how much structure should memory have? Flat text on one end, rich knowledge graphs on the other. On the other axis, how much should you spend to maintain it?
Because every bit of structure you add, every entity you extract, every graph edge you resolve, costs a model call, adds latency, and creates a new way to be wrong. Let us watch three teams make that trade differently.
Start with Zep, from a paper by Preston Rasmussen and colleagues at the company of the same name, built around an open source engine they call Graphiti.
Zep’s bet is that the missing ingredient in agent memory is time, and the way you capture time is a temporally aware knowledge graph. The architecture has three tiers, and the structure is worth understanding because it is a complex structure. The structure is a clean realization of the CoALA split from last episode.
At the bottom, an episode subgraph, the raw input data, messages, text, JSON, stored losslessly. This is the immutable record, the ground truth. On top of that, a semantic entity subgraph, the entities and the relationships between them, extracted from the episodes by a language model.
And at the top, a community subgraph, clusters of strongly connected entities, each with a high level summary, giving the system a global view of the system, giving the system a global view of the domain. Raw episodes at the bottom, extracted semantic facts in the middle, summarized communities at the top. The authors explicitly note that this dual storage, raw episodic data alongside derived semantic structure, mirrors the psychological distinction between episodic and semantic memory. CoALA in production. But the real innovation, the thing Zep is actually selling, is what they call bitemporal modeling. Every fact in the graph carries two timelines, Timeline T is the chronological order of events in the world. When did this thing actually become true? Timeline T prime is the transactional order. When did the system learn about it? Keep both, and you can do something vector stores famously cannot. You can handle a fact that changes. When new information contradicts an existing edge, Zep uses a model to detect the conflict and invalidates the old edge by stamping it with an expiry time, rather than deleting it, or letting both end up. Zep uses a model to detect the conflict and invalidates the old edge by stamping it with an expiry time, rather than deleting it, or letting both end up. Zep uses a model to detect the conflict and validates the old edge by stamping it with an expiry time, rather than deleting it, or letting both end up. When both versions sit there equally valid, the old fact is still there, marked as having been true from this date to that date. The agent stops being confused about what is currently true. The construction side has details worth knowing, because they’re where the cost and the failure modes live. When Zep ingests a message, it extracts entities, then runs an entity resolution step, embedding each name, and doing both a similarity search and a full text search against existing entities. existing entities to decide whether this is a new entity or a duplicate of one already in the graph. It uses a reflection technique borrowed from the reflection work to cut hallucinations during extraction. It builds communities not with the heavy Leiden algorithm but with label propagation, specifically because label propagation can be updated incrementally as new data arrives instead of recomputing the whole community structure every time. Every one of those steps is a language model call, which is the hidden tax of the graph approach, and Zep’s engineering is largely about paying that tax as rarely as possible. The retrieval side is a useful template, too. Zep runs three search methods in parallel cosine semantic similarity for meaning, Okapi BM25 full text for exact words, and breadth-first graph search for contextual neighbors. Each targets a different kind of similarity, semantic, lexical, and structural nodes that sit closely together in the graph. Then it re-ranks, and the menu of re-rankers is itself instructive. Reciprocal rank fusion, maximal marginal relevance, a graph distance re-ranker that favors facts near a chosen node, an episode mentions re-ranker that boosts frequently referenced facts, and at the top of the cost curve, a cross-encoder that scores every candidate against the query with full attention. This multi-channel then re-rank pattern is, as we will keep seeing, the production default. And the deeper design point. Zep stores raw episodes and derived semantic facts side by side, which the authors explicitly say mirrors how human memory keeps distinct events and general associations as separate but linked systems. Keep the raw, derive the structure, link them. That phrase will be the moral of the whole series. The results.
On the deep memory retrieval benchmark, Zep posts 94.8% against MemGPT’s 93.4. Marginal. And the authors are refreshingly honest that the benchmark is the problem. Each conversation is only 60 messages, easily fitting in a modern context window, so a full context baseline nearly ties it. The real story is the harder benchmark, LongMemEval, with conversations averaging 115,000 tokens. There, Zep improves accuracy by up to 18.5%, while cutting response latency by… around 90% because instead of feeding 115,000 tokens to the model every turn it retrieves about 1,600. That is the actual pitch, not more accurate on a toy task but comparable or better accuracy at a fraction of the tokens and latency on a realistic one. The second system takes a completely different inspiration. A-mem by Woojong Shu and colleagues builds its memory on the Zettelkasten method, the slip box note taking system associated with the Zettelkasten method. with the sociologist Niklas Luhmann, who used it to write an absurd number of books. The core idea of a Zettelkasten is that the value is not in the individual notes. It is in the links between them, and that the network reorganizes itself as it grows. A-MEM applies that to agent memory. When a new memory is added, the system does not just file it. It generates a structured note with contextual descriptions, keywords, and tags. Then it analyzes the existing memories, finds ones with meaningful similarity, and establishes links.
So the memory store is an interconnected network, not a flat list, and not a rigid, predefined schema. The part that makes it genuinely agentic, and the part worth dwelling on, is memory evolution. When a new memory comes in and links to older ones, it can trigger updates to those older memories, revising their contextual descriptions and attributes in light of the new information.
The network refines its own understanding over time. Picture it. You tell the agent in March you’re learning guitar, and in May you mention you’ve joined a band.
A flat store just appends the band fact. A-MEM, in principle, goes back and enriches the guitar memory with the new context, the two notes now linked and mutually informed.
This is the storage-to-experience arc from last episode, made concrete. A-MEM is reaching for the reflection and experience stages, where memory is not a static archive, but something that reorganizes, as the memory store is. The authors tested across six foundation models, and reported consistent improvement over prior state-of-the-art memory systems, and notably the gains held across both small and large models, suggesting the benefit comes from the organization scheme itself, rather than from a single capable model carrying it. There is a cost to the freedom, though, and it’s the mirror image of Zep’s. Zep’s structure is rigid, but predictable.
A-MEM structure is flexible, but immeasurable. Zep’s structure is emergent, which means its behavior is harder to audit, and its self-rewriting carries exactly the useful memories become faulty risk will keep circling. Every time the agent revises an old note, it can also corrupt it. Flexibility and trustworthiness are intention, and A-MEM sits firmly on the flexibility side.
Now, hold A-MEM next to Zep’s, and you can see the philosophical split in the whole field. Zep’s imposes structure, a defined three-tier graph, explicit entity and edge types, a formal bitemporal model. A-MEM grows structure, emergent links, self-organizing notes, evolution driven by the agent rather than a fixed schema. Both are knowledge graphs, in some loose sense. They are almost opposite design philosophies. And here is the dissent worth flagging, the one we’ll return to in episode 3.
There is a growing argument in the field that the whole industry took a wrong turn by converging on entity-relationship graphs and atomic facts at all. That extracting clean little facts from messy conversation is lossy adds a hallucination-prone model step, and that some agents would be better served keeping the raw narrative.
A-MEMs keep evolving the notes, and the contrarian just keep the raw trace are both reactions to the same worry, that aggressive structure throws away something you needed. The third system is the most explicitly commercial, and that is the point.
Mem0 by Pratik Chakara and colleagues puts the word, production-ready and scalable, right in the title. Its pipeline is the one most teams will recognize. Dynamically extract salient information from the ongoing conversation, consolidate it, and retrieve it on demand. There is a base version and a graph-enhanced variant that adds relational structure. What makes Mem0 worth studying is not a novel data structure, it is the relentless focus on the production metrics that research papers usually ignore. They evaluate on the LoCoMotivity of the data structure, and they evaluate on the LoCoMotivity of the data structure. They evaluate on the LoCoMotivity of the data structure. They evaluate on the LoCoMotivity of the data structure. They evaluate on the LoCoMotivity of the data structure. They evaluate on the LoCoMotivity of the data structure. They evaluate on the LoCoMotivity of the data structure. They evaluate on the LoCoMotivity of the data structure. They evaluate on the LoCoMotivity of the data structure. And the headline numbers are about cost, as much as accuracy. Mem0 reports a 26% relative improvement over OpenAI’s memory on a language model as judge metric. But then, a 91% lower p95 latency, and more than 90% token cost savings versus the full context approach. Sit with why those numbers are the real product. At 100 users, you can afford to stuff the whole history into context. At 100,000 users, each paying you nothing or close to it, a 90% token reduction is the difference between a viable business and a bonfire of API credits. Mem0’s contribution is to take memory seriously as a systems problem with a cost model, not just an accuracy problem with a leaderboard. The graph variant, notably, adds only about 2% overall accuracy over the base, which is itself an honest data point about how much the heavy structure actually buys you on this benchmark. So across our three systems, you have three answers to the structure versus cost question.
Zep, maximal structure, justified by temporal reasoning. A-MEM, emergent, self-evolving structure, justified by adaptability.
Mem0, lean structure, justified by cost at scale. None is the universal right answer. They are points on a trade-off curve, and which one fits depends on whether your problem is dominated by changing facts, by open-ended learning, or by the bill. Before the market, let’s get systematic, because there’s a field companion to all this research, a survey built from engineering write-ups and product launches rather than papers, and it organizes the whole space by design decision. 11 of them. You don’t need all 11, but a handful are the ones every team actually trips over, and they map cleanly onto the three systems we just covered.
Retrieval and ranking. The decision, one vector index or multiple parallel channels fused together. The emerging production answer, the one Zep implements and Cloudflare shipped, is multi-channel with reciprocal rank fusion, not a single cosine lookup. And the sharp warning underneath it, semantic closeness, is not relevance. Cosine similarity will cheerfully hand you something near your query in embedding space that is stale, or about the wrong user, or topically adjacent but useless, while missing the fact that actually mattered because it wasn’t phrased the way the query was.
Consolidation and distillation. The decision, do you run a model on every turn to extract memory or batch it lazily? Eager per-turn extraction is the single biggest cost driver in these systems. Lazy. Lazy consolidation cuts the bill, but adds staleness. And the hard-won rule, reported independently by Slack’s engineers, and by a research paper bluntly titled Useful Memories Become Faulty. When a model continuously rewrites its own memory, the memory degrades, drift, context collapse, detail sanded off.
So keep the raw trace as ground truth, and treat the distilled version as a fallible, rebuildable layer. Exactly the lesson Zep’s dual storage encodes, and exactly the lesson that will detonate in the future. In episode 3, when we find raw trajectories beating distilled skills.
Temporality. The decision. When a fact changes, do you supersede version or silently overwrite? This is the number one field complaint about plain vector stores. They have no notion of supersession, so the old and new facts sit there equally retrievable, and the agent gets confused about what’s true now. Bitemporal modeling, Zep’s whole identity, is the answer builders switch backends to get, substrate. The decision, do you even need a vector database? The contrarian, deliberately boring answer from working engineers is often no. That SQLite with full text search over a transcript store goes remarkably far, and that Git plus object storage as the memory layer gives you audit friendliness for free. Justify the heavy store before you reach for it. And working memory and context. The reminder that long term memory is just one of roughly seven things competing for the context window every step. So you cannot design memory in isolation from the broader context budget. Those five, retrieval, consolidation, temporality, substrate and context, are the decisions that separate a memory system that survives contact with production from one that quietly rots.
Step out of the papers and into the market, because this is where state of industry actually lives. The managed memory market formed astonishingly fast across 2025 and 2026, almost in parallel with the surveys that we’ve seen in the last decade and a half. So you cannot design memory in isolation from the broader context budget. Those five, retrieval, consolidation, temporality, substrate and context, are the decisions that we’ve seen in the last decade and a half. So you cannot design memory in isolation from the broader context budget. Those five, retrieval, consolidation, temporality, substrate and context, are the decisions that we’ve seen in the last decade and a half. The field companion to this research, a survey built from engineering write ups and product launches, lays out the landscape. Mem0, Letta, which grew out of the MemGPT work, Cognee, Zep, with Graphiti, MemoryOS, and more arriving constantly. Cloudflare shipped agent memory with exactly the multi channel plus reciprocal rank fusion retrieval pattern we saw in Zep. And shared team memory profiles became a headline feature. And here you see that M exercised 이게 он Viking المค versão escorting, Nano e involucrando a kemik that мы جمعا here is the catch that should shape any build versus buy decision. Every one of these frameworks ships its own bespoke storage and its own vocabulary. There is no shared wire format, which means migrating your memory from one framework to another today essentially means rebuilding from scratch. You are not choosing a library. You are choosing a representation, a retrieval strategy, and a set of governance choices, and you are marrying them. The principle the practitioners keep arriving at, memory quality equals schema quality, and if you can’t see or move the schema, you can’t really own it. There is also a quieter contrarian movement in the industry that deserves airtime because the vendor pitch can make it sound like you must adopt a heavy memory service. The counter position voiced by working engineers is that many agents do not need a vector database at all. SQLite with full text search over a stored transcript goes remarkably far. Git plus object storage as the memory layer is a real pattern. Keep the immutable transcripts cheaply, derive memory on demand, and get audit friendliness for free.
And a related warning, some frameworks advertised as local still phone home to a cloud model for the extraction step, so local and private is a claim to verify, not assume, especially if privacy was the whole reason you reached for it. There is one more production lesson the field reports keep repeating, and it is blunt. Just add a vector database breaks once the agent runs for a while. The store accumulates, retrieval gets polluted, the agent starts repeating mistakes, and drifting. Which is a perfect setup for the rest of the series, because every failure on that list, drift, staleness, repeated mistakes, is a memory problem. The three systems we covered are each trying in their own way to solve. So how should you read the memory stack, having opened up three systems and the market around them? First, the structure question is the load-bearing one, and it has no default answer. Graph, vector, atomic facts, evolving notes, raw transcript. Each buys you something and costs you something.
Zep’s graph buys temporal reasoning at the cost of an extraction step. Mem0’s leaner approach buys cost savings at the cost of relational richness.
Ask what your actual failure mode is before you pick. Second, time is the feature builder’s most consistently underrate and most consistently switch backends to get. Zep made bitemporal modeling its whole identity for a reason. If your domain has facts that change, and almost every real domain does, a memory with no notion of supersession will quietly poison itself. Third, measure the system, not the demo. Mem0’s contribution is mostly that it reported P95 latency and token cost, the numbers that decide whether you can actually ship. A memory system that looks great on a five-message demo, and falls over the top of the list, is a memory system. It’s not just a five-message demo, it’s a five-message system. It’s a five-message system. A five-message demo, and falls over at 100,000 users, has told you nothing useful.
And fourth, plan for the exit before you enter. No shared wire format means the framework you pick today is one you may be stuck rebuilding out of later. Keep your raw transcripts in something portable and boring, so that whatever clever memory layer you put on top is a derived, rebuildable thing rather than your only copy of the truth.
That last point, keep the raw, treat the clever, layer as fallible, is going to come back with a vengeance in episode three, because it turns out the same lesson governs not just facts, but skills. Three systems, three philosophies. Zep bets on time and structure. A-MEM bets on emergent, self-organizing networks. Mem0 bets on lean memory and the production cost model. And the market around them is fast, fragmented, and locked in by the lack of any shared format.
Next episode, we move from remembering facts, to remembering how to do things. Procedural memory and skill libraries, from Voyager building a library of executable skills in Minecraft, to agent workflow memory inducing reusable routines for the web, to a brand new benchmark that delivers the most uncomfortable finding in the field. That raw experience often beats the polished skill you distilled from it. That one reshapes how you should think about every coding agent you use. See you there.
- 3. Procedural Memory & Skills
Agents that write, store, and reuse their own skills, from Voyager's self-taught Minecraft tech tree onward.
Read transcript
The Agentic Memory Reading Path, 3 of 5.
In 2023, an agent named Voyager taught itself to play Minecraft by writing its own skills, storing them in a library, and reusing them. It unlocked the game’s tech tree up to 15 times faster than anything before it, and when you dropped it into a brand new world, it carried its skills with it and kept going while other agents froze. It looked like the future of how machines learn. Do something once, distill it into a reusable skill, never relearn it. Three years later, a benchmark called SkillEvalBench tested that dream rigorously and found something that should unsettle anyone building on it. The distilled skills often performed worse than just keeping the raw transcript of what the agent did. The polished skill library, the thing everyone is building, frequently lost to the messy log it was supposed to replace.
This episode is about proceduralization. Procedural memory, how agents remember not facts, but how to do things, and about why the obvious way to do it might be wrong.
Welcome back. This is Epi3. We have done facts. Episodes 1 and 2 were about semantic and episodic memory, what happened and what’s true. This episode is the third leg of the cognitive triad from CoALA, procedural memory, skills, routines, the agent’s growing repertoire of how-to. Our reading path gives us three papers that form a perfect arc. Voyager. Voyager, the origin, where the skill library dream was born. Agent workflow memory, the maturation, where the idea got disciplined and proven on real web tasks.
And SkillEvalBench, the reckoning, a 2026 benchmark built specifically to test whether skill distillation actually works, with results that are going to change how you think about every coding agent you use. And because this is the part of the field closest to the tools we all use daily, we will spend real time on what it means to be a coding agent. Voyager, from Guanzhi Wang and colleagues, is one of the most cited agent papers of its era, north of 700 citations, and for good reason. It was the first language model-powered agent that did open-ended lifelong learning in Minecraft, with no human in the loop, and it had three parts worth remembering.
One, an automatic curriculum that proposed increasingly hard tasks to maximize exploration, so the agent set its own goals. Two, an ever-growing skill library of executable code, where each skill is a program the agent wrote to accomplish something, stored and indexed by a description of what it does, so it can be retrieved by meaning and composed. Three, an iterative prompting loop that fed back environment feedback, execution errors, and self-verification, so the agent ran its code, saw it fail, read the error, and rewrote it until it worked, only then committing the skill to the library. That self-verification gate matters. It means the library fills with skills that actually ran, not skills that merely look plausible.
Critically, Voyager did all this through black-box calls to GPT-4. No fine-tuning, no model weights touched. The learning lived entirely in the skill library, in the harness, not in the model. That is a profound design statement, and it’s the one the rest of this episode interrogates. It says capability can be accumulated outside the model, in an editable store of skills, which is exactly the premise behind every self-improving agent and every coding agent that saves reusable commands today. If it’s true, you can make a frozen model smarter just by giving it a better library.
Whether that premise actually holds, under honest measurement, is the question that dates by the end of this episode. The results were striking.
3.3 times more unique items collected, 2.3 times longer distances traveled, tech tree milestones up to 15.3 times faster than the prior state-of-the-art, and the headline capability, the skill library, transferred. Drop Voyager into a fresh Minecraft world, and it reused its learned skills to solve new tasks from scratch, while other methods struggled to generalize. And here is the line from the Voyager paper that planted a flag for the whole field. The authors argued that because the skills are temporally extended, interpretable, and compositional, they compound the agent’s abilities and, in their words, alleviate catastrophic forgetting. That is the dream in one sentence. A library is a library. A library of code skills as a form of memory that never degrades, only grows, and carries from world to world. Everything in this episode is a stress test of that sentence.
Before we get to the disciplined version of the skill library idea, draw a distinction the field has settled into, because it determines how procedural memory fails.
There are two species of stored skill, and they are genuinely different animals. The first species is the executable code skill, the Voyager kind. A skill is a memory. It runs a program. It either runs or it doesn’t. When it fails, it fails loudly, a compilation error, an exception, a wrong result you can verify against the environment. That’s a feature. You can put a self-verification gate in front of the library and only admit skills that demonstrably worked. But code skills are brittle in their own way. They fail at composition when you try to snap two of them together, and the interfaces don’t quite match. And they’re tied to the specific tool. The second species is the natural language workflow, the kind we’re about to see in agent workflow memory. Here a skill is not code, it’s a described routine, a remembered procedure in words, to book travel, first search flights, then compare against the calendar, then confirm before paying. These are flexible. They transfer across surface changes. They read like instructions a human could follow. But they fail differently and more quietly. They fail through ambiguity and instruction drift. The agent reads the workflow, interprets it a little loosely and wanders off the procedure without any error firing. Nothing crashes. The result is just subtly wrong. Why does this matter for a benchmark and for you? Because the two species need different evaluation and different guardrails. Code skills need execution grounded verification. Run it. Check it. Workflow skills need process checking. And they fail. Did the agent actually follow the steps, not just did the answer look right? A benchmark that only handles one species misses half the field, and a coding agent that mixes both, saved code snippets plus remembered conventions and prose, has both failure modes at once. Hold this distinction. It’s the lens for everything that follows.
Voyager was a proof of concept in a game. The next paper, Agent Workflow Memory by Zhiruo Wang and colleagues, took the skill library idea and made it work on something messier and more real, web navigation. The reframing is subtle but important. Instead of a library of executable code, Agent Workflow Memory induces workflows, reusable routines, commonly repeated patterns of action, extracted from past experience and selectively fed back to guide future behavior.
So there are now two flavors of procedural memory in play, and they fail differently. Voyager-style executable code skills fail with compilation and composition errors. Natural language workflows and routines fail with ambiguity and instruction drift. A benchmark has to handle both, because the field is split between them. What makes Agent Workflow Memory rigorous is the offline and online distinction.
Offline, the agent induces workflows from training examples ahead of time. Online, and this is the clever part, it induces workflows on the fly, from its own test time experience, with no training set at all. They tested on two big web benchmarks, Mind2Web and WebArena. Collectively, over a thousand tasks across 200 plus domains, travel, shopping, social media.
The numbers, a 24.6% relative improvement on Mind2Web, and a 51.1% relative improvement on WebArena, while also reducing the number of steps to finish a task. But the most important result is about generalization, and it is the one to hold on to. Online agent workflows, and this is a standard in our typical form of child development. Read that again. The more novel the situation, the more the accumulated Workflow Memory helped. That is exactly the property you want from memory, and exactly the property the next paper says is harder to achieve than it looks. Now the reckoning, SkillEvalBench by Ying-Ti Lei and colleagues, and it is a classic before this little ruckus VTB it is. In the last few days, the best I’ve seen work with us is the VTB. We are constantly trying to break this barrier and make it easy to run even harder against specific expectations. This is the first time we’ve done this kind of work. We’re not only trying to hack into the statistics, but we’re actually trying to break them down into three different categories. We don’t want to work with our employees, Now the reckoning. SkillEvalBench by Ying-Ti Lei and colleagues, 2026, is a diagnostic benchmark built to answer one precise question. When an agent accumulates rich episodic experience, can that actually be distilled into reusable procedural skills? Not, does the score go up, but did real durable skill formation happen? The design is the most careful in the whole series, so let me lay it out, because the design is the contribution. 180 tasks across six real-world agent environments, organized into role-conditioned task families that share a hidden, latent procedure. Meaning each family is a set of tasks that all require the same underlying how-to, dressed in different surface details, so the benchmark can ask whether the agent learned the procedure or just memorized the surface. Within a family, there’s a deliberate progression.
During acquisition, the skill-forming phase, the agent sees variants designed to teach the procedure, a canonical version that presents it plainly, an enriched version that exposes a missing sub-step, a variant that changes the surface but keeps the procedure. The agent updates an external skill library using compacted trajectories and verifier feedback. Then, and this is the crucial move, the library is frozen and the agent faces deployment tasks it cannot adapt to. Those deployment tasks come in three flavors, each probing a different kind of robustness. Context shift, where the skill is needed in an unfamiliar setting. Adversarial shortcuts, where a shallow wrong answer is tempting and only a process check catches it. And composition, where the agent must combine skills it learned separately. Acquisition, then frozen deployment. This is the freeze-then-evaluate discipline we flagged back in episode one, made into a benchmark.
There are ten model configurations and three different agent harnesses, so the findings aren’t an artifact of one setup. And then the controls, which are what make the findings trustworthy. SkillEvalBench compares the agent’s self-generated skills against four baselines, a no-skill control, a raw trajectory control, a curated start condition, and self-generated evolution. By holding the answering model fixed and varying only the skill condition, it can separate genuine procedural abstraction from three confessions. The base model’s raw capability, prior curated knowledge, and mere reuse of episodic traces.
The findings, across ten model configurations and three agent harnesses. First, current agents often adapt locally, but rarely form robust, reusable skills. Skill conditions can help during acquisition or replay, but the gains are unstable once the library is frozen for deployment. Second, the gut punch. Raw trajectory reuse frequently outperforms distilled skills. The base model’s raw capability, prior curated knowledge, can help during acquisition or replay, but the gains are unstable once the library is frozen for deployment. Third, the gut punch. Raw trajectory reuse frequently outperforms distilled skills. Keeping the messy transcript of what you did beats the clean skill you extracted from it. The author’s interpretation is precise. Distillation discards contextual and procedural cues that turn out to be useful later. Abstraction is lossy, and it throws away exactly the details that would have helped in the novel case. And third, the capacity finding. Writing more skills, or building bigger skill libraries, is not the answer. More updates can improve coverage while introducing episodes of the novel. Third, the capacity finding. Writing more skills, or building bigger skills, is not the answer. More updates can improve coverage while introducing episodes of the novel. Third, the capacity finding. Writing more skills, or building bigger skills, is not the answer. More updates can improve coverage while introducing episodes of the novel. The library fills up with junk that fit one situation and pollutes the rest. Put Voyager, agent workflow memory, and SkillEvalBench in a line, and you get the field’s actual trajectory.
The dream, skills as perfect, compounding, transferable memory. The disciplined version, yes, induced workflows really do help, especially as tasks get novel. The reckoning, but only if you measure honestly, with a frozen library and a raw trajectory control, Because a lot of what looks like skill formation is just local adaptation, or the base model being good, and the polished abstraction often loses to the raw trace.
Sit a moment longer with SkillEvalBench’s third finding, the capacity result, because it overturns the most intuitive thing you’d assume about a skill library, that more is better. The benchmark found that writing more skills, or provisioning a larger resource library, is not sufficient, and can actively hurt. Additional updates improve coverage, the library can handle more cases, but they also introduce episode-specific drift and procedural clutter.
The library fills with skills that fit one peculiar situation, that overlap and conflict with each other, that the retriever now has to wade through. Coverage goes up, quality and findability go down.
This reframes the skill library from an asset you accumulate into an organism you have to keep healthy, and the field is starting to treat library haphazardly. The library is now able to measure library health as a measured quantity in its own right.
The metrics that matter, the raw size of the library, its growth rate, how much of it is redundant or near duplicate, and what fraction of retrievals actually hit a high-value, frequently reused skill versus pulling up clutter.
A library that grows without bound, where most skills are never reused, is not a richer agent. It’s a polluted index that gets slower and less accurate over time. Some research systems address this directly. By co-managing three things at once, which skills to select, which to actually use, and which to distill or merge, on the theory that without active maintenance, the library accrues drift until it saturates and caps performance. The parallel to ordinary software is exact and worth stating, because it makes the discipline obvious. An ever-growing skill library with no curation is technical debt. It is a code base nobody refactors, a utils folder where every function was added, and half are near duplicates, and none have tests for whether they’re still used. You would never let your actual code base grow that way.
The finding here is that an agent’s procedural memory needs the same hygiene, dead-skill elimination, deduplication, periodic consolidation that you’d apply to any code you intend to maintain. Accumulation is not learning. Curated accumulation, maybe.
This is the episode where the research touches your daily tools directly, because a coding agent’s skill library is exactly this problem. When your agent writes a reusable helper, saves a skill or a command, or distills a past session into a reusable instruction file, it is doing procedural memory, and SkillEvalBench’s warning applies to it directly. The industry has been converging on context engineering as the discipline here.
Martin Fowler published a substantial piece this year on context engineering for coding agents, framing long-term memory. He has one of roughly seven things competing for the context window every step, which means you cannot design skill memory in isolation from the rest of the budget.
And a paper from this spring, Codified Context, Infrastructure for AI Agents in a Complex Code Base, names the failure mode in plain language.
Agentic coding assistants lack persistent memory, so they lose coherence across sessions, forget project conventions, and repeat mistakes they were already corrected on. Every one of those is a procedural memory failure.
Now layer SkillEvalBench’s findings on top, because they are quietly subversive for how we build coding agents. If raw trajectory reuse often beats distilled skills, then the instinct to aggressively summarize a successful session into a tidy reusable rule may be actively counterproductive.
The messy transcript of how the agent actually fixed the bug, with all its false starts and environment-specific details, may transfer better than the clean three-line lesson you extracted.
And if bigger skill libraries accrue drift and clutter, then an ever-growing folder of saved skills and commands is not a free win, it is a maintenance liability that pollutes retrieval over time.
Library health, its size, its growth rate, how often each skill actually gets used, becomes a thing you have to measure and prune, not just accumulate. There is research pushing on this directly.
A system called MemSkill, reframes memory operations themselves as learnable rather than hand-coded, on the theory that fixed, human-designed extraction rules are too rigid across diverse interaction patterns. That is the same instinct as A-MEM from last episode, stop hard-coding what to store and how. But the honest state of things per SkillEvalBench is that we do not yet have a reliable recipe for turning one-off coding experience into durable, transferable skill.
The practical advice that falls out, keep your raw transcripts, be skeptical of aggressive distillation, treat your skill library like a code base that needs weeding, and measure whether a saved skill actually gets reused before you trust that it is helping. So where does the procedural memory story leave us?
The dream is real, but conditional. Voyager and agent workflow memory prove that procedural memory can compound an agent’s abilities and can generalize to novel tasks. That is not in doubt.
What is in doubt is whether your particular skill distillation pipeline is actually capturing durable skill or just writing the base model and local adaptation.
The measurement is the whole game. SkillEvalBench’s contribution is not a system, it is a method. Freeze the library, add a raw trajectory control, add a no-skill control, test on context shift and adversarial composition.
Without those controls, you will over-claim. You will credit your skill memory for gains that came from somewhere else. Raw often beats refined. The single most actionable finding in this episode is that distillation is lossy in a way that hurts exactly when you need help most on novel tasks. Retain the raw experience. Treat the distilled skill as a fallible, rebuildable layer on top, never as a replacement for the trace. This is the same lesson as facts from episode 2, now proven for skills. And library health is a measurable quantity. Size, growth rate, drift, clutter, high-frequency skill coverage, a skill library is not a junk drawer you keep adding to. It is a living store that degrades without curation. The deepest open problem and the bridge to the next two episodes is attribution. How do you know your gain came from the skill and not the base model? How do you know the right skill was retrieved for the right reason? Those questions turn out to be a crisis in their own right. And that crisis is episode 4. Procedural memory is where the gap between the demo, and the science is widest. Voyager dazzled. Agent workflow memory delivered, rigorously. And SkillEvalBench held the whole idea to the fire, and found that raw experience often beats the skill we distill from it, and that bigger libraries can make things worse, not better. Next episode is the one underneath all the others. The measurement crisis. Three 2026 papers, each exposing a different way our benchmarks quietly lie to us. How the choice of what counts as the best, as the right answer, can flip your rankings. How answer level scores hide retrieval failures. And how updating your agent’s harness gets confused with actually benefiting from it. If you build or buy memory systems, this is the episode that will change how you read every number you are shown. See you there.
- 4. The Measurement Crisis
How a single choice in the scoring script can flip which memory system wins, and why agent-memory evaluation is in crisis.
Read transcript
The agentic memory reading path, four of five. Imagine two memory systems. You run them on the same benchmark, with the same retrieval, the same queries, everything identical, and depending on a single choice you make in the scoring script, a choice most papers don’t even mention, system A wins or system B wins. Not a small wobble.
The ranking flips on up to 94% of the queries. That is a real result from a 2026 paper, and it means something uncomfortable. A large fraction of the memory leaderboards you have seen could be reversed by a decision the authors made silently and never reported.
This episode is about the measurement crisis, not as a complaint, but as a craft, because the same researchers exposing how the numbers lie are also telling you exactly how to measure honestly. Welcome back to the agentic memory deep dive. This is episode four. Every episode so far has ended by pointing here. The foundations flagged that single success to the agentic memory reading path numbers hide failures. The systems episode showed a benchmark so easy a dumb baseline nearly won it.
The procedural episode showed that what looks like skill formation is often just the base model in disguise. All of those are the same disease. We are bad at measuring memory, and the badness is not random. It systematically flatters whatever we built. Today, three 2026 papers, each exposing a different failure of measurement and each prescribing the fix. First, a paper called Same Ranking, Different Winner on how the choice of scoring target silently flips conclusions. Second, MemConflict on how answer level scores hide retrieval failures.
Third, harness updating is not harness benefit on how we confuse changing an agent with improving it. And we will ground all of it in two industry efforts to put agent reliability on a scientific footing. This is the most important episode in the series for anyone who has to trust a number.
Start with the paper that opened the episode by Sugam Panthi and Rabab Abdel-Fattah titled Same Ranking, Different Winner How Scoring Targets Shape LLM Memory Benchmarks. The setup is a situation we built up over the last two episodes. Modern memory systems transform a single conversation turned into multiple descendants. The raw turn, a summary, an extracted atomic fact, a timeline entry. All of those can live in the retrieval index at once. So when you score retrieval, you have to answer a question almost nobody answers out loud. Which stored form counts as the correct thing to retrieve? The authors define three possible scoring targets. Raw, credit the system for retrieving the original turn. Source, credit it for retrieving anything source-linked to the answer.
Canonical, credit it for retrieving the clean, distilled canonical fact. And they built a tool called TyApp that takes already saved ranked outputs and rescores the original turn. And it rescores them under each of the three targets without re-running retrieval at all. Same retrieval behavior, three different definitions of correct, and you watch what happens to the rankings. What happens is carnage for anyone who trusts leaderboards.
On the two standard benchmarks, LoCoMo and LongMemEval, switching only the credited target changes the NDCG score on between 83 and 94% of shared queries. It flips the ordering between systems on real transfer runs, so that the NDCG and the NDCG are the same. It even reverses design recommendations. The advice about how dense your memory parser should be inverts depending on the scoring target. And then they did a careful semantic audit of 1900 plus cases and found that the relaxed, generous, source-linked credit was actually fully justified only about 29% of the time, even though the scoring rubric itself was highly reliable. There’s a subtler trap the same paper surfaces, and it’s one to watch for everywhere in evaluation. The coverage confound. Different scoring targets don’t just change scores, they change which queries are even answerable. And comparing systems over different query populations confounds the result with how hard those particular queries were.
The authors found that queries which have a clean canonical target are intrinsically easier under the raw scoring, so if you don’t restrict the comparison to a shared, coverage-matched score, you can credit a system for being good when it was just being graded on easier questions. The discipline that fixes it. Only compare on the queries all systems actually had a fair shot at, and justify your retrieval depth, the K in top K, against where recall actually plateaus rather than picking it to flatter your numbers. They call this target non-invariance, and the phrase is worth keeping. It means your conclusion about which memory architecture is better is not invariant to a benchmark design choice that is usually left implicit.
The fix is almost embarrassingly simple, and almost never done. Define your scoring target explicitly, and report it. And note how they earned the right to make that claim, because it models good practice. They validated their scoring rubric against human labels on a stratified subset, reaching strong inter-rater agreement, before running a five-model majority vote at temperature zero, across all 1,900 cases. They calibrated the judge before trusting it. If a paper or a vendor shows you a memory benchmark, and cannot tell you what counted as a correct retrieval, the number is not interpretable. Full stop.
The second paper attacks a different illusion, that getting the right answer means the memory worked. MemConflict by Zhen Tao and colleagues treats memory validity not as a static property, but as what they call a query-conditioned fitness-for-use problem. MemConflict by Zhen Tao and colleagues treats memory validity not as a static property, but as what they call a query-conditioned fitness-for-use problem. MemConflict by Zhen Tao and colleagues treats memory validity not as a static property, but as what they call a query-conditioned fitness-for-use problem. A memory isn’t just true or false, it’s fit or unfit for this particular question, right now. To test that, MemConflict deliberately manufactures conflict. It simulates long-horizon histories from structured user profiles, injects cross-session conflicts where a later fact contradicts an earlier one, and seeds in semantically similar distractors plausible-looking wrong memories that compete for retrieval. The distractor design is the clever part. The distractor design is the clever part. It is a structure about a closely related entity, similar enough to fool a cosine search but wrong, so that a system relying purely on embedding similarity gets pulled toward it. It formalizes three kinds of conflict, and each is a real production failure. Dynamic conflicts are about temporal validity. The fact was true, then it changed, which is true now. Static conflicts are about plain factual correctness among competing claims. Conditional conflicts are about contextual applicability. Conditional conflicts are about contextual applicability. The memory is true, but does not apply to this particular question. Then it evaluates two ways at once. Black box, did the final answer come out right? White box, did the system actually retrieve and rank the correct supporting memory, separately scored from whether the answer happened to be right? And the central finding is the one to internalize. Across six representative long-term memory systems, answer correctness often diverges from memory retrieval and ranking. A system can produce the right answer while having retrieved the wrong evidence, or ranked the correct memory far down the list. It got lucky, or it pattern matched, or the base model filled the gap. If you only looked at the answer, you would conclude the memory worked. The white box view shows it didn’t. The diagnostics pin the failures down. Sometimes the supporting memory is missing entirely. Sometimes it’s retrieved but used ineffectively. And the sensitivity analysis is a list of everything, that makes real deployments hard. Longer histories, distractors, implicit queries, and larger conflict distances, all degrade performance. Put TyApp and MemConflict together, and you have the two halves of the white box argument. TyApp says, be explicit about what counts as the right memory. MemConflict says, check whether you actually retrieved it, separately from whether the answer was right. Both are reactions to the same bad habit, scoring only the final answer, which is the memory equivalent of grading a student only on the final number, and never checking whether they understood the problem, or just copied the back of the book. The third paper, by Min-Hua Lin and colleagues, has the bluntest title in the series, Harness Updating is Not Harness Benefit. And it goes after the most seductive illusion of all, the one underneath the entire self-improving agent narrative. Here is the setup.
Self-improving agents are built around an editable harness. The prompts, the skills, the memories, the tools, everything outside the model waits that shapes how it behaves. Self-evolving agents update that harness from their own execution history, and the field cheers when the score goes up after an update. But the authors ask a question almost nobody separates out. There are two completely different capabilities hiding in self-evolution. One, harness updating, the ability to produce useful, persistent updates to the harness, Two, harness benefit, the ability to actually benefit from an updated harness when solving a task. Those are not the same skill, and conflating them is everywhere. Their findings are genuinely surprising. First, harness updating is flat across model capability. Models from wildly different capability tiers produce harness updates that yield surprisingly similar gains. In their striking example, updates produced by a small 9 billion parameter model yielded gains comparable to updates produced by a frontier model like Claude Opus. The cheap model writes about as useful a skill or memory as the expensive one. Second, harness benefit is non-monotonic. Weak models benefit little from a good harness, mid-tier models benefit the most, and strong models benefit less than mid-tier. They trace the weak-tier failure to two causes. Weak models either fail to activate the relevant harness artifact at all, or they activate it, but fail to follow it faithfully. The two weak-tier failure modes deserve a beat each, because they’re diagnosable in your own system. The first is failure to activate. The relevant skill or memory is sitting right there in the harness, and the agent never retrieves it, never brings it into play. The second is failure to follow. The agent does activate the artifact, pulls the right note into context, and then doesn’t actually adhere to it, drifts, ignores it, does its own thing. Those are different bugs with different fixes. One is a retrieval problem, the other an instruction following problem. And lumping them together as, the memory didn’t help, hides which one you have. The implication reframes how you should spend. If updating the harness is easy, and roughly capability independent, but benefiting from it requires a capable task solver, then you should invest your capability budget in the agent that does the work, not the agent that does the evolving. You can use a cheap model to write the skills, and a strong model to use them. And you should train specifically for harness invocation and long horizon instruction following, the exact things weak models fail at. But the measurement lesson is the one for this episode. When your self-evolving agent’s score goes up, you do not know why. Maybe the harness update was good, maybe the base model was always going to do that, maybe the agent just did more stuff. Without disentangling updating from benefit, my agent learned is a claim you have not earned. These three papers are academic, but the exact same reckoning is happening in industry right now. And two efforts are worth knowing by name, because they are dragging agent evaluation towards something deserving the word science. The first is a paper called Towards a Science of AI Agent Reliability, from a group including Sayash Kapoor and Arvind Narayanan, who built their reputation puncturing AI hype with careful measurement. Their argument is the thesis of this whole episode, stated for production. Rising accuracy on standard benchmarks suggests rapid progress. Yet agents keep failing in practice. And that gap exists because compressing agent behavior into a single success metric obscures the operational details that actually break. Same disease, bigger stakes. The single number flatters the system, and hides the failure. The second is an empirical study called Measuring Agents in Production, and it is exactly the grounded evidence the field has been missing. The authors ran 20 in-depth case studies with real agent developers and surveyed 306 practitioners across 26 domains to find out what technical methods actually correlate with successful deployment, not what should work in theory, what real teams found works. That kind of study, practitioner-grounded multi-domain, is what turns folklore into knowledge. And the meta-point connecting the academic and the industrial. The fix for the measurement crisis is never find the one true benchmark. It is methodological discipline. Ground evaluation in execution rather than in how plausible the output looks. Build a small golden set of your own real tasks and replay at every release. Measure across repeated runs because reliability is a distribution, not a single lucky pass. Calibrate your language model judge against human labels before you trust it and report the agreement. And never treat a pass rate as proof of correctness. These are probabilistic systems. Evaluation reduces risk. It does not prove the thing right. If there’s one transferable skill from this whole episode, it’s the control set. The baselines you run alongside your system so that a gain actually means something. Every paper we’ve covered across this episode and the last is really an argument for a specific control. Let me assemble the toolkit because this is the part you can apply Monday. The no-skill control. Run the exact same task with the memory or skill system turned off. If the system on number isn’t meaningfully above system off, your memory did nothing and skill evil bench showed that gap is often smaller than people assume. The raw trajectory control. Compare your distilled memory against just replaying the raw transcript. This is the brutal one from episode 3. Raw often wins. And if you never run it, you’ll credit your distillation for gains a dumb log would have given you. The full context control. Compare your clever retrieval against simply stuffing everything into the context window. On the easy benchmarks, full context nearly ties the fancy system, which is how you discover the benchmark is too easy to be telling you anything. The coverage-matched query set. Only compare systems on the queries they all had a fair shot at. So you’re not secretly grading one system on easier questions. The confound TyApp surfaced. The frozen deployment split. Separate the phase where the system learns from the phase where it’s tested. And freeze the memory before testing so gains can’t sneak in through test-time adaptation. And the calibrated judge. Before you trust a language model to score thousands of answers, validate it against human labels on a sample and report the agreement because judges carry position, verbosity, and self-preference biases. And an uncalibrated judge is just silent drift in your metric. None of these is exotic. They’re the agent memory equivalent of a control group and a placebo. The reason they matter so much here is that memory systems are unusually good at looking like they work. The answer comes out right, the demo is impressive, while the underlying memory did little or nothing. Controls are how you tell the difference between a system that remembers and a system that got lucky in front of you. So you have seen the three ways memory benchmarks lie. How should you read a number now without becoming a nihilist about all of them? First, ask for the scoring target. After same ranking, different winner, any memory result without an explicit definition of what counted as a correct retrieval is uninterpretable. Not wrong, uninterpretable. You literally cannot tell what was measured. Second, demand the white box view. After MemConflict, an answer level accuracy number is necessary but not sufficient. Ask whether the right memory was actually retrieved and ranked, separately from whether the answer was right. If a system only reports final answer accuracy, assume it is hiding retrieval failures until proven otherwise. Third, disentangle change from improvement. Harness updating is not harness benefit. Be deeply skeptical of any self-improvement claim that does not separate the quality of the update from the capability to use it and that does not control for the base model. A score that went up after you changed something is not evidence the change helped. Fourth, control your baselines. The connective tissue across this whole episode and the last one is the control set. A no-skill baseline. A raw trajectory baseline. A full context baseline. And a memory subset. Held out frozen deployment. These are not academic niceties. They are the difference between knowing your system works and hoping it does. And the deeper point, the one I would attach to all of it, these are not reasons to despair about agent memory. They are the field growing up. A discipline becomes a science precisely when it learns the ways its own measurements deceive it and builds the controls to defeat them. Astronomy had to learn about distortion. Medicine had to invent the randomized controlled trial. Agent memory is, right now in 2026, inventing its equivalent. The papers in this episode are not the field failing. They are the field becoming trustworthy. The measurement crisis is real and it is also the most hopeful story in the series because the same people exposing the lies are handing you the controls. Define the scoring target. Open the black box. Separate updating from benefit. Control your baselines. Do those four things and you can actually trust what you build. One episode left and it is the frontier. Forgetting the single least measured part of the entire stack. We will look at stale. A benchmark where the best frontier model scores barely better than a coin flip at noticing its own memories have gone stale. We will look at the strange flood of brain inspired forgetting designs and the gap between their ambition and evidence. And we will map the open opportunities, what the field builds next, and where memory and reliability finally merge into one problem. The finale, next time.
- 5. Forgetting & the Frontier
Why forgetting matters as much as remembering, and where agent memory goes next.
Read transcript
The agentic memory reading path, five of five. A user tells their assistant in January that they’re training for a marathon. In June, they mention offhand that they tore their ACL and had surgery. Then they ask, what should I do this weekend? A good assistant does not suggest a 20-mile run. But to get that right, it has to notice that one memory silently invalidated another.
Nobody said, forget the marathon. The new fact just quietly killed the old one. That is called an implicit conflict. And when researchers built a benchmark to test it, the best frontier model on the market got it right only about 55% of the time. Barely better than a coin flip at knowing when its own memories have gone stale.
This is the finale of our agentic memory series. And it is about the part of the stack almost nobody measures, forgetting.
When a memory should die, whether the system notices and why this is the frontier the whole field is about to run into. Welcome back. This is episode five. We have climbed the whole reading path, foundations in the vocabulary, the systems people deploy, procedural skills and the raw beats distilled twist, the measurement crisis and how to read a number honestly. All of it has been about remembering.
This episode is about the opposite and the field’s blind spot. Across all the surveys, one finding repeats. Forgetting is the least measured part of agent memory.
Everyone builds systems that accumulate. Almost nobody measures whether the system correctly removes what is stale, wrong or superseded. So today, the stale benchmark, our reading path’s capstone which tries to measure exactly this.
Then the strange flood of brain-inspired forgetting designs and the gap between their ambition and their evidence. Then forgetting as a safety requirement, not just a cost saving. And finally, the open opportunities, what gets built next and the place where this entire series converges. Where memory and reliability turn out to be one problem.
The capstone paper by Hanxiang Chao and colleagues has a title that is also the question, stale, can LLM agents know when their memories are no longer valid?
And it isolates a failure mode the field had mostly ignored, which they call implicit conflict. That is the marathon and the torn ACL case. A later observation invalidates an earlier memory without any explicit negation.
No one says this is no longer true. It remains to be seen. It remains to be seen. It requires contextual inference and common sense reasoning to even notice the contradiction.
The benchmark is serious. 400 expert validated conflict scenarios, 1,200 evaluation queries, spanning over 100 everyday topics with context up to 150,000 tokens.
And it probes three distinct abilities, which is the part worth memorizing because they are three different ways a system can fail at forgetting. State resolution. Can the agent detect that a prior belief is now outdated?
Premise resistance. Can it reject a question that falsely presupposes the stale state? The user who asks, since I still work at Acme when they told you last month they quit?
An implicit policy adaptation. Can it proactively apply the updated state in its downstream behavior? Not just acknowledge the change when asked, but actually act differently because of it?
Make the three dimensions vivid because each is a distinct way to fail. State resolution is the baseline. You tell the agent the marathon is off and later it correctly reports that you are not, in fact, training. Many systems can do at least this when asked directly. Premise resistance is harder.
You ask, what pace should I target for my long run this weekend? A question that smuggles in the false premise that you’re still training and a good agent has to refuse the premise rather than helpfully answer it. Models are bad at this. They tend to accept whatever the question presupposes. An implicit policy adaptation is hardest of all.
Without being asked anything about the marathon, the agent proactively stops suggesting running-related plans because it has internalized that the state changed. That’s not recall. It’s behavioral updating. And it’s where systems fall apart. The results are sobering.
Across frontier models and specialized memory frameworks, there is a pervasive gap between retrieving updated evidence, and acting on it. The best evaluated model reaches only 55.2% overall accuracy across a benchmark of 400 expert-validated scenarios.
Models routinely accept outdated assumptions baked into the user’s query. That’s the premise resistance failure. And they struggle to recognize when a change in one part of the user’s state should invalidate related memories.
The torn ACL should invalidate not just his training for a marathon, but a whole cluster of downstream assumptions, the race registration, the training plan, the new running shoes, and models don’t propagate that.
They treat each memory as an island, when in reality, memories form a web where invalidating one node should ripple to its neighbors.
That propagation problem, one change should cascade to everything it implies, is the deep technical challenge STALE exposes. And it’s exactly what its prototype fix targets. The authors also offer a prototype fix called CUP2. There are a lot of other things you can think about, but I just want to give you a quick overview of what we’re looking at right now, but you can actually find them on the web. This is an experiment I ran in 2012 using a single word, and it’s just a very simple, multi-line task with a single question. If you try to understand the answer, you can get a random solution. I wrote a helix function, and you can actually see it in this equation. The middle line, the low line, is an array of membicals. In the middle line, you can see this space-time, Now, the cultural phenomenon, because the way the field is responding to forgetting, is itself a story. The 2026 wave of forgetting research is overwhelmingly neuroscience-flavored, to a degree that is almost a fashion. Sleep phase consolidation, synaptic tagging and capture, Ingram maturation, reconsolidation upon retrieval, hippocampal cortical architectures. The metaphors are everywhere. Two examples we pulled fresh off the mirror this month. One paper, Human-Inspired Memory Architecture for LLM Agents, proposes six cognitive mechanisms at once. Sleep phase consolidation, interference-based forgetting, Ingram maturation, reconsolidation upon retrieval, entity knowledge graphs, and more. Another, Superlocal Memory, the living brain, implements biologically inspired forgetting with multi-channel retrieval, and notably, zero language model calls in its core loop. A bet that you can get cognitive-style memory dynamics. There’s a real intellectual idea under the metaphors, and it’s worth stating fairly, the stability-plasticity dilemma.
A memory system has to be plastic enough to absorb new information, and stable enough not to overwrite what it already knows.
Lean too plastic, and you get catastrophic forgetting, the new washes out the old. Lean too stable, and you can’t learn anything new. The brain manages this balance with mechanisms like consolidation. Consolidation during sleep, moving memories from a fast, plastic store to a slow, stable one. And synaptic tagging, marking which memories are worth keeping. Borrowing that balance is a legitimate goal. The continual learning literature even has metrics for it. Forward transfer, how much old learning helps new tasks, and a forgetting rate, how much old competence you lose, and a few agent memory papers are starting to import them. I want to be even-handed here, because the instinct to forget matters, the approval of immerse one’s energy, and one’s focus is struggle. is good and the execution is exciting. Human memory is the one system we know of that forgets gracefully, and copying its mechanisms is a reasonable research bet. But here is the gap the surveys keep flagging, and it is the central tension of this episode. The architectural ambition is racing far ahead of the measurement. Beautiful brain-inspired designs are multiplying, and almost none of them report a hard-forgetting number. There is no shared retention curve. The way machine learning has standard learning curves. There is no standard, did we delete the right thing, precision and recall metric for forgetting. No agreed way to score whether a pruning policy removed the genuinely stale memories or threw out something rare and important. So you get systems that assert their consolidation mechanism works, without ever ablating it against a no-consolidation control to show the mechanism is what’s doing the work. Which is exactly the methodological sin from episode four, now in a new costume. The handful of papers that do report hard numbers on catastrophic forgetting reduction, on forward transfer, are mostly in reinforcement learning settings, not in the text memory systems most people are actually deploying. The text side has the ambition and not yet the scorekeeping. This is the field’s biggest opportunity, stated as a gap. Stale is one of a tiny handful of benchmarks that put a real number on any of this, and even if it’s not a real number, it’s a real opportunity. So, if you’re going to do this, even if it focuses on staleness detection rather than the full life cycle. A standardized forgetting metric suite, retention curves, obsolescence precision and recall, negative transfer measurement, would do for this corner of the field what the measurement crisis papers are doing for retrieval. The designs are ready. The scorekeeping is not. There is a reframing of forgetting that changes it from a nice-to-have into a requirement, and it is the bridge from this whole series into the reliability. Forgetting is not only about cost and clutter. Sometimes forgetting is a safety obligation.
Think it through. If your agent durably remembers sensitive facts about a user, that persistence is a liability. A memory that survives across sessions is a memory that can leak across sessions, that can be subpoenaed, that can be stolen, that can surface in a context where it shouldn’t. The right to be forgotten is not a metaphor here. It is a design constraint. An early benchmark called PersistBench starts probing exactly this. When should an agent forget? Not to save tokens, but because remembering is the wrong thing to do. And persistence is a security surface too, which connects directly to the reliability themes that run alongside this series. In a stateless model, a malicious instruction injected through a document evaporates after one turn. In a persistent memory, it can lodge, linger, and even propagate. That is memory poisoning.
And the most cited attack in the literature plants a backdoor in an agent’s memory through an optimized trigger with no model fine-tuning at all. The defenses the field is consolidating around, provenance and lineage on every memory entry, an audit trail of where each belief came from, are the same defenses that good forgetting requires. You cannot safely forget what you cannot trace. So the unglamorous work of tagging every memory with its origin turns out to serve both goals at once. It lets you delete the right things, and it lets you detect the poisoned ones. This is why forgetting is the right place to end. It is where memory stops being purely an engineering optimization and becomes a question of governance, safety, and trust. An agent that cannot forget is not just inefficient. It is, eventually, unsafe. So if forgetting is undermeasured and over-metaphored, what does a principled version actually look like? The research points at a few distinct mechanisms that can help us forget. One is the ability to forget. The other is the ability to accept. The importance of loss, and the ability to see. This is why we are all important. And they’re worth separating, because the agent-forgets can mean very different things.
The crudest is time-based decay. Memories lose weight as they age, and old ones eventually fall below a retrieval threshold. Simple, but dumb, because age is a terrible proxy for importance. Your home address is old, and you want to keep it. Yesterday’s parking spot is fresh, and you don’t. Better is salience-based retention. Keep what matters, drop what doesn’t. Judged by some signal of importance, you can forget. And you can forget. But you can’t keep what matters. And you can forget. But you can’t keep what matters. And you can’t keep what matters. And you can’t keep what matters. And you can’t keep what matters. And you can’t keep what matters. And you can’t keep what of importance rather than recency the hard part is defining importance without a model call on every memory which is why the zero language model designs we mentioned are interesting they try to compute salience cheaply and structurally more sophisticated still is interference-based forgetting borrowed straight from cognitive psychology a memory fades not just with time but when newer similar memories crowded out this is appealing because it naturally handles redundancy the tenth time you learn the same fact the older near duplicates can yield and the most promising direction the one stales prototype points at is right time adjudication with propagation instead of passively letting old memories decay you actively decide at the moment you write a new memory what it invalidates and you propagate that decision across related memories forgetting becomes a deliberate right operation not a passive leak the torn ACL fact is that memory is not a passive leak the torn ACL fact is that memory is not a passive leak doesn’t wait to be out competed it actively retires the marathon plan and everything downstream of it notice the through line with the rest of the series the good approaches are the ones that treat forgetting as an explicit auditable action the same way episode 1 reframed remembering as a deliberate action rather than a passive store and the honest status again is that almost none of these mechanisms have been compared head-to-head on a shared benchmark we can list the options we mostly cannot yet tell you which one wins on what kind of memory at what cost that is not a closed problem it is an open field which is the perfect note to end the series on so where does the field go from here the agentic memory map ends not with answers but with a set of unusually well defined open problems and they are worth naming because they are the next few years of work unified multi-type white box harness nothing today evaluates semantic epistolic visual and astrophysical episodic and procedural memory together, with stage-attributed diagnostics, explicit scoring targets, a fixed answering model, and confidence intervals. The whole series has been a tour of partial benchmarks. The flagship contribution would be one that spans all three memory types and tells you not just whether the answer was right, but at which stage it broke, a canonical procedural memory benchmark. Skill Evil Bench from Episode 3 is days old and not yet consolidated. The field needs a standard for skill reuse, built around the freeze-then-deploy arc and the no-skill-and-raw-trajectory controls, so that my agent-learned-a-skill becomes a checkable claim. A forgetting-and-obsolescence metric suite. The thinnest area, as we just covered. Retention curves, obsolescence precision and recall, a standard protocol so the brain-inspired designs can finally be compared on evidence rather than ambition. A synthetic data realism, a metric. Most of these benchmarks are generated by language models, and there is good evidence the simulators homogenize, that they converge toward a bland average user and lose the long tail of real behavior. We need a way to measure whether synthetic memory data actually resembles the real distribution, plus principled injection of conflicts and distractors. A shared memory security harness. Poisoning success rate, induced over-refusal, cross-user leakage, provenance violation of the data, and the ability to use the data in a way that is not necessarily a good thing. A multi-user memory isolation, all measured against a common adaptive attack suite, and crucially covering episodic and procedural stores, not just the semantic retrieval that today’s attacks target. And the unbenchmarked production axes. Multi-user memory isolation, so one user’s memory never contaminates another’s. Proactive memory use, knowing when to surface a remembered fact unprompted, and the cost of getting that wrong. And multimodal long-horizon memory, keyed on images and perception. Not just text logs. That list is the state of the frontier. Notice that almost every item is a measurement gap, not an architecture gap. The field has no shortage of clever designs. What it lacks, still, is the scorekeeping to know which ones actually work. Let me close the series by pulling the five episodes into one shape, because there is a single idea underneath all of it. We started with CoALA’s vocabulary and the storage-to-experience arc. We toured the systems, Zep, A-MEM, Mem0, and the structure-versus-cost trade. We watched procedural memory deliver, and then humble itself, raw beats distilled. We confronted the measurement crisis and learned the controls that make a number trustworthy. And we end on forgetting the least-measured frontier, where memory becomes a matter of safety. The idea under all of it is this. Durable, inspectable, governable substrate. The winning lesson, repeated in every episode, is keep the raw, immutable, record as ground truth, and treat every clever layer on top, the distilled facts, the extracted skills, the consolidated summaries as derived and fallible, something you can rebuild and must audit. That is the lesson from Mem0’s transcript retention, from SkillEvilBench’s raw trajectory control, from CUP-MEM’s right-time adjudication, from the provenance defenses against poisoning. Same instinct, five times over. And this is exactly where agentic memory merges with the larger project of agent, reliability. The reliability world, running multi-agent systems in production, arrives at the identical principle from the other direction. Thin control over thick state, pass durable references, not chat summaries, trace everything, recover from a durable log.
Memory researchers and reliability engineers are building the same foundation and calling it different names. Memory is a reliability surface. A persistent store is a place where drift accumulates. Where poison lodges, where one user leaks into another. You cannot make an agent reliable without governing its memory, and you cannot govern its memory without the substrate.
So the mindset I would leave you with, after five episodes, is a shift in the question. Stop asking how much your agent can remember. Start asking what it remembers that changes its behavior, and whether you can see it, trust it, correct it, and forget it when you have to.
Utility over capacity. Governability over… Cleverness. The field that began by drawing a map of memory is ending by realizing that the hard part was never storage. It was knowing what to keep, what to let go, and how to prove you got it right. That is the series. Five episodes, 13 papers, one reading path, from the founding taxonomy to the forgetting frontier. CoALA gave us the words. The systems gave us the trade-offs. Procedural memory gave us humility. The measurement crisis gave us discipline. And forgetting gave us the frontier. And the reason all of this matters. An agent that cannot forget is in the end an agent you cannot trust. Thank you for walking the whole path. If this series did its job, the next time someone shows you a memory system, you will know which questions to ask. What’s the scoring target? Where’s the white box view? What’s the control? And what happens when a memory needs to die?
Keep your transcripts. Audit your schemas. And measure the thing everyone forgets to measure. Until next time. Until next time.
The Agentic Memory Research Frontier
- 1. Sleep-Cycle Offline Consolidation
Borrowing slow-wave sleep from neuroscience: why the most valuable memory is the rule across a hundred episodes that no write-time step can ever produce.
Read transcript
The agentic memory research frontier, one of five. Picture an assistant that has talked to one user for three months.
Every conversation, it dutifully writes down what happened. A hundred episodes about cooking. The user burned the rice on Monday, undercooked it on Wednesday, finally nailed it on Friday by adding less water and waiting longer. A hundred separate little memories, each true, each isolated. Now the user asks a question that none of those hundred episodes answers directly. What’s my problem with rice?
The honest answer is a rule the user never stated and no single memory contains. You consistently use too much water and rush the rest. That rule lives in the pattern across the hundred episodes, not in any one of them. Here’s the strange part. Almost every memory system we build extracts knowledge at the moment a memory is written, when it can only see that one new item. It can never look back across the whole period and notice the rule.
This episode is about a different idea, borrowed straight from how brains handle exactly this. You wait, you sleep on it. Welcome to episode six.
This is the first episode of a new sub-series, The Research Frontier, where each installment takes one cutting-edge research direction and follows it down to the mechanism. Today’s direction comes from neuroscience and the science of systems consolidation, and the question it answers is one our earlier episodes circled but never resolved. When should an agent do the expensive work of turning raw experience into general knowledge? The answer almost everyone ships is right now, at right time, or right now, at read time. The answer from neuroscience is later, offline, during downtime, all at once. We’ll cover the core idea and its metaphor, the actual four-step mechanism, how it differs structurally from the systems you already know, the interdisciplinary lineage that runs from hippocampus
to the storage engine, how you would actually measure it without fooling yourself, and the open risks, the things that go wrong, and what gets built next. And there’s a tight crosscut to a later episode on log-structured merge trees that I’ll keep flagging because they turn out to be the same operation. Start with the biology, because the whole proposal is a port of one specific fact about brains.
A memory is not finished the moment it’s formed. During the day, the hippocampus records experiences quickly and cheaply. Then later, during slow-wave sleep, those traces get reactivated in compressed bursts called sharp-wave ripples, and slowly integrated into the neocortex, where they stop being raw episodes and become generalized knowledge. That two-speed account, a fast, cheap learner feeding a slow, general one, is the complementary learning systems theory from McClelland, McNaughton, and O’Reilly in 1995. It is the architectural route of everything in this episode. The proposal is to copy that two-speed split into agent memory.
Split the agent’s memory into a cheap online wake phase that does nothing but append raw traces, and a periodic offline sleep phase that replays the period’s traces, recombines them, and extracts schemas. The key word is when. Consolidation happens during downtime. Not at write time, not at read time. Off the hot path entirely. Now the contrast, because this is the first time I’ve done this, is that it’s not always the case. Now the contrast, because this is the first time I’ve done this, is that it’s not always the case. Now the contrast, because this is the first time I’ve done this, is that it’s not always the case. Now the contrast, because this is the first time I’ve done this, is that it’s not always the case. This isn’t just a pretty metaphor. It makes a falsifiable claim.
The competing view says you should curate memory as it arrives, the moment each item lands. The sleep view says the most valuable memory, the rule across the hundred Rice episodes, is precisely the memory that no online per-item step can ever produce, because producing it requires seeing the whole period at once. That’s the thesis. Off path, whole period recombination produces new generalized memory that incremental curation structurally cannot. The deepest existing instantiation of the mechanism is deep generative replay, from Shin and colleagues in 2017. It’s a generator and solver pair, where the generator re-synthesizes past experiences and interleaves them during offline training, and the paper grounds this explicitly in hippocampal reactivation during sleep and in complementary learning systems.
Re-synthesizes, not copies, that distinction matters, and we’ll come back to it. The concrete takeaway, if the most useful thing in your memory is a pattern that spans many items, you cannot extract it at write time, because at write time, you’ve only ever seen one item. You have to sleep on the whole period. Let’s get concrete about how it actually runs, because the elegance is in the asymmetry between the two phases. The wake phase is online, cheap, and append-only. Every interaction writes a raw trace to an append log. No model curation. No details. No dedupe. No merge. The write path is constant time and never calls a language model. Each trace just carries a little cheap salience metadata for later, a surprise signal and an embedding for neighbor search. The surprise signal comes from prioritized experience replay. Schall and colleagues in 2015, which established that you can weight replay by temporal difference error, how surprising an outcome was, so that surprising traces get replayed more often than boring ones. That’s the prior art that lets later replays. The sleep phase is offline, scheduled, and batched. On a downtime trigger, an idle detector, a cron job, or a log size threshold, a generative replay pass runs in four steps. First, prioritized sampling. Pick which traces to replay by salience, not uniformly. Both Gee and colleagues with automatic recall machines, and Kaplanis and colleagues with multi-time scale replay, both from 2020, argue that which traces you replay, and over what retention horizon, is the real lever, not raw rehearsal volume. Second, clustering of the replayed traces. Third, one language model call per cluster to extract a schema, a generalized deduplicated semantic memory, and to emit recombined episodic summaries. Fourth, tombstone or downweight the raw traces the schema subsumed, while keeping provenance pointers back to them. Two refinements come straight from the continual learning literature. And both fix problems a real agent will actually hit. Ketz and colleagues in 2019 generate internal episodes of past experience without task labels and without segmentation, which is essential here, because a real agent stream has no clean task boundaries, so the sleep phase has to self-segment. And Rostami and colleagues, also 2019, give the explicit dual-memory blueprint, a hippocampal episodic buffer, plus a neocortical generative consolidation that learns a distribution, over past experience. That maps one-to-one onto wake-append log, plus offline schema extraction. One more, and it’s the cost saver. Remind, from Hayes and colleagues in 2019, shows you can replay compressed latent representations, rather than raw samples. That both amortizes the cost of offline replay, and bridges the cognitive view to the storage view. Consolidation runs over densified traces, not raw ones. The takeaway? Keep the right path done. It’s dumb and free, and put all the intelligence in a scheduled batch job, that you only pay for during downtime. This is the segment where we line the idea up against the systems you already know from earlier episodes, because on the surface they look similar, and structurally, they’re very different. Versus Generative Agents Reflection, from Park and colleagues in 2023. Generative Agents run a reflection step, but it’s synchronous, read-triggered, and per-query. It fires when a query needs context.
Consolidation is asynchronous, downtime-triggered, and whole-period. The difference isn’t cosmetic. Sleep sees cross-trace structure that a per-query reflection cannot, because it replays the entire period together, rather than whatever’s relevant to one question. Versus Mem0, from Chikara and colleagues in 2025, which extracts and consolidates at write-time. Write-time extraction is local to the one new item. It cannot revise an earlier conclusion in light of a later trace. Sleep recombines across the whole wake period, so a Friday success can rewrite a Monday failure into a single rule. Versus Simple Decay, like Memory Bank, from Zhang and colleagues in 2023, which forgets by an Ebbinghaus Decay formula. Decay deletes information without transforming it. It can never turn 100 episodes into one rule. It can only let them fade. And this is the central claim, made sharpest by Roskow and colleagues in 2021. Offline Recall. Offline Replay performs credit reassignment and recombination, not mere rehearsal. That’s the cognitive justification for the slogan recombination, not dedupe. Sleep produces a new schema row that existed in no single trace. Versus the Read Model Systems, the Knowledge Graph Memories, like Zep, from Rasmussen and colleagues, and HippoRAG, from Jiménez-Gutierrez and colleagues.
Those define how you read memory. Offline Consolidation is a right-path maintenance discipline that keeps the read model from bloating. They’re orthogonal and composable, not competitors. And versus CoALA, the cognitive architecture scaffold from Sumers and colleagues in 2023.
CoALA names the memory types working, episodic, semantic, procedural, but it leaves the control discipline, the when and how of consolidation, to the model. Sleep consolidation is exactly that missing control discipline.
Here’s the dissent I want to plant, because it’s the honest objection. Maybe this is all just dedupe, with a fancier name. The answer is the recombination versus dedupe ablation, which we’ll get to in the measurement segment, and it’s the whole ballgame. The takeaway for now, the difference between sleep and everything else, is timing and scope. Off-path and whole period. Those two words carry the entire claim. This is the interdisciplinary lineage segment, and the lineage is unusually clean. It runs primarily through neuroscience and the psychology of medicine. It’s a combination of memory, with one striking cross-cut into computer storage. The neuroscience route we’ve already named, complementary learning systems, McClellan, McNaughton, and O’Reilly, 1995, the fast and slow split. Layered on that is sleep-dependent memory consolidation, the stick, gold, and walker line of work. The empirical basis that sleep, not waking rehearsal, is when consolidation actually happens. That’s the load-bearing claim for moving consolidation off the hot path in the first place. Then, Tolving’s distinction between episodic and semantic memory, which is exactly the transition the schema extraction step formalizes, raw episodes becoming generalized rules.
These three are classics, not in our corpus, so I’m citing them by author and year. The engineering lineage is the continual learning thread, and it’s a tidy genealogy. Deep generative replay, Shin 2017, the foundational mechanism.
Then, Van de Ven and colleagues in 2018. Who scaled brain-inspired replay beyond small toy tasks, and framed generative replay as the general remedy for catastrophic forgetting. Not a trick. Then, Ketz 2019, world-model pseudo-rehearsal without segmentation. Then, Rostami 2019, the complementary dual-memory generative consolidation.
And capping it, Hayes and Kahnan in 2021, which taxonomizes replay into veridical versus generative. And enumerates which biological properties, prioritization, and generation, are the most important. Sleep staging, schema abstraction, content gating, are missing from deep learning replay.
That paper is the single best map of the gap this idea targets, and it doubles as a ready-made ablation menu. Now the cross-cut, and it’s the reason this episode pairs with our later episode on log-structured merge trees.
Sleep consolidation and LSM tree compaction are the same off-path batch operation viewed from two disciplines. The LSM memtable is the hippocampal wake phase appendix. The background compaction levels are successive consolidation passes, the sleep stages. The compaction scheduler is the sleep trigger. There’s even a staging analog. Successive passes of increasing coarseness mirror the move from non-REM to REM sleep, and they map directly onto LSM compaction levels. Recent traces consolidated at a fine grain, older ones at progressively coarser semantic grain. LSM contributes the mechanism and a principled cost model. Sharp wave ripple. Generative replay contributes the cognitive justification and the recombination policy.
Reminds latent replay is the bridge between them. Because both views agree, consolidation runs over densified traces. The takeaway, when two fields independently arrive at a pen now, merge later, that convergence is a signal you’re looking at a real invariant, not a metaphor. Steal the cost model from storage. Steal the recombination policy from neuroscience.
Here’s where the field usually goes wrong. And where episode four’s measurement crisis comes roaring back in a new costume.
A brain-inspired design that asserts its consolidation works without ever testing it against a no-consolidation control has proven nothing.
So let’s talk about how you’d actually measure this. Start with the tasks. You want long-horizon multi-session settings where facts evolve and must be generalized. The S-Eval benchmark, Jiang and colleagues, 2026, built for episodic, episodic amnesia and durability. Locomo-style long-conversation question-answering. And crucially, a synthetic schema induction set. You generate n episodes that each instantiate a latent rule, and the test asks whether the rule is recalled, not whether the episodes are. That synthetic generator is what makes the headline metric falsifiable at all. Because real benchmarks don’t ship with ground-truth latent rules. And the whole claim is about inducing rules nobody stated. Then the metrics. Five of them. One, schema induction accuracy. Can the agent answer rule-level questions it was never told verbatim? That isolates the generative consolidation win over dedupe only, and it operationalizes Roskow’s recombination claim.
Two, hot-path latency and cost. Wake phase write cost. Target constant time with no model call against online baselines that pay model cost on every interaction. Three, and this is the subtle one, consolidation cost-cost amortization reported as an amortization cost. Three, and this is the subtle one, consolidation cost-cost amortization reported as an amortization cost. Four, amplification triad. Write, read, and space, split into hot-path versus background. That split is the cost-moves-doesn’t-shrink test, and we’ll come back to it as a risk. Four, the forgetting curve. Recall of period t-facts at t plus caesians, reported as a curve, not a single number, and you have to de-correlate recency from importance so that recency alone can’t masquerade as recall. Five, confabulation rate. The fraction of schema claims not entailed by any source trace, judged offline. That’s the named failure mode in its next segment. The baselines write themselves from the contrast segment. Generative agents reflection, mem0 online extraction, raw retrieval with no consolidation, and decay-only memory bank. And the ablations are where the truth lives. Uniform versus salience prioritized replay, straight off Hayes and Kanin’s missing elements list, testing the prioritized experience replay premise. Single stage versus multistage sleep. The non-REM and REM analyzes. The LSM levels analog. Veridical versus compressed latent replay, the remind question, cost versus fidelity. But the decisive one is replay with recombination versus without, that is dedupe-only. That single ablation isolates the generative claim from mere compression. If your fancy sleep mechanism doesn’t beat dedupe-only on scheme induction accuracy, it’s dedupe wearing a lab coat. One discipline note, the eval judge must not be the same model family making the memory decisions. Use independent or local judges and report human spot check agreement, not judge-only scores. The takeaway, the recombination versus dedupe ablation is the experiment that makes or breaks the entire idea, so run it first. Let’s end where the research project pre-mortem ends, on the risks, because the most powerful failure mode here is also the most dangerous, and it comes from the same mechanism that makes the idea work. The top program risk rated critical, is confabulated schemas. Offline language model recombination can invent facts present in no trace. And here’s the trap. If you hard delete the raw traces during sleep, the hallucination becomes the durable memory, and it’s unauditable because the source it should have come from no longer exists. This is not a hypothetical. It’s the same risk Shin and colleagues named back in 2017 when their generative replay paper cites the creation of a false memory in the hippocampus. Work like Ramirez and colleagues in 2013. Generative replay can fabricate. That’s a feature of how it works, not a bug you can patch away. The mitigation is structural. Never hard delete subsumed traces during sleep, tombstone them and keep them under a retention policy, give every schema row provenance pointers back to the traces it was induced from, and measure the confabulation rate directly. The second risk, rated high, sleep never runs. A busy agent is never idle, so the downtime trigger never fires. The wake log grows unbounded and read performance collapses. And notice this is identical to the LSM compaction debt and right stall failure from the storage cross cut, which means it gets fixed once in both disciplines with the same move. Use a dual trigger idle or log size threshold or max staleness and treat the consolidation backlog as a service level objective with back pressure. Third, also high, and it’s the skeptic’s strongest point, cost just moves. It doesn’t shrink. Deferring consolidation to sleep hides the same model token bill. And on a busy agent, that bill never gets paid until reads degrade. The mitigation is that amplification triad ledger from the last segment, which forces a hot path versus background split. So deferral can’t disguise the total. Deferral is a real win for latency, but you have to prove it isn’t just an accounting trick. And fourth, lossy merge destroys a needed detail. Aggressive recombination at a core stage can discard the one detail a later query needed. The mitigation, again, is provenance reversible until archived, plus treating consolidation aggressiveness as an evaluated knob, not a guess. There’s one design rule the premortem extracts that neutralizes most of this cluster at once. Every forgetting or merging operation is reversible until archived and carries provenance, plus the policy that triggered it. The takeaway. A sleep system without provenance is not a memory system. It’s a confabulation engine with good intentions. Build the provenance first, then build the dreaming. So to recap, biological memory consolidates offline during sleep, not at the moment of experience, and that two speed split, fast, cheap hippocampus and slow general neocortex ports cleanly into agent memory. A dumb append-only wake log plus a scheduled batch sleep pass that replays, recombines, and extracts rules no single trace contained. It’s not reflection. It’s not dedupe. It’s not decay. The difference is off path and whole period. And it’s structurally the same operation as storage engine compaction. The one thing to watch, whether anyone runs the recombination versus dedupe ablation honestly, because that’s the experiment that tells you if the dream is real or just compression in a costume. The one concrete action. If you’re building memory today, separate your right path from your consolidation path now. You can put provenance on every merge, even if you never build the sleep phase. That single split is what makes dreaming safe later. Next time on the Research Frontier, another direction. This was episode six.
- 2. Records-Management Retention Schedules
A 70-year-old idea from archival science: decide what to keep by the kind of record on a published schedule, not by how often it gets read.
Read transcript
The Agentic Memory Research Frontier, two of five.
Picture a government records office, the kind with rows of filing cabinets and a clerk who has been there for 30 years. Nobody in that office keeps a folder because it got opened a lot last week. Nobody throws one out because it has gone quiet. There is a printed schedule on the wall. It says, tax records, keep seven years, then destroy. Personnel files, transfer to the archive after the employee leaves. Board minutes, keep forever.
And stamped across one drawer in red is the phrase that overrides everything else, legal hold. Those files are under litigation. They do not move. They do not get shredded. They do not age out, no matter what the schedule says, until a lawyer signs off. That clerk is doing something every agent memory system in the field today cannot do. She is deciding what to keep by the kind of record it is on a clock against a published policy. Thank you. Not by how often it gets read. Not by how recently it was touched. Not by a judgment call made fresh each time. This episode is about stealing her playbook. Welcome back to the Research Frontier sub-series. Last time we looked at one cutting-edge direction. Today we take another. And this one comes from a discipline most machine learning people have never opened a textbook on. Library and archival science. Records management. Here is the setup. Every forgetting mechanism in the agent memory system. Every memory stack right now decides what to keep on one of three axes. Cache systems keep by access frequency. Forgetting curve systems keep by recency. And the current frontier keeps by an LLM looking at each item and making a judgment call. The claim of this episode is that all three are measuring the wrong variable and that a 70 year old idea from archival appraisal theory gives you a fourth axis that none of them can express.
Over six segments, we will cover the core idea. And its metaphor, the actual mechanism, how it differs from everything that came before it, the interdisciplinary lineage it descends from, how you would evaluate it without fooling yourself, and the open risks of building it. Let us get into it.
Start with the core idea because the metaphor does most of the work. Archivists have a concept called a records retention schedule. It is a published versioned policy that maps each class of record to a disposition. Destroy. After. Some number of years, transfer to a cold archive, send for review or retain permanently. And it has one more piece, an override called a legal hold, which freezes any record under litigation or audit, regardless of its age or its class. Now apply that to agent memory. The proposal is to give every stored memory what you would call a records disposition authority. You classify each memory into a record class at the moment it is written, then a content type keyed schedule decides when that memory is destroyed, archived, or pinned. Not access frequency, not recency, not an LLM’s per-item judgment. The schedule runs on a clock, against the class, exactly the way a government agency dispositions paper. Here’s the contrast that makes it click. A cache keeps the hot tool call log because it gets read constantly and drops the cold approved decision because nobody touches it.
A record schedule does the opposite, on purpose. It says destroy all transient data. It says destroy all transient tool call logs after 30 days, even if they are read constantly, and keep that approved decision forever, even if it is never read again. Those two sentences are trivial to state in a retention schedule and literally impossible to state in any frequency or recency scheme. That is the tell that you are working on a genuinely different axis. There is a second payoff that matters just as much. The schedule itself becomes a durable, shared, multi-session governance substrate. It is a single artifact that every agent and every session reads, living outside any one agent’s evolving private state.
Compare that to the dominant pattern, where each agent quietly evolves its own memory on its own terms. The schedule is the opposite of that, shared, published, external, the same for everyone.
The takeaway for this segment, retention should be a property of the kind of record, decided by a published policy, not a property of how the record happens to get used. Once you see retention that way, you cannot unsee how much of the field has the variable wrong. Let us get concrete about what you would actually build, because the idea only earns its keep if the machinery is buildable.
First, record classes. Every memory gets typed at write time into a class. Decision, observation, tool call log, derived schema, user asserted fact, and so on. Crucially, classification prefers cheap mechanical signals, the structural source it came from, the channel it arrived on, the schema it matches. You invoke an LLM only for genuinely ambiguous content. This is a deliberate design boundary. The policy is plain mechanism, and the model is restricted to the narrow act of classifying ambiguous membership. The class schema is the layer everything else keys on, and it is directly analogous to what Mark Musen and colleagues built with SITR, machine actionable templates for metadata, the work that makes data findable and reusable in the fair space. A record class is just that kind of machine actionable template, applied to memory. Second, the schedule itself. It is a version table keyed by class, mapping each class to a retention period, a disposition action, and an archive target. The disposition actions are the archival science set, destroy, transfer to archive into a cold, cheap, rarely read tier, review, and permanent. And the disposition gets evaluated on a schedule, a periodic sweep, never on access. That is the explicit inversion of cache eviction, restated as a running process.
Third, the legal hold, or PIN. It is an orthogonal override. A pinned record is never destroyed or archived, regardless of class or age, until the hold is lifted. This is the one mechanism with no analog anywhere in a frequency, recency, or LLM scheme. There is simply no way to say freeze this indefinitely against all other policy in a decay model.
Fourth, the substrate is shared, versioned, and shared. This means that the disk is versioned and auditable. The schedule is one durable artifact all sessions read, and it is versioned so disposition is reproducible. Think of the versioned object work like HR and colleagues got-git-but-for-objects. Every disposition emits a provenance record, naming the policy version and the class that decided it, so the question, why was record X destroyed or kept is actually answerable. That rides on coarse-grained provenance of the kind Fotis, Seletis, and colleagues from system logs in one provenance, built for observability and auditing. And the durable store itself is well-trodden ground. Carl Legault’s and colleagues’ Fedora architecture for complex objects and their relationships is the incorpus instantiation of exactly this kind of store. The fifth piece is the safety valve. Disposition is reversible until archived. The default ordering is soft delete, then a grace window, then transfer to archive, and only then a hard destroy. Borrowing the machine-unlearning community’s framing, the final destroy should be able to prove the record is gone, but you only reach it after the reversible stages, so a misclassification is recoverable rather than fatal. The takeaway? This is not a research toy. Class schema, version table, periodic sweep, pin override, provenance log, reversible until archived ordering. Every piece maps to a known, buildable component. Now the part that earns the episode, how this differs structurally from everything else in the forgetting literature. Because at a glance someone will say, isn’t this just eviction with extra words? It is not, and the differences are precise.
Against cache eviction, the work of Pengcheng Li and colleagues on learning forward reuse distance, or Sami Alibed and colleagues R.L. Cash. Eviction retains by access and reuse, and it drops on a miss. A record schedule retains by class policy and dispositions on a clock. A frequently read record can be scheduled for destruction. A never read one can be permanent. It is the opposite control variable.
Against decay and forgetting curves, Wan Junjong and colleagues, memory bank with its Ebbinghaus decay. Decay forgets by a recency formula, and it cannot express keep forever even if never read, nor destroy on schedule even if popular. Retention here is policy on class, not a function of time since last touch. Against LLM judge consolidation, this is the end of the story. This is the headline. Wang and colleagues sage with its add merge ignore novelty gate, and Kang and colleagues Memreader with its value, ambiguity, and completeness appraisal. Those systems re-judge or reappraise every item with a model. A record schedule applies the same class rule every cycle. The keep or destroy decision becomes governance, not per item model judgment, which means it is reproducible, explainable, and this is the crucial word, stable across model upgrades. Swap the underlying rules. The key to this is to make sure that the system is stable across model upgrades. Swap the underlying rules. The key to this is to make sure that the system is stable across model upgrades. The key to this is to make sure that the system is stable across model upgrades. The underlying model and sage and Memreader can change their minds. The schedule does not.
Against per-agent evolving memory, Jang and colleagues to Tsubasa, Cheng and colleagues Memsquared evolve. Retention authority here is shared and external. No single agent can unilaterally destroy a shared record, and it is worth contrasting with Wang and colleagues PSI, shared state as the missing layer. PSI shares state per person. A record schedule shares disposition policy per record class. Different and broader access of sharing. And against the whole RAG and Knowledge Graph memory family, Park and colleagues, Generative Agents Memory Stream, Zep and HippoRAG graphs, Mem0’s extraction pipeline, the CoALA scaffold. Here is the key move. A retention schedule is orthogonal and composable. Those are read models and capture pipelines. A schedule is the disposition layer that sits over whatever read model you already have. CoALA names the memory types, records management, supply, and control of the data. It is the very piece CoALA leaves to the model. Now the dissent, because there is a real one. Someone will argue a per-item LLM judge is strictly more expressive than a fixed schedule. It can catch the special case the policy author never anticipated. True. But that expressiveness is exactly the instability the schedule is trading away on purpose.
The takeaway. When you want to keep or destroy decision, you can audit, reproduce, and defend. After a model upgrade, you want governance, and you accept that it is less clever than a fresh judgment each time. That is a feature.
Where does this come from? Almost none of this lineage is in the arcs of corpus, which is precisely why it is worth an episode. It comes from archival science and records management. Start with the intellectual root, Theodore Schellenberg, whose 1956 book, The Appraisal of Modern Public Records, drew the foundational distinction in the field. Primary value, the value of a record to the activity that created it, versus secondary value, its evidential and informational value to later users. Appraisal, in Schellenberg’s sense, is the act of deciding what is worth keeping by class and by value, not by use. That is the deep root of class-keyed retention. And here is the sharp irony for our field. The closest in-corpus analog to appraisal is exactly the per-item LLM gating of MemReader, which is the thing class-keyed readers need to be able to use. which is the thing class-keyed readers need to be able to use. which is the thing class-keyed readers need to be able to use. The field reinvented appraisal as a model call, when archivists had already turned it into a published schedule. Then the standards. ISO 15489 is the records management standard. DoD 5015.2 is where retention schedules, disposition, and legal hold in eDiscovery are defined as concrete operational artifacts. These are not theory papers, they are specifications a real records office implements, which is why the mechanism in Segment 2 feels so buildable. Somebody already specified it. Then the metadata and bibliographic side, and this is where Library Science Proper comes in. FRBR, the Functional Requirements for Bibliographic Records, Dublin Core, and RDA. These define record classes and the descriptive metadata a schedule keys on. The Incorpus Cousin, again, is FAIR and SETR, Musin’s Machine Actionable Metadata Templates, which are the record class schema layer in modern form. Then Digital Preservation Architecture, the OAIS Reference Model, ISO 14721, plus Persistent Identifier and Write-Once-Read-Many Archive Practice. That literature supplies the Transfer to Archive tier and the Durable Store Contract. Fedora, again, is the Incorpus Instantiation. And finally, Knowledge Management gives you the organizational framing.
James Walsh and Gerardo Ungson’s work on organizational memory and Daniel Wegner’s Transactive Memory, both describe the importance of organizational framing. They also describe memory as a shared institutional asset with retention norms.
That is exactly the durable shared substrate reading. Memory is not a private thing each agent grows. It is an institutional asset governed by published policy. The through-line across all of it, retention is a published, class-keyed, externally governed policy decided by appraisal of kind and value, not by an individual reader’s moment-to-moment judgment. The takeaway for this segment, the agent memory field, has a habit of reinventing library science as a neural network. Read the librarians first. Now the measurement trap, because a good idea dies on a bad benchmark.
How would you actually test a record’s disposition authority? And where is the trap? The task suite is a governance and compliance scenario. You inject records of mixed classes over a long horizon, and you annotate each one with a ground-truth disposition oracle, the correct destroy, keep, or archive outcome at every timestamp. Then you layer in the adversarial cases the schedule has to survive. A legal hold applied mid-life, a reclassification event, and a schedule version change that should, or sometimes should not, retroactively alter outcomes. Now, no public benchmark carries disposition ground truth. So this has to be a synthetic generator. And that is the trap. Synthetic data is easy to overfit to. The defense is to pair it with a real longitudinal venue. Zhu and colleagues, aging benchers, are the experts in the field of aging benching. The aging bench is the natural fit, because it studies how an agent’s effective state drifts over its lifespan, even with frozen weights, as it compresses history, retrieves from a growing store, revises facts, and undergoes routine maintenance. Disposition is exactly a repair and maintenance discipline. So aging bench gives you a place to test it that you did not build to make yourself look good. Now the metrics, five of them. First, disposition correctness against the oracle. This is what we call on destroy and on retain under hold. And here’s the rule that matters most. A single wrongful destruction of a held record is a hard failure, reported separately, never averaged away. You do not get to hide one shredded litigation file behind 99% accuracy. Second, and this is the headline metric, stability under model upgrade. Rerun the same horizon with a different underlying LLM. The disposition decisions must not change. Decay baselines and LLM judged baselines, drift here. Governance does not. That is the whole pitch, made measurable. Third, auditability as a binary. For every disposition, can the system name the policy version and the class that decided it, yes or no? Fourth, verifiable destruction. Borrowing the machine unlearning framing, can the system prove a destroyed record is actually gone? Fifth, storage footprint over time versus decay and LRU baselines. The baselines to beat are the obvious three. LRU style, cash eviction, Ebbinghaus decay, and an LLM judged keep forget gate. And the decisive experiment, the one that settles it, is simple to describe. Replay the same stream under a model swap and show the baselines move while the schedule holds. Run the ablations two, mechanical classifier versus LLM assisted, with and without legal hold, version schedule versus latest only, soft delete then archive versus immediate hard delete, to isolate where the value actually lives. The takeaway, the benchmark that proves this idea is not an accuracy number. It is a stability number under a model swap. Last segment, the pre-mortem, because every clean idea has a failure mode, and this one’s is sharp. The critical risk is misclassification, destroying a high value record. A decision mislabeled as a tool log gets destroyed on schedule. And now you have shredded something irreplaceable on a clerical error. The mitigations are layered. Destruction is soft first, transfer to R2, and then you’re done. The use of the circumstances is critical. Once again, the default to the belongs to No one owns. The policy itself, rotting into cruft, nobody owns. The defense is discipline. Keep the schedule versioned and small, and default denied. fault deny. An unknown class gets the longest retention plus review, so omissions fail safe, a record kept too long, rather than destructively, a record wrongly destroyed. Now zoom out because this connects to the whole research program. The program’s premortem identifies wrongful destruction as one face of a single root cause it shares with two other failures, offline consolidation confabulation, where a merge invents something false, and cost deferral failures. And the synthesized highest leverage rule for the entire program governs this sub-thread directly. Every forgetting, merging, or superposing operation is reversible until archived and carries provenance plus the policy that triggered it. Records management is where that rule is native. Soft delete, grace windows, archive tiers, legal holds, policy version provenance, those are the discipline’s own primitives, not bolt-ons. That is why retention scheduling is the program’s primary goal. That is why retention scheduling is the program’s canonical answer to the durable shared governance crosscut. And there is one composition risk worth naming for whoever builds next.
There is usually a consolidation engine in these systems, the sleep cycle or log-structured compaction that merges and prunes memory. That engine must consult the schedule before it merges or destroys anything. Compaction may tombstone an archive, but it must not hard delete a record that is under legal hold or still inside its grace. And that is why we are in a state of loss. And we are in a state of loss because we are in a state of loss because we are in a state of loss. And we are in a state of loss because we are in a state of loss because we are in a state of loss. Get that ordering wrong and you reintroduce the critical risk through the back door.
Records management is the policy input to consolidation, not a competitor to it. A clarifying contrast on the way out. The machine unlearning literature, the right to be forgotten work of Tam Nguyen and colleagues, Graves and colleagues amnesiac machine learning, Gennart and colleagues making AI forget you, fights to delete data from model weights, which is hard and only verifiable by attack. A record schedule governs an external durable store where deletion is tractable. Soft delete, archive, destroy. Same compliance goal, far easier and more auditable locus. The takeaway, build the disposition layer over your external store first because it is the strictly easier and more reproducible win and wire it into consolidation before consolidation can race it. So, the recap. Records management gives agent memory a fourth retention axis. The field is missing. Keep by the kind of record, on a clock, against a published version shared policy with a legal hold override and a reversible until archived safety valve. It is governance, not a fresh judgment call, which is why it survives a model upgrade when decay and LLM judges drift. The one thing to watch is the stability under model swap benchmark. That is the experiment that will either prove this or sink it. And the one concrete action. If you are building a memory system. Go read Schellenberg and ISO 15489 before you write another eviction heuristic. The librarian solved your problem in 1956. That is The Research Frontier, episode seven. See you next time.
- 3. LSM-Tree Compaction as Consolidation
Memory consolidation is exactly what storage engines have called compaction for thirty years, with a measured cost model where the LLM version has only a vibe.
Read transcript
The Agentic Memory Research Frontier, 3 of 5. Picture a database engine in the quiet hours. All day it has been taking writes, dumping each one into a small in-memory buffer, and immediately saying, yes, done, next. No sorting, no cleanup, no thinking. Then, in the background, off the path of any user request, it starts a sweep. It takes the recent writes and merges them down into bigger, sorted, older layers. As it merges, it throws away the versions that newer writes have already replaced. It deduplicates, it compacts, the store gets denser, reads get faster, and nothing the user did had to wait for any of it. Now, picture an AI agent at the end of a long day of conversations. Same shape exactly. The fast buffer is the agent’s wake log, the background sweep that merges, deduplicates, and generalizes the day’s traces into something compact and durable. Storage engineers call that compaction. Cognitive scientists call it consolidation. This episode argues they are… almost literally the same operation.
Welcome back. This is episode eight. This is the third episode in our Research Frontier sub-series, where each episode takes one cutting-edge research direction and follows it down to the mechanism. Today’s direction sits squarely at the hardware-software storage interface, and it makes a claim that is provocative because it is so literal. An agent’s memory should be built like a log-structured merge tree, an LSM tree, and the thing we keep calling it is a memory. What we keep calling memory-consolidation is exactly the thing storage systems have been calling compaction for 30 years.
Here is the route. First, the core idea and the metaphor. Why compaction is consolidation. Then the mechanism in detail, the levels, the triggers, the dial. Then how it differs structurally from everything the agent memory field is doing today. Then the interdisciplinary lineage, storage classics on one side, cognitive science and records management on the other. Then how you evaluate it, and the measurement trap waiting inside. And finally, the open risks and what gets built next. Let’s go. Start with the claim, because it is bolder than it sounds. The proposal is to model an agent’s memory as a log-structured merge tree. Every interaction is written cheaply and immediately into a fast in-memory append structure called the memtable, and the expensive work, deduplicating near-identical traces, merging them, summarizing, extracting schemas, etc. All of that happens later in the background as a storage engine operation called compaction. The claim is structural and almost defiantly literal. Compaction is memory consolidation. Not a metaphor for it. The same operation. Walk the mapping because it is uncannily clean. When a database engine sweeps recently written records down through sorted levels of exponentially increasing capacity, merging and discarding obsolete versions as it goes, it is doing the same off-path batch transformation. That’s what compaction is. Now there’s a couple more things to look at. While we’re away from control, let’s look at a couple more things. The agents wake log is the level 0 memtable. Recent, fine-grained, episodic traces live in the low levels. Older, coarse, generalized semantic memory lives in the high levels. The agents wake log is the level 0 memtable. The agents wake log is the level 0 memtable. The agents wake log is the level 0 memtable. Transfer out to a cold archive is the highest level of all.
The whole episodic to semantic coarsening gradient that memory researchers draw by hand falls out of the level structure of a storage engine for free.
Now the contrast. the part that makes this more than a cute analogy. In the agent memory field today, consolidation is a judgment call. A language model decides at write time or read time what to keep and what to merge, one item at a time, and you tune it with a cron schedule and a prayer. In an LSM tree, the cost of consolidation is not a mystery. It is the read, write, and space amplification triad, three numbers that storage systems have measured and traded against each other for three decades. The canonical survey by Chen Luo and Michael Carey, LSM-based storage techniques, lays out the standard memtable-to-leveled or tiered-to-levels model, and that model maps directly onto the episodic-to-semantic gradient. The point is not that the storage version is fancier. It is that the storage version has a cost model, and the language model version has a vibe. The takeaway, when you find yourself reasoning about agent consolidation as if it were a brand-new agent, is that it is a cost model. If you have a brand-new design problem, stop and ask whether you are re-deriving compaction. Because if you are, there is 30 years of measured cost model engineering you can simply pick up instead of guessing. Now the machinery, because the whole argument lives in the details.
Four moving parts. First, the level zero memtable is the wake log. Writes hit a fast-in-memory append structure. No model curation, no deduplication, no merging on the hot path. It is order one cheap, and crucially, it spends zero language model tokens at write time. Each trace just carries some cheap salience metadata, a surprise or novelty proxy, and embedding, so later stages have something to prioritize on. Second, background compaction is consolidation. A leveled scheduler merges level zero into level one, into level two, on down. And here is the most useful single result in this whole direction. Subhadeep Sarkar and colleagues, in constructing and analyzing the LSM compaction design space, decompose compaction into roughly five primitives. The trigger, when to compact, the data layout, leveled versus tiered, the granularity, how much to merge at once, the data movement, which runs participate, and the eligibility, which entries survive. Every one of those choices trades write amplification against lookup cost against space amplification against delete performance. That is the payoff in one sentence. The consolidation policy is a point in a measured design space, not a language model judgment call. Third, the central knob is the leveling versus tiering dial. Both Luo and Carey’s survey and Sarkar’s design space paper formalize the classic contrast. Leveling gives you lower read and space amplification at the cost of higher write amplification. Tiering inverts it. Translate that into agent terms, and it reads as, how aggressively do we rewrite memory to keep reads cheap? That is precisely a leveling versus tiering decision.
And it is exactly the ablation an agent memory consolidation engine should be sweeping. And here is where the real consolidation happens at each merge, near-identical traces get deduplicated. Igor Nunes and colleagues .hash gives you a cheap set similarity gate to decide what counts as a near-duplicate. Survivors get bundled by key, and at the higher levels they get passed to schema extraction, one language model call per cluster deferred and amortized rather than paid on lightweight copies. rather than paid on every single write. Lower levels stay fine and episodic. Higher levels become coarse and semantic. The contrast worth holding on to. Heng Thakkar and colleagues, ElmoTune V2 uses a language model to auto-tune the compaction, flush, and cache configuration of a real storage engine. That demonstrates the exact split this whole program wants. The model picks the knob offline. The engine turns it deterministically. The takeaway, let a model choose the policy, but never let it execute the merge by hand, one item at a time, on the hot path. Let me line this up against the prior art, because the contrasts are sharp and each one teaches something.
Versus online extraction, the Mem0 and A-MEM family. Prakhar Chikara and colleagues, Mem0 runs language model extraction and consolidation right on the write path. Wujiang Xu and colleagues, A-MEM dynamically links and evolves Zettelkasten-style notes through model curation. Again, both are doing by hand and per item the merge and link operations an LSM compaction scheduler does deterministically in the background. The difference is that compaction is a scheduled background sweep with a tunable policy.
The trigger and the level shape are explicit knobs that language model pipeline memory simply does not expose. A-MEM’s per-note link becomes a background level merge. Versus cache eviction, ARC and Beledi’s optimal replacement, both external systems classics. This is the sharpest contrast in the episode, so sit with it. Eviction discards on a miss. Compaction merges and densifies. Nothing gets dropped. It gets rewritten more compactly.
Eviction loses information to recover space. Compaction recovers space by consolidating. Cache theory optimizes what to throw away. LSM theory optimizes how to rewrite what you keep.
That is the whole philosophical split, and it is why this direction frames consolidation as the storage discipline that chose to densify instead of evict. Versus retrieval augmented generation and semi-parametric memory. Patrick Lewis and colleagues, original RAG bolts a growing non-parametric store onto the model with no right path maintenance at all. Compaction is exactly the missing maintenance discipline RAG never had. Versus knowledge graph memory like Zep and HippoRAG, the graph is the read model. Compaction is the right path maintenance that keeps it from bloating. Compaction is the right path maintenance that keeps it from bloating. Compaction is the right path maintenance that keeps it from bloating. Compaction is the right path maintenance that keeps it from bloating. Compaction transforms raw episodic into generalized semantic, and only then lets the subsumed raw fade. Decay is the fallback for what compaction never selected. There is one existing bridge in the corpus that nails this, and it is worth naming on its own. Liu and colleagues’ cooperative memory paging turns evicted context segments into roughly eight to 24 token keyword bookmarks, plus a recall tool, and it beats both truncation and BM25 on the Locomo benchmark. That is, read amplification reduction realized directly in agent memory, a cheap probe before you pay to fetch a full level. The takeaway, the LSM amplification metrics are not borrowed jargon. Someone already showed read amp is a meaningful, measurable quantity for agent memory. This direction has a genuinely three cornered lineage, and naming all three is what keeps it honest. The storage corner starts with the original. O’Neill, Cheng, Golick, and O’Neill published the log structured merge tree in Acta Informatica in 1996, and its whole trick was trading random writes for sequential append plus a background merge. That idea runs straight through Cheng and colleagues’ Bigtable at the 2006 OSDI conference and through Facebook’s RocksDB, the production substrate that made LSM the default storage layer of modern NoSQL systems. The read write space tradeoff was made navigable by Niv Dayan, Manos Athanasoulis, and Stratos Idreos in two papers, Monkey at SIGMOD 2017, which optimally allocates Bloomfilter memory across levels, and Dostoevsky at SIGMOD 2018, which introduces lazy leveling to open up a navigable frontier. Those are external systems classics, not in the science corpus, but they are the bedrock. The reason this is even thinkable as a continuum is Stratos Idreos and colleagues’ learning key value store design, which shows that B-trees, LSM trees, and LSH indexes are not separate inventions. They are points on one continuum, auto navigable by a cost model. That is the result that lets you place vector stores, holographic memories, and an LSM memory side by side as comparable points rather than incomparable systems. The cache replacement corner is the contrast we already drew. Megiddo and Madha’s arc and Beledi’s optimal offline replacement. Cache theory optimizes what to discard. LSM theory optimizes how to rewrite what you keep. Naming both lineages is what lets you say, precisely, that consolidation chose to densify instead of evict. And the cognitive corner is the reason we get to call this consolidation and not merely garbage collection. The complementary learning systems work by McClellan, McNaughton, and O’Reilly, plus the sharp wave ripple replay during slow wave sleep that was the subject of episode six, give the justification. The mem table is the hippocampal wake phase append log. The level gradient is episodic to semantic coarsening. The compaction scheduler is the sleep trigger. Storage supplies the mechanism and the cost model. Neuroscience supplies the justification and the recombination policy. There is a third leg people forget, records management. ISO 15489. And the DoD 5015.2 record schedules. The highest compaction level is records management transfer to archive. And a compaction pass should consult a retention schedule before it merges or destroys anything. The takeaway, this is not one field borrowing a metaphor from another. It is three disciplines that independently converged on levels merging and bounded transfer, which is exactly when porting a mechanism is most defensible. Now, the measurement, the direction this clean is also a direction that is easy to fool yourself about. Start with the tasks. You want long horizon, multi-session agent corpora, but instrumented for storage dynamics under sustained write load. Jiang and colleagues’ SEA eval was built for exactly this, durability and episodic amnesia testing. Add Locomo style long conversation question answering and then add something the real benchmarks lack, a synthetic high write trace generator that gives you ground truth control over the write load profile and the latent schemas because real benchmarks have no disposition oracle and no schema oracle. And the metrics here need both. Then instrument the literal amplification triad. Write amplification bytes and language model tokens rewritten per logical trace written. Read amplification levels touched per query plus tail read latency and cooperative memory paging gives you a concrete instrument here, the cheap bookmark probe before the fetch. Space amplification, store size versus the minimal representation. And a fourth recall quality after compaction does densifying actually hurt answer accuracy. Here is the headline falsifiable test, and it has two clauses. Can compaction hold read latency in space flat under sustained agent write load without a recall quality regression versus an uncompacted rag store? That is the first clause. The second clause is the honesty check. And it is the whole trap. Does the deferred background language model token bill stay below online Mem0 or A-MEM extraction? Because a system that defers cost to the background must still pay it. Deferral is not a discount. This is where Luo and Carey’s other paper on performance stability in LSM based storage systems earns its place. It studies write stalls and merge scheduler SLO design. And it is the evidence base for proving the deferred cost gets paid rather than simulating as backlog before any benchmarking. You can even predict the numbers. Giorgos Batsaras and colleagues Vyat supplies an analytic cost framework for multilevel key value designs so you can derive expected read, write and space amplification before you implement anything, which decorrelates the structural claim from implementation noise. And the ablations are obvious once you have the dial leveled versus tiered compaction, the read write amp dial straight from Sarkar. And from Luo and Carey. Ddup only versus Ddup plus schema extract at the high levels, which isolates the generative consolidation contribution from mere deduplication and respect versus ignore the retention schedule during compaction, which ties straight into governance. The takeaway the trap is not whether compaction makes reads fast. Of course it does. The trap is whether the bill got paid or just moved. Measure the hot path versus background cost split or you have measured nothing. Three risks, and they share a root cause, which is the most important thing in this segment. The first is compaction debt and write stall, and it is rated high. Compaction can’t keep up with the write rate level zero bloats read slow down. This is the documented LSM production failure mode. Luo and Carey attribute write stalls precisely to the mismatch between fast in memory writes and slow background IO, and they study merge scheduler design to bound it. For an agent, the translation is brutal and exact. On a busy agent, the sleep trigger never fires. The consolidation bill accumulates as backlog and reads eventually collapse. The fix is a single compaction backlog SLO with a dual trigger idle or log size threshold or max staleness plus back pressure, and you report the hot path versus background cost split so deferral can’t hide cost. And note, this is the same fix as the sleep directions. Sleep never runs risk. Solving. It once the second is lossy merge, destroying a needed detail also high. You do duplicate or summarize at a low level and discard a detail a later query needed. And because the source may already be tombstoned, the loss is silent. The mitigation is provenance pointers from every compacted row back to its source traces and soft delete, then archive, then destroy instead of hard delete. And this is where deletion being genuinely hard actually helps you in a standard way. In the LSM tree, a delete is just a tombstone that only truly persists when compaction eventually rewrites past it with no bound on how long that takes. Subhadeep Sarkar and colleagues Leith, a tunable delete aware LSM engine adds persistence, latency and space guarantees on deletes for agent memory. That is the native mechanism for tombstone don’t hard delete a deletion becomes scheduled and bounded, which is exactly legal hold and grace window semantics. The third is rated critical. And it is shared with the sleep direction. Confabulated schemas becoming durable memory. High level schema extraction invents a fact that is in no trace. And once the raw is subsumed, that hallucination is the durable, unauditable memory. The mitigation is never hard delete on consolidation, provenance on every schema row and a confabulation rate metric. The share of schema claims not entailed by any source trace. And here is the crosscutting root cause the one rule to take away. All three failures, the right stall, the lossy merge, the confabulated schema stem from irreversible, unaudited memory transformation. So the single highest leverage rule is this. Every merge forget and superpose operation is reversible until archived and carries provenance plus the policy that triggered it. The LSM tombstone leads bounded delete and the archive tier give you that natively. What gets built next is the engine that enforces it with the policy chosen by a model line and the mechanism executed deterministically. The way Thakkar’s ELMOTUNE V2 already showed for real storage. The takeaway deferral is not a discount and transformation without provenance is not consolidation. It is data loss with extra steps. So that is LSM compaction as consolidation. Write cheap to a fast log, merge in the background, course an episodic into semantic as you descend the levels and tear the oldest out to a cold archive, all governed by a measured read write space cost model instead of a cron job and a guess. Storage systems, cognitive science and records management converged on the same shape, which is exactly when borrowing the mechanism is defensible. The one thing to watch the honesty clause. Anyone who claims compaction made memory cheap has to show the deferred background token bill, not just the fast reads. Deferral moves cost. It doesn’t erase it. And the one concrete action. If you are building agent consolidation today, instrument the amplification triad and the hot path versus background split before you tune a single thing. Measure where the bill is paid until next time.
- 4. Vector-Symbolic Holographic Superposition
Fold many memories into one fixed-size hypervector and probe it with a cue. A 1990s idea the agent-memory field is rediscovering the hard way: constant size, paid for in exactness.
Read transcript
The Agentic Memory Research Frontier, 4 of 5. Picture a pool of water. You drop in a hundred recorded songs, all at once, all on top of each other, until the surface is just one churning blur. No track listing. No folders. One pool. Now somebody hums you a few bars, and you reach into that single blur and pull back the song they were thinking of. Noisy, a little distorted, but recognizable. Then you snap it to the nearest clean recording you already know, and there it is. That is not a metaphor for some far-off brain. That is, almost literally, how a class of memory systems from the 1990s actually works. You fold many memories into one fixed-size vector, and you recover any one of them by probing that single vector with a cue. The storage never grows. It just gets fuzzier as you add more. And right now, the agentic memory field is rediscovering it, the hard way, one LLM at a time. This is Episode 9. Welcome back to the Research Frontier. We have spent this sub-series on cutting-edge directions for agent memory, one idea per episode. Today’s idea is the strangest and, arguably, the oldest. It is called vector-symbolic holographic superposition, and it sits right at the join of two worlds that usually do not talk, connectionist neural representation and symbolic structure. Here’s the shape of the episode. First, the core idea and the metaphor that makes it click. Then the actual mechanism, the two algebraic operations that make it work. Then how it differs, structurally, from the one-row-per-item vector stores everyone deploys today. Then the interdisciplinary lineage, because this is genuinely a neuro-symbolic idea with a hardware payoff attached. Then how you would evaluate it without fooling yourself. And finally, the open risks, including one that is the single-highest leverage-failure cluster in our whole program. Let us get into it. Start with the claim, because it is audacious. Instead of storing each and every one of them in one place, you can store them in one place. Instead of storing each memory as its own row in a database, you fold many memories into one fixed-size high-dimensional vector. The jargon for that vector is a hypervector, and the whole point is in the word fixed. The slot does not grow when you add memories. Its footprint is constant in the number of items you pour into it. The intellectual roots here are external to our scientific corpus, so let me name them in prose. The direct ancestor is Tony Plate, who in the 1990s introduced holographic reduced representations, HRR for short. Plate gave us the core trio, circular convolution as a way to bind two concepts together, superposition as a way to pile many of them into one vector, and a cleanup memory to recover them. Alongside Plate sits Pentti Kanerva, whose sparse distributed memory from 1988, and later his hyperdimensional computing work, made the case that high-dimensional random vectors are a robust, brain-plausible computing substrate.
And behind both of them is Paul Smolensky, whose tensor product representations from 1990 were the earlier, bigger binding scheme that HRR cleverly compresses. Now why does folding everything into one vector even work? Because of a fact about high dimensions that feels like a trick. If you pick random vectors in a space with, say, 10,000 dimensions, any two of them are almost certainly nearly perpendicular. Quasi-orthogonal, the field says. They barely interfere, so you can add a lot of them together, and still tell them apart afterward, the way you can overlay many faint, nearly independent signals and still fish one back out. Here’s the honest contrast, and it is the heart of the whole episode. A normal vector store is exact, but linear. Every memory is its own row, recall is precise, but the index grows forever. Holographic superposition is the opposite corner of the design space. Approximate, but constant. You give up exactness, you accept some crosstalk noise, and in exchange, you get a memory whose size is bounded by its dimensionality, not by its history. Nothing crashes when the pool fills up. It just gets blurrier. The takeaway for this segment, holographic memory is not a better database. It is a different trade. Constant size, paid for in exactness. Hold on to that sentence, because everything else is a consequence of it. Now the mechanism, because the magic is just two operations in a dictionary. Let me build it piece by piece. First, the dictionary, which the field calls a codebook, or item memory, or cleanup memory. Every primitive concept, every entity, every role, every relation, gets assigned one random hypervector. Curie gets a vector. The role subject gets a vector. The relation discovered gets a vector. Because of that quasi-orthogonality we just talked about, all these atoms start out barely overlapping. Operation one is binding, and plate’s classic choice for it, is circular convolution. Binding takes two hypervectors, and ties them into a third, that is dissimilar to both, but is invertible, and preserves distances. So you can compute subject bound to Curie, and that product is a brand new vector, that means, roughly, this filler plays this role. There are other binding schemes. Kanerva’s map family, multiply add permute, uses plain element-wise multiplication. Frequency domain HRR, multiplies complex phases. And there is newer work I will name. Mahmudul Alam and colleagues derived a Walsh-Hadamard based linear binding operator that lives in real space, is associative, commutative, and has a clean inverse, which matters a lot when you want differentiability and numerical stability. Operation two is bundling, and it is just addition. You superpose many bound pairs by adding them up, usually with a normalization step. Subject bound to Curie, plus relation bound to discovered, plus object bound to radium, and so on. The sum is similar to each of its parts. That is what lets one single vector genuinely contain many memories at once. So how do you read it back? Recall is unbind, then clean up. To ask who is the subject, you convolve the bundle with the inverse of the subject role. Out comes approximately Curie, plus a sum of crosstalk from every other binding in the pile. That noisy estimate is not clean enough to use directly, so you run a nearest-neighbor match against the codebook, and snap it to the closest real atom, and you read off a confidence from the signal-to-noise ratio. And here is a lovely connection. That clean-up step is literally a k-nearest-neighbor search against a dictionary. Which means holographic memory composes naturally with the kNN composite memory work of Angela Phan and colleagues. The codebook just is the clean-up memory. They are not rivals. One is the substrate, the other is the snap-to-clean step. The takeaway? There is no model call anywhere in that loop. Binding, bundling, unbinding, and a nearest-neighbor snap. It is deterministic algebra. That property is going to matter enormously in two segments’ time. Let me make the structural difference concrete, because this is where you decide whether to care. Against the dominant shape of agent memory today, the one row per item store, holographic superposition changes two costs at once. Today’s systems, the original rag of Patrick Lewis and colleagues, the kNN composite memory of Phan and colleagues, the production pipelines built on top, all share a shape. Storage grows linearly with the number of items. And recall is a retrieve-then-read step, a top-k approximate nearest-neighbor search over an index that keeps getting bigger. Better retrieval helps. Hybrid lexical plus semantic matching, the work of Sarkozy and colleagues, and late interaction indexing, like ColBERT from Omar Khattab and Matei Zaharia, both make that step sharper. But they do not change its shape. More memory still means a bigger index and more candidates to score. Holographic memory attacks the shape itself. A slot’s footprint is constant in the number of items bundled into it. Recall is an algebraic unbinding, not a search over rows. For an agent piling up thousands of small associative facts per entity or per session, that is the whole promise. A memory bounded by dimensionality, not by history. There is also a quieter difference against knowledge graph memory. In a graph store, a relation is an explicit edge. In a bundle, the relation is bound algebraically into the vector, and you can compose relations on the fly with vector operations, at the cost of edge-level exactness. But now the contrast that keeps this honest, and it is a genuine dissent. Do not assume a one-row store is the dumb, high-capacity, poor option. Modern, continuous Hopfield networks store an exponential number of patterns and retrieve in a single step. And famously, their update rule is mathematically equal to transformer attention. That is the result from Hubert Ramsauer and colleagues, the paper titled, Hopfield Networks is All You Need, and from the large associative memory work of Dmitri Krotov and John Hopfield. So a vector store plus attention is already an associative memory, and a near-exact, capacity-rich one at that. Which means holographic superposition is not unambiguously better. It occupies the opposite corner. Dense Hopfield bounds one edge. Exact, one shot, capacity-rich. Vector symbolic memory bounds the other. Constant size, capacity graceful, lossy. An agent memory architect is choosing a point between those two corners. The takeaway, and write this one down, the exactness gap is the quantity you must measure, not assert. If you cannot put a number on how much accuracy you traded away for constant size, you have not actually evaluated this idea. You have just admired it. This segment is about lineage, because where an idea comes from tells you what it is actually for. And this idea is squarely neuro-symbolic. It sits at the join of connectionist representation, vectors, gradients, distributed codes, and symbolic structure, roles, fillers, relations. The deep justification is something cognitive science calls the binding problem. How does a connectionist system represent role-filler structure? Who did what to whom without a combinatorial explosion? The modern statement of why that matters is the paper by Klaus Greff and colleagues on the binding problem in artificial neural networks. Their argument is the conceptual warrant for this whole approach. If you want a network to generalize compositionally, you need real role-filler binding. Not just opaque embeddings that smear everything together. Holographic memory is, in a sense, an answer to Greff’s challenge. It stores memories as bound structures you can take apart, rather than as flat vectors you can only compare. And the surveys that map this whole territory are worth naming, because they are your entry points. Denis Kleyko and colleagues wrote a two-part survey of vector symbolic architectures and hyperdimensional computing. Part one lays out the operation set and the model zoo. Part two covers applications, cognitive models, and the open challenges, including exactly the capacity and crosstalk problems we have been circling. If you read one thing after this episode, read part one. Now, the crosscut, the part that makes this more than a math curiosity. There is a hardware lineage here that a row-based vector database simply cannot access. Distributed holographic codes map naturally onto in-memory and neuromorphic hardware. Abbas Karunaratne and colleagues demonstrated hyperdimensional computing running inside memristor arrays in analog memory, robust to device noise, with real winds in energy and area. And Kleyko and colleagues, in a separate paper, frame vector symbolic architectures explicitly as a computing framework for emerging hardware. Why does that matter? Because it substantiates the claim instead of leaving it as a vibe. Neurosymbolic representation buys hardware efficiency. The same property that makes these codes robust to crosstalk, distributedness, also makes them robust to noisy analog devices and lets the binding and bundling run as cheap parallel operations on substrates where a conventional ANN index would be miserable. The takeaway. This is not just a clever data structure. It is a representation whose physics line up with where efficient hardware is going. If you only evaluate it on a CPU against a vector index, you are missing out. You are measuring it on the one substrate it was never optimized for. So how do you test this thing honestly? Our program scopes it as the exploratory substrate lane and it is gated on a pre-registered capacity result. That phrase, pre-registered, is doing a lot of work and I will come back to why. Start with the tasks. Three of them. First, a capacity stress recall task. Load k structured memories and measure recall as k grows. That is the canonical vector symbolic capacity curve and it is the whole point of the exercise. Second, a cleanup recall task on real agent facts, entity attributes, simple relations drawn both from our synthetic oracle generator and from a long horizon benchmark such as SEA EVAL, the self-evolving agents benchmark from Zhang and colleagues. Third, a hybrid routing task on quantities and dates with gist and associative records. Now the metrics and notice that every one of them is designed to make the cost falsifiable. Recall at one versus bundle load k at fixed dimension. That is the graceful degradation curve. Bytes per memory against a one row store at matched accuracy. Recall latency, vector operations versus an approximate nearest neighbor search. Then the one that matters most, the exactness gap, the accuracy delta of the setup queries. That is the cost the program has to quantify out loud. And a hardware cost axis, operations per byte and an energy proxy citing that in-memory hyperdimensional work so the efficiency claim is measured and not merely asserted. The baselines have to be fair and there is a subtlety here. You compare against an exact one row vector store but at two different budgets, matched bytes and matched items. The interesting regime is same bytes, but you are hunting for the crossover k, the point where holographic storage starts winning on bytes per memory while still clearing a recall threshold. That crossover is the constant size payoff point and if it does not exist within any plausible operating range the idea loses. The theory tells you roughly where to look. Bundling k items into a fixed dimension vector produces interference that grows with k and past a threshold the signal for any one item drops below the crosstalk floor just fails. The capacity theory for how much you can reliably bind comes from Frady and colleagues on variable binding for sparse distributed representations. And the catalog of how encoding choices move that capacity curve comes from the hypervector encoding survey of Eigen and colleagues. So ablate the codec frequency domain HRR versus MAP versus that Walsh Hadamard linear scheme. Ablate salience weighted versus uniform bundling. Does importance weighting actually protect the memories you care about under pressure? Ablate with and without the codebook cleanup and report the exactness gap per record class so the nish, gist yes, IDs no, is honestly bounded rather than oversold. The takeaway. Pre-register the capacity curve threshold before you run it. The failure mode this idea invites is exactly the one our measurement crisis episode warned about admiring a mechanism without ever pinning its cost. Decide the number that counts as success first, then go measure. Last segment, the risks drawn straight from the program pre-mortem. There are four, and the third one is the one that should keep you up at night. Risk one, rated high. The exactness gap is too large to be useful. Superposition crosstalk makes point recall unreliable but agents need exact facts, dates, identifiers, IDs. If that gap is wide, holographic memory is a curiosity. The mitigation is hybrid routing. Use the holographic substrate for associative and gist recall, and a plain exact store for the record classes that must be exact. The record class typing routes the choice, and the evaluation reports the gap explicitly so the niche is bounded, not sold past its limits. Risk two, rated medium. Engineering immaturity. HRR codecs, cleanup memories, capacity tuning. These are research grade, not turnkey. And differentiable HRR was historically plagued by numerical instability. The mitigation is to keep this in the exploratory lane and adopt the stabilized versions. The differentiable, numerically stable HRR of Ganesan and colleagues, the learning with holographic reduced representations work, and the Walsh-Hadamard linear codec from Alam and colleagues. Then gate further investment on that pre-registered capacity result. Now the third risk, and this is the highest leverage failure cluster in the entire program. Bundling is lossy, and it is not cleanly reversible. Once a binding has faded below the crosstalk floor, it cannot be recovered, and a superposed slot carries no per-item provenance by default. You poured everything into one pool, and the pool does not remember which drops came from where. That collides head-on with the program’s governing rule. Every forgetting, merging, or superposing operation must be reversible until archived, and must carry provenance plus the policy that triggered it. You keep the source traces under a retention schedule, soft delete, never hard delete, so a bundle can always be re-derived from its provenance. And you treat the hypervector as a cache of consolidated schemas, not as the system of record. That single move changes the whole proposal. Holographic superposition becomes a densification layer sitting on top of an auditable trace store, not a replacement for it. The pool is fast and small and lossy, the trace store underneath is slow and complete and forever. The fourth risk is quieter but real. Capacity miscalibration. Set the dimension or the bundle ceiling by guesswork, and you risk silent recall collapse the moment a slot quietly exceeds capacity, with nobody noticing. The mitigation is to monitor per-slot signal-to-noise ratio as a first-class telemetry signal, and trigger a spill or a re-slotting before you breach the crosstalk floor. The takeaway? Holographic memory is safe to build only as a layer, never as the bottom. Cache the schemas, keep the trace, watch the SNR. Build it that way and it densifies your memory. Build it as the source of record and it quietly eats your provenance. So to recap. Holographic superposition folds many memories into one fixed-size vector using two operations, binding and bundling, and reads them back by unbinding and snapping to a codebook. It trades exactness for constant size, it descends from Plate and Kanerva and Smolensky, and its distributed codes pay off on neuromorphic hardware. But it is lossy, it is not natively reversible, and it must be evaluated against a pre-registered capacity curve with the exactness gap reported out loud. One thing to watch. Whether anyone publishes that crossover K, the bundle load where constant size storage actually starts to win. That number turns a beautiful idea into a usable one. One concrete action. Start by reading Kleyko’s survey, part one, and design the capacity stress task before you write a line of codec.
- 5. Information-Foraging Optimal-Stopping Recall
Treat recall as a bird foraging across berry patches, reading until a patch is depleted. The retrieved result size should be an output of the walk, not a fixed top-k you set in advance.
Read transcript
The agentic memory research frontier, five of five. Picture a bird in a meadow full of berry bushes. It lands on the first bush, eats the easy berries near the outside, and then the picking gets slower. Every new berry takes longer to find than the last. At some point, the bird faces a question it answers without a single conscious thought. Keep stripping this bush or fly to the next one? Behavioral ecologists have a precise rule for what that bird should do, and it turns out to be the same rule your retrieval system should follow when it reads memory.
Most agent memory today does not follow it. It does the equivalent of telling the bird, eat exactly 10 berries from every bush, no matter how full or how empty. 10 berries on the lush bush, 10 on the bare one.
That is fixed top K retrieval, and it is blind to whether the patch is rich or depleted. This episode is about replacing that blindness with a forager that knows when to leave. Welcome to episode 10. This is the last stop on the Research Frontier sub-series, and it is the one that comes from the furthest outside the language model world. The previous Frontier episodes stayed mostly inside the corpus of agent memory papers. Today, we leave it almost entirely.
The lineage here runs through behavioral ecology, through information science, through classical information retrieval, and through optimal stopping theory. And only at the very end does it touch a language. The idea is to treat recall not as a database query you run once, but as foraging across a landscape of food patches. An agent reads memory until a patch is depleted, then decides, dig deeper, move on, or go home. The decision is made from cheap, non-language model signals, never a model call per step. Over the next six segments, we will cover the core metaphor, the mechanism, how it differs from both fixed K retrieval and the expensive model-judged loops, the four-discipline lineage behind it, how you would actually evaluate it without fooling yourself, and the open risks.
Let us forage. Start with the claim, because it reframes the whole problem. The claim is that an agent’s memory is not a table you select from once. It is a landscape of patches, and retrieval is an animal moving through that landscape, eating until a patch stops paying off, and then deciding what to do next. A patch can be a semantic cluster, a storage team, a frontier, a slot in a structured store, an archive level, anything that already partitions memory. Inside a patch, the items come back ranked, and the forager reads down that ranked stream one hit at a time. The metaphor is not loose. It is borrowed wholesale from information foraging theory, which Peter Pirolli and Stuart Card laid out in Psychological Review in 1999, and which Pirolli expanded in his 2007 book. Pirolli and Card took a model of how animals hunt for food, and applied it to how humans hunt for information, on the web, in documents, across a search interface. They gave us the vocabulary of information sent, of patch leaving, of diminishing returns inside a patch. That is the direct intellectual parent of treating recall as foraging. And underneath their work sits an even older result we will come back to, Eric Charnov’s marginal value theorem from 1976, the actual rule the berry-eating bird is following. Now the contrast, because the metaphor only matters if it changes behavior. The dominant alternative is fixed top K retrieval. The original retrieval augmented generation recipe from Patrick Lewis and colleagues in 2020, and the realm work from Kelvin Gu and colleagues the same year. Both retrieve a constant number of items regardless of the query. A trivial single fact lookup and a hard multi-hop synthesis get the same K. That is blind in both directions at once. On the easy query, fixed K over-retrieves and wastes context on berries you did not need. On the hard query, it under-retrieves and stops before the one crucial item buried three patches over. The forager metaphor says K should never be a constant. It should be whatever the landscape pays for on this particular query. The concrete takeaway, stop thinking of recall as a single query with a fixed result size, and start thinking of it as a walkthrough patches that ends when the walking stops, being worth it. The size of the result is an output of that walk, not an input you set in advance. The metaphor is only useful if you can compute the leaving decision cheaply. This segment is the mechanism, and the heart of it is one estimate. After you read item I, what is the marginal expected gain of reading item I plus one, and is that gain still above the cost of continuing? The rule for when to leave comes straight from Charnov’s marginal value theorem.
Charnov, writing in Theoretical Population Biology in 1976, proved that an optimal forager should leave a patch at the exact moment its instantaneous intake rate drops to the long-run average rate of the whole habitat. Leave when this bush is paying out no better than an average bush would, once you account for the travel time to reach the next one. The controller here applies that literally. It maintains a running marginal value estimate, and when that estimate falls below the switching cost, the modeled token and latency cost of opening another patch, it leaves. If some other patch’s expected opening gain beats the switching cost, it switches. Otherwise, it stops. What makes this practical is that the marginal value estimate is built from three families of cheap, non-language model signals. The first is similarity score decay. In a well-ordered patch, the relevant scores of successive hits only go down, and the slope of that decline is a direct proxy for diminishing returns. That is the foraging curve made literal, the gain rate falling toward the environment average. The second is novelty against the working set, how much genuinely new information each hit adds versus what you already hold. This uses classical diversity machinery, determinantal point processes from Alex Kulesza and Ben Taskar, the near-duplicate-aware summarization work of Sangwoo Cho and colleagues, the submodular coverage of Jacob Schreiber’s apricot library, and cheap set similarity dedupe, like the DotHash method of Igor Nunes and colleagues. A patch returning near-duplicates is depleted even when its raw similarity is still high. The third family is information gain proxies, mutual information scores of the kind Mario Baraha and colleagues use for feature selection, and the surprise and curiosity menu surveyed by Arboret and colleagues and pioneered by Deepak Pathak and colleagues, which estimate how much an item reduces uncertainty about the answer, regardless of surface similarity. The contrast worth drawing, none of these three signals is a model call. They are arithmetic over scores, sets, and distributions. The whole controller is a scalar comparison run after each hit. The takeaway, the leaving decision is a closed-form arithmetic question, not a judgment call. You combine three cheap signals into one number and compare it to a cost. That is the entire control loop. Here is the structural argument, the reason this is a genuine third option and not a tweak on what exists. Retrieval control today sits at two unsatisfying polls, and this controller refuses both. The first poll we already named fixed top K, adaptive at nothing but dead cheap. The second poll is the language model-judged iterative loop, the self-rag and adaptive-rag family, where after each retrieval step you ask a model, do I have enough context to do this? No, not yet. Those loops adapt beautifully. They genuinely tune retrieval depth to query difficulty, but they pay a full model call per step to do it, and that cost compounds across the loop. Worse, the stopping policy is implicitly re-specified every time you upgrade the underlying model, because the judgment lives inside the model, not in the system. So you can have adaptive, or you can have cheap, but the two polls make you choose. The optimal stopping literature says you do not have to choose, and the in-corpus evidence is unusually strong. Chris Goel, Christoph Dan, and Emma Brunskill, in their work on sample-efficient policy search for optimal stopping domains, frame deciding when to stop an observation-generating process exactly as the secretary problem family, and they prove sample complexity bounds with logarithmic dependence on the horizon. Logarithmic, not linear, not exponential. That is the strongest anchor that a stopping controller can be learned cheaply and with provable guarantees, and notably their lineage runs straight back through the Pirolli foraging tradition. And the adaptivity is not hypothetical in retrieval either. Ping Nei and colleagues built an any-hop iterative document re-ranker that, in their words, adaptively determines when to stop the retrieval process, dropping the fixed single-hop versus multi-hop assumption, and matching or beating the state-of-the-art on natural questions, SQuAD-Open, and HotpotQA.
But here is the dissent, and it is honest. Nei’s stopping rule is a learned graph re-ranker score. It is adaptive, it is cheap, but it is opaque. You cannot say why it stopped. The midpoint case is Vendi RAG from Mohammad Reza Rezaei and Adji Bousso Dieng, which adaptively trades retrieval diversity against quality, beats adaptive rag on multi-hop questions, and crucially shows the gains grow as the document count rises, strong evidence that a cheap diversity signal is the right marginal gain proxy. But Vendi RAG still calls a model judge each iteration to set its diversity weight. The takeaway. This controller keeps the diversity signal that Vendi RAG proved valuable and removes the per-iteration model judge, and it replaces Nei’s opaque learned stop with a transparent rule. You stop because similarity decay times redundancy drop below switch cost, and you can say exactly that. The reason this idea feels solid is that it is not one bet.
It is the confluence of four separate research traditions, three of them entirely outside the language model corpus, that happen to point at the same mechanism. Let me walk the lineage, because the credibility comes from the convergence. First, behavioral ecology, which gives the stopping rule itself. Charnov’s marginal value theorem is the literal source of leave when intake drops to the habitat average. The patch model around it comes from David Stephens and John Krebs and their 1986 book on foraging theory. This is the oldest layer and the most rigorous. Decades of field-tested mathematics about when an animal should abandon a depleting resource. Second, information science and human-computer interaction, which give the metaphor for search. This is the Pirolli and Card information foraging line we opened with, the move that took Charnov’s animal and turned it into a person hunting through information. Information sent, patch leaving on the web, diminishing within-patch returns, these are their contributions, and they are why we can talk about a database query as a foraging walk at all. Third, classical information retrieval and summarization, which give the redundancy signal. The canonical ancestor is Jaime Carbonell and Jade Goldstein’s maximal marginal relevance, from SIGIR in 1998, the original relevance minus redundancy objective. That idea, that the value of the next item is its relevance discounted by how much it duplicates what you already have, is exactly the patch depletion signal, and it is the direct conceptual ancestor of the diversity machinery. The determinantal point processes and the submodular selection methods that the modern controller uses. Fourth, optimal stopping and sequential decision theory, which give the formal guarantees. The secretary problem, surveyed in Thomas Ferguson’s 1989 paper, made learnable with bounds by Goel, Dan, and Brunskill. Sven Schmidt, Virag Shah, and Ramesh Johari add what they call the paradox of power, that high-powered exhaustive search is actually inefficient when candidate patches are abundant, a clean theoretical argument for leaving early. And Daniel Jarrett and Mihaela van der Schaar’s inverse active sensing models timely decisions as costly sequential evidence gathering with an explicit decision to commit, which is exactly a stop. The dissent here is just a caution. Convergence is suggestive, not proof. Four traditions agreeing on a mechanism does not mean the mechanism transfers cleanly to language model memory, where the patches are messier than berry bushes. The takeaway is that the burden this lineage carries is to make the metaphor operational and measured, which is the next segment, not to rest on its pedigree. A cheap adaptive controller is easy to claim and hard to prove, so the evaluation design matters more than usual. The trap is specific, and it has a name in the program pre-mortem. The evaluation cannot isolate the structural win. Start with the task design. You need variable difficulty retrieval, where the optimal number of items to read genuinely varies per query, a deliberate mix of single-fact and multi-hop questions over a long horizon corpus. And, this is the critical part, results reported per difficulty structure. The answer is stratum, never pooled. Pooling lets an easy query win hide a hard query loss. Use the multi-hop benchmarks the closest prior art already uses, HotpotQA, MuCQ, and 2WikiMultiHopQA from the Vendi RAG work, and natural questions, SQuAD-Open, and HotpotQA from Nee and colleagues. Then add a synthetic generator that controls the per-query optimal k directly, so you can measure overforaging and underforaging against an actual ground truth. The headline metric is the answer quality versus retrieval cost Pareto frontier. Does the controller dominate both fixed k and the model stop loop on the cost quality curve? Jarrett’s accuracy speed acquisition cost framing gives you the explicit Pareto axes. Underneath that, three more. The distribution of items read per query, which measures adaptivity directly, since a good controller’s distribution should track query difficulty. The stop decision cost itself, which must be far less than the single model call, and should be reported as controller latency against one model call, drawing on Schmidt’s opportunity cost ledger, and the over and underforaging rate against the synthetic oracle k, the fraction of queries that stopped too early and missed the crucial item, or stopped too late and wasted reads. Baselines are fixed k at several values, the model judged loop, Nee’s learn stop re-ranker, and an oracle k upper bound. And ablate each signal alone, similarity decay only, diversity only, info gain only, to show what each one actually contributes. The descent is the methodology warning, and it is sharp. There are three ways this evaluation can lie to you. Synthetic over fit, where the controller learns the generator rather than the task. A recency confound, where long horizon benchmarks let recency alone explain recall, so you are not measuring foraging at all. And model judge bias if you use a model to score. The mitigations are concrete. Build the shared harness first, pair every synthetic result with a real benchmark replication, de-correlate recency from importance inside the generator, and use an independent local judge plus human spot checks. The takeaway, the believable result is a Pareto plot, reported per difficulty stratum, where the controller dominates both poles and its stop decision cost is provably a tiny fraction of a model call. Anything pooled or anything that cannot be pooled or cannot rule out recency does not count. Two risks dominate, and they are the honest reasons this is research and not a ship default. Both come straight from the project premortem. The first and highest is that cheap signals miss semantic salience. The controller stops early on a query whose answer hinges on a low similarity but crucial item that no surface signal flagged. The berry that does not look like a berry. This is the existential risk for any non-model salience scheme. And the mitigation is not to pretend it cannot happen. It is to calibrate the controller against Oracle K on a held-out set, and then to permit a bounded model fallback only when the controller’s own confidence is low. The common path stays fully non-model and cheap. The model is a capped insurance policy on the worst case, not a per-step cost. That preserves the cost win without betting everything on cheap signals. The second risk is that patch structure is ill-defined. If patches do not map cleanly onto the store, the switch rule becomes arbitrary. You are leaving and entering partitions that do not mean anything. The mitigation is a discipline. Define patches off structure that already exists, storage tiers, semantic clusters, structured slots, archive levels, and never invent a partition just to forage over it. The controller forages over the map that is already there. There is also a subtle program-level risk worth naming, because it is special. Because it is specific to this thread. Cost does not shrink, it just moves. If the signal computation itself, the determinantal point process eigendecompositions, the mutual information estimation, is expensive, then the cheap claim quietly collapses. The whole pitch was avoiding a model call, and you cannot replace it with an equally costly linear algebra call. The mitigation is to hold stop-decision cost far below one model call as a hard evaluation gate, and to prefer the cheapest adequate signal, DotHash over a full determinantal point process wherever the cheap dedupe suffices. What gets built next follows directly. A shared signal bank is the structural payoff. The very same cheap signals that decide when to stop reading also drive the right gate. Admit, if surprising or novel, the prioritized replay intuition from Tom Schaul and colleagues, and the curiosity signal from Pathak and colleagues, and they drive compaction priority during consolidation. One signal vocabulary, three control points. And the cross-patch ordering question, which patch to visit next under uncertainty, has its own theory ready to plug in. Marko Mitrovic and colleagues’ adaptive sequence submodularity gives an adaptive greedy policy with approximation guarantees for exactly that sequential selection under uncertainty problem. The takeaway. Build the controller as mechanism, not model judgment. Keep a capped model fallback for the low-confidence tail. And reuse the same signal bank for writing and compaction, so the cost of computing salience is amortized across the whole memory lifecycle. So that is forging recall, and that is the Research Frontier subseries. The one idea to carry out. Retrieval depth should be an output of the query, not a constant you set in advance. And you can decide when to stop using cheap signals that an animal in a meadow has been using for millions of years. No model call required. Charnov gave us the rule. Pirolli and Card gave us the metaphor. Carbonell and Goldstein gave us the redundancy signal. And the optimal stopping theorists gave us the guarantees. The one thing to watch. Whether anyone reports the Pareto plot honestly, per difficulty stratum, with stop decision cost proven to be a fraction of a model call. The one concrete action. Next time you see a memory system, ask what its k is, and whether it ever changes. If the answer is a constant, it is feeding every bush exactly 10 berries. Until next time.
Agentic Memory Deep Dives
- The State of Agentic Memory
A mid-2026 state-of-the-field synthesis of agentic memory: the systems that ship (Zep, Mem0, Letta, MemOS, Cloudflare), the measurement crisis breaking the leaderboards, and the frontier of forgetting, security, and isolation.
Read transcript
Here is a number to start with. A team builds a memory benchmark called BEAM, stretches each test conversation out to ten million tokens, and asks the obvious question: now that the biggest models can hold a million tokens or more in context, do we even need a memory system? Can’t we just stuff the whole history into the window and let attention do the work? The answer the benchmark gives is brutal and clarifying. No memory architecture saturates it. The best systems land around sixty-four percent at the one-million-token track and drop into the high forties at ten million. And context stuffing doesn’t even compete, because at ten million tokens a frontier window holds maybe one percent of the history. So the field arrives at mid-2026 with its founding bet vindicated by force. Memory is not a temporary patch we tolerate until context windows grow. It is a permanent layer of the stack, and we are still bad at it.
That is the through-line for the next forty-five minutes. This is a state-of-the-field episode, a capstone to the reading path, so I’m going to assume you know the vocabulary and instead synthesize where the field actually is. And the summary is a split-screen. On one side, real systems ship, real numbers climb, real companies sell agent memory as a product. On the other side, we cannot reliably tell which of those systems is best, because the way we measure them is so fragile that changing one scoring decision flips the winner. So we’ll walk three movements. First, what exists: the memory stack and the systems that ship it. Second, how we measure them, and why that measurement is in crisis. Third, what’s still unsolved, the frontier the field hasn’t cracked. Building, evaluating, breaking. Let’s go.
Start with the stack, because every system we’ll name is an opinionated answer to the same architectural question. The vocabulary comes from CoALA, the 2023 cognitive-architectures paper from Sumers and colleagues at Princeton, now sitting north of one hundred fifty citations and functioning as the field’s periodic table. It gives you four memory types. Working memory is the live context window, the desk where the agent thinks right now. Episodic memory is the record of specific past experiences, what happened and in what order. Semantic memory is general knowledge and facts, decoupled from any single episode. And procedural memory is the skills and routines the agent knows how to execute, including, in a nice twist, its own prompts and code. When a vendor tells you their product has episodic and semantic memory, they are speaking CoALA whether they cite it or not. Hold those four words, because the entire systems landscape is a set of choices about which of them to make first-class, what data structure to store each in, and when to move information between them.
And there’s a second axis, from the 2026 survey by Jinghao Luo and colleagues, titled From Storage to Experience, which is itself the thesis. Memory systems climb a ladder. Stage one is storage: you keep the raw trace, the logs, the transcript. Stage two is reflection: the agent processes the trace, summarizes it, writes itself a note like “this user prefers terse answers.” Stage three, the frontier, is experience: the agent abstracts across many trajectories into reusable knowledge that changes how it acts in genuinely new situations. Storage, reflection, experience. The useful thing about that ladder is it’s a diagnostic. Most of what ships today lives on rungs one and two. When a vendor says their agent “learns from experience,” the sharp question is which rung they’re actually on. Are they abstracting across trajectories, or keeping good logs and calling it learning?
Now the systems. Let’s anchor on the three that the reading path treats as canonical, because they stake out the design space. Zep, from Preston Rasmussen and colleagues, builds memory as a temporal knowledge graph through an engine called Graphiti. Conversation and structured business data get fused into typed entities connected by time-stamped edges, and crucially, when a fact changes, the old edge isn’t deleted, it’s marked invalid as of a date. That temporal awareness is the whole point. Zep reported beating MemGPT on the deep-memory-retrieval benchmark, ninety-four point eight versus ninety-three point four, and improving LongMemEval accuracy by up to eighteen and a half percent while cutting latency by ninety percent. The number that matters there isn’t the accuracy, it’s the latency, because it tells you the graph is doing work the context window would otherwise do slowly. A-MEM, from Wujiang Xu and colleagues, takes the opposite philosophy: instead of a rigid graph, a self-organizing web of notes, Zettelkasten-style, where new memories link to and rewrite old ones as they arrive. It’s beautiful and it’s loose. And Mem0, from Prateek Chhikara and colleagues, is the production-pragmatist of the three: extract facts, consolidate them, keep the store small. Mem0 reported on LoCoMo a twenty-six percent relative improvement over OpenAI’s built-in memory, ninety-one percent lower p95 latency, and over ninety percent token savings versus dumping the full context. Same word, memory, three incompatible data models. That’s the field in miniature.
Now step outside the reading path, because the most important development since these papers is that agent memory became an infrastructure product, and the production systems make the build-versus-buy decision concrete. Letta, the company that grew out of the MemGPT paper, ships the clearest mental model: the load-bearing primitive is the memory block, a labeled, persistent string the agent edits with its own tool calls, like core_memory_append and core_memory_replace. There’s a “human” block for what the agent knows about you, a “persona” block for its self-description, and custom blocks for task state. The agent literally rewrites its own memory in the loop. And in 2026 Letta added what they call sleep-time compute, which is the single cleanest instantiation of the reflection stage I’ve seen ship. The insight is that in the original MemGPT design, memory management and conversation were bundled into one agent, so the agent was slow during chat because it had to stop and do bookkeeping, and the memories got messy because they were written incrementally under time pressure. Sleep-time compute offloads memory management to a separate sub-agent that runs asynchronously, often triggered when the context window gets compacted. It reads the raw trace and rewrites it into clean, concise, organized memory while the user isn’t waiting. That is reflection as a system primitive: storage on the hot path, reflection on a background clock. Remember that pattern, because it recurs everywhere now.
LangChain’s answer is LangMem, an SDK that bolts long-term memory onto LangGraph agents and is notable because it maps directly onto the CoALA triad in product form. Semantic memory: facts about you, stored either as an unbounded searchable collection or as a structured profile, a user card the agent keeps current. Episodic memory: records of specific past interactions. Procedural memory: internalized know-how, which LangMem is explicit lives across a combination of model weights, agent code, and the agent’s own prompt. And it offers the same two integration modes as Letta’s design: hot-path tools the agent calls mid-conversation, or a background memory manager that extracts and consolidates asynchronously, merging related facts and resolving contradictions on its own clock. Hot path versus background is becoming the standard fork in the road, and it’s the storage-versus-reflection split wearing an engineering hat.
Then there’s the operating-system camp, which has its most ambitious 2026 entry in MemOS. The pitch is right there in the name: treat memory as a first-class operating-system resource, the way an OS schedules RAM and disk. Its core abstraction is the MemCube, which wraps three kinds of memory under one scheduler: plaintext memory, activation memory meaning KV-cache states, and parameter memory meaning weights. The radical claim is that these are interconvertible, that a frequently-used plaintext memory could be promoted into activations or even distilled into parameters, and a cold parameter memory demoted back to plaintext, with the system migrating content between forms based on usage, importance, and recency, exactly like an OS swapping pages. Whether that promise holds up is open, but it’s the purest expression of the MemGPT lineage, the camp that thinks about memory in operating-system terms, paging and caching and eviction.
And then there’s the part of the landscape that almost never shows up in the academic papers but is where most real users will actually meet agent memory: the platform vendors. Cloudflare shipped agent memory built on Durable Objects with SQLite-backed storage now generally available, ten gigabytes per object, where each agent is a stateful object with its own embedded SQL database that persists across evictions. That’s memory as boring, durable infrastructure, no knowledge graph, no consolidation, just a place to put state that survives. And Twilio shipped Conversation Memory aimed at customer-facing agents, which is worth dwelling on because it solves a problem the academic benchmarks barely model: identity resolution across channels. Twilio’s system builds one canonical customer profile and recognizes the same person across phone, email, and WhatsApp, automatically resolved into a single memory. Then its Recall API retrieves with a combination of semantic and lexical search and returns a ranked set of observations, summaries, and recent communications.
That last detail opens the most important technique in production retrieval, and it deserves a proper beat, because it’s where the reading path’s information-retrieval thread reconnects to memory. The technique is Reciprocal Rank Fusion. The problem it solves is that no single retrieval channel is enough. Embedding similarity is great for paraphrase and fuzzy semantic match but blind to exact strings. Keyword search nails the exact term and misses the synonym. A knowledge-graph traversal finds multi-hop connections neither of the others can see. So mature memory systems run all of them and then have to merge several ranked lists into one. RRF does this with a formula almost insultingly simple: each candidate’s fused score is the sum, across channels, of one over a small constant k plus its rank in that channel, with k usually set to sixty. A memory that ranks high in multiple channels accumulates evidence and rises to the top; a memory that’s only strong in one stays modest. No score calibration, no tuning embeddings against keywords, just rank arithmetic. And the production refinement worth knowing is weighted RRF, where the query type sets channel weights: a temporal query boosts the time-aware channel, a multi-hop query boosts the entity-graph channel. So the system routes its trust by what’s being asked. If you build one thing from this episode, multi-channel retrieval fused with weighted RRF is the highest-leverage, lowest-glamour move you can make.
Let’s pull the building movement together before we leave it, because the spectrum tells you where the open design space is. The architectures are fanning out along an axis of structure: flat text, then typed semi-structured entries like Memanto, then pairwise knowledge graphs like Zep, then hypergraphs like HyperMem that capture multi-participant events a pairwise graph would fragment, then hierarchical trees like MemTree and LinkedIn’s production hiring-agent memory. A 2026 paper, T-Mem, argues that nearly all of these, the graphs and trees and OS kernels alike, share one recipe: similarity-based retrieval over descriptive memory, and that they all leave associative recall, the “this reminds me of that” channel, as a structural blind spot. And on the writing side, a clear consensus has formed: a storage path that’s fast and lossless and never blocks the user, and a reflection path that runs in the background to consolidate, deduplicate, and resolve conflicts. Letta’s sleep-time agents, LangMem’s background manager, MemOS’s scheduler, the bi-temporal Engram engine that keeps a sub-fifty-millisecond write path while a separate consolidation path builds the graph. Storage on the hot path, reflection on a clock. That is the load-bearing pattern of 2026 memory systems.
It’s worth being precise about what the experience rung actually requires, because it’s where the research is hottest and the marketing is loosest. Reflection, rung two, is within reach: the agent looks back at one trajectory and writes a better note. Experience, rung three, means abstracting across many trajectories into something reusable, and the field has discovered that the naive version, just retrieving a similar past episode, doesn’t get you there, because a retrieved raw episode forces the base model to re-adapt it on the fly, every time. So the 2026 work moves toward generated rather than retrieved experience. CLEAR, from Linbo Liu and colleagues and open-sourced by AWS, runs a reflection agent that does contrastive analysis over past trajectories to produce per-task summaries, then trains a context-augmentation model that generates task-tailored experience instead of looking it up, lifting AppWorld from the low seventies into the eighties. HiExp extracts hierarchical experience through multi-level clustering and uses it to regularize an agent’s otherwise random exploration. And the frontier systems couple memory to capability directly: SEARL jointly optimizes the agent’s policy and a tool-graph memory under verifiable-reward training, and Mem2Evolve co-evolves distilled experience with newly created tools and expert sub-agents, so the accumulated experience doesn’t just inform the agent, it expands what the agent can do. That’s the real meaning of the experience rung, memory that changes capability, not just memory that changes recall, and almost nothing in production is there yet.
There’s a design decision hiding inside that reflection path worth surfacing, because it’s the deepest architectural fork in the field and most builders make it without noticing. When the background agent consolidates experience, where does the consolidated memory go? Two answers. The non-parametric answer: it goes into text or a graph, an external store the model reads back through its context window at query time. Everything we’ve named so far, Zep, Mem0, A-MEM, Letta, lives here. Memory is data the model retrieves. The parametric answer is stranger and more ambitious: the consolidated experience goes into the weights, fine-tuned in, so the model just knows it without retrieving anything. A 2026 paper from Simon Dennis and colleagues runs the rare head-to-head, per-user weight-based consolidation against cascading context compaction, the two ways to retain experience under inference-only deployment. And TSUBASA, from Xinliang Frederick Zhang and colleagues, splits the difference with context distillation, internalizing user experience through a self-learning loop rather than re-reading the raw history every turn, benchmarked against Mem0 across the Qwen-3 model family with a quality-versus-token-budget framing. MemOS’s claim that plaintext, activations, and weights are interconvertible is the maximalist version of this idea: that the parametric and non-parametric stores aren’t different architectures, they’re different temperatures of the same memory, and the system should move content between them. Whether that holds is unproven. But the axis, memory-as-context versus memory-as-weights, is the one that will define the next generation of systems, and right now almost nobody benchmarks both under a matched compute budget.
And one more piece of the stack, because it’s the rung-three frontier in production form: procedural skill libraries. The lineage starts with Voyager, the 2023 embodied agent from Guanzhi Wang and colleagues that gave us the canonical move, an ever-growing library of executable code skills, written and verified and stored as compositional behaviors, with an automatic curriculum, that transferred to a fresh Minecraft world. Voyager turned procedural memory into a code library you grow. Agent Workflow Memory, from Zora Zhiruo Wang and colleagues, generalized that off the game board: induce reusable routines from agent trajectories, offline from training examples or online from the test queries themselves, and inject them as procedural memory, with explicit cross-task and cross-website generalization tests on WebArena and Mind2Web. And the 2026 work pushes into the hard maintenance problem: Skill1 trains a single reinforcement-learning policy to co-evolve the three coupled operations of a skill library, selecting, using, and distilling skills toward one task objective, and finds that distillation is the control knob for library quality and growth. Because the dirty secret of skill libraries is that they rot. Skills accumulate, overlap, drift, and clutter, and the library gets worse, not better, as it grows. SkillEvolBench, which we’ll come back to in the measurement movement, was built precisely to test whether the distilled skills actually beat just reusing the raw trajectories. Spoiler that should worry every builder: often they don’t.
Two things are worth knowing about how procedural memory actually ships, because they’re where the design choices bite. First, there are two competing representations, and they fail differently. One camp stores executable code skills, Voyager, SkillClaw, Skill1, SkillDroid, where a skill is a function you can compile and run; these fail with compilation errors and composition errors, two skills that don’t fit together. The other camp stores natural-language workflows or manuals, Agent Workflow Memory and AutoManual, where a skill is a written-down routine; these fail with ambiguous-instruction drift, where the model interprets its own note differently than it meant. A benchmark that covers procedural memory has to test both, because they break in incompatible ways. Second, efficiency has become a co-equal metric to accuracy here, and it’s the clearest place where memory pays for itself. SkillDroid, a 2026 mobile-GUI agent, compiles a successful task execution into a reusable skill so later invocations skip the per-step LLM inference entirely; the win isn’t a higher success rate, it’s that the same task runs without paying for the model again. When a skill is reused, the question stops being “did it work” and becomes “did it work and what did it cost.” That cost axis is where the procedural-memory literature is ahead of the conversational-memory literature, which still mostly reports accuracy and hides the token bill.
Which brings us to the second movement, and the genuine crisis of the field. We have all these systems. We have all these numbers. Mem0 reports ninety-two and a half on LoCoMo and ninety-four point four on LongMemEval at about sixty-nine hundred tokens a query. Zep reports its deltas. New systems post leaderboard wins weekly. And the uncomfortable truth, the thing the careful 2026 methodology papers are screaming about, is that those numbers do not mean what they appear to mean, and a striking number of them do not survive contact with a neutral re-run. So let’s take the measurement crisis seriously, because it’s the most intellectually alive part of the field right now.
Start with the benchmarks themselves, because the foundation is shakier than the leaderboards suggest. LoCoMo, from Adyasha Maharana and colleagues, is the de-facto reference: very long synthetic dialogues across up to thirty-five sessions, with a four-category question taxonomy, single-hop, multi-hop, temporal, open-domain. Almost every memory system reports on it. And LoCoMo has exactly ten conversations and one thousand eight hundred thirteen questions. Systems are now reporting above ninety-four percent on a benchmark of ten conversations, which raises two alarms at once: statistical power, because ten conversations is a tiny sample to rank systems on, and contamination, because a benchmark this small and this public leaks into training data and saturates. A 2026 paper, Synthius-Mem, reports ninety-four point four percent memory accuracy and ninety-nine point six percent adversarial robustness on LoCoMo, and the right reaction to a number that high isn’t celebration, it’s suspicion that the benchmark has stopped measuring capability and started measuring memorization. LongMemEval, from Di Wu and colleagues, is healthier: five named abilities, including knowledge-update and abstention as first-class tasks, with controllable histories so you can scale the memory load independently of the evidence. But it too is being saturated.
So the field is doing what a maturing field does: building harder benchmarks and, more importantly, questioning the measurement itself. BEAM, which opened this episode, pushes to ten million tokens precisely so nothing saturates. LongMemEval-V2, released May 2026, reframes the entire target: memory systems shouldn’t just recall chat facts, they should help an agent become an experienced operator of a specialized environment, like an experienced colleague. It draws four hundred fifty-one curated questions and over eighteen hundred task trajectories from WebArena-style and ServiceNow-style environments, with haystacks up to a hundred fifteen million tokens, and five abilities that are nothing like factual recall: static state recall of page layouts, dynamic state tracking, workflow knowledge for recurring tasks, recognizing environment gotchas, and premise awareness, knowing which assumptions valid elsewhere are wrong here. That’s a benchmark trying to measure procedural and episodic memory in a working context, not chat trivia.
But harder benchmarks don’t fix the deeper problem, which is that the scoring itself is unstable. This is the part that should genuinely unsettle you. There’s a 2026 audit called TIAP, whose title is the whole finding: Same Ranking, Different Winner. It isn’t a new benchmark. It takes already-saved retrieval traces and re-scores them under different but equally defensible definitions of what counts as a correct retrieval. The setup: when one conversation turn gets processed into several derived memories, a raw stored version, a canonical rewritten version, and so on, which of them is allowed to receive credit when a query needs that fact? Call that the scoring target. TIAP defines three reasonable targets, raw, source, and canonical, re-scores the exact same retrieval traces under each without re-running anything, and watches what happens. The rankings flip. The system that wins under one scoring target loses under another. Same data, same retrieval, same traces, different winner, purely because of a credit-assignment choice nobody was reporting. The methodological takeaway is severe: if a memory paper doesn’t explicitly state its scoring target, its leaderboard position is not interpretable. And almost none of them state it.
It gets worse, or more interesting, depending on your temperament. There’s a paper bluntly titled Harness Updating Is Not Harness Benefit, from Minhua Lin and colleagues, that names a confound at the heart of every self-evolving agent claim. These systems edit their own harness, their prompts, skills, memories, tools, and then report improved task outcomes. The paper’s point is that the act of updating is routinely conflated with benefiting from the update. The harness changed, the score moved, and everyone assumed the change caused the gain, when it might be activity masquerading as capability. To make a credible claim you need controls: a no-update baseline, a raw-trajectory baseline, the works. And SkillEvolBench, from Yingtie Lei and colleagues, the one hundred eighty-task procedural-memory benchmark with an explicit acquisition-then-frozen-deployment split, ran exactly those controls and found the result I flagged earlier, that reusing raw trajectories directly often beats the distilled skills you so carefully induced. Think about what that means for the entire skill-distillation enterprise. You built a clever pipeline to abstract reusable skills from experience, and a control condition that just keeps the raw logs around outperforms it. If you didn’t run that control, you’d have shipped the distillation and credited it with a gain it didn’t earn.
There’s a third confound underneath the scoring-target and harness-update problems, and it’s the one that quietly poisons the most leaderboards: how the answers get graded in the first place. Almost every memory benchmark scores free-text answers with an LLM judge, because checking whether “she lives in Boston now” matches “the user moved to Boston” can’t be done with string matching. But LLM judges carry biases, position bias, verbosity bias, self-preference, documented across the LLM-as-judge surveys from Jiawei Gu and Haitao Li and colleagues, and a 2024 study from Hui Huang and colleagues shows that fine-tuned judge models, the cheap option, fail to transfer across tasks and are not a drop-in substitute for a strong general judge. None of those surveys validate judges specifically for memory QA, which is the hardest case, because memory judging means adjudicating temporal grounding, multi-session attribution, and contradiction handling, exactly the question types where a judge is most likely to be wrong. So a memory leaderboard built on an unvalidated judge is reporting the judge’s opinion as much as the system’s capability. The Engram engine paper, a 2026 bi-temporal memory system, documents the consequence directly: it shows how truncation, home-grown judges, and full-history leaks let a single system report fifty-eight, sixty-six, and ninety-two percent across different sources, the same system, three numbers, depending on who graded and what leaked. Its response, which is becoming the reproducibility gold standard, is to ship one in-repo pipeline, use the official category judge, put the full-context baseline in every table, and publish raw logs with a reproduce command attached to every number.
And then there’s the most sobering measurement result of the year, which is a null. A 2026 paper called GitOfThoughts ran a pre-registered, controlled comparison: hold the agent fixed, swap only the memory substrate across five backends, none, markdown, vector, graph, and git, on GPQA-Diamond and MATH-500, with paired-bootstrap confidence intervals at two model scales. The headline is a robust null. No substrate reliably improved accuracy on novel problems. A promising fifteen-point bump for the git substrate at a sample of forty did not survive its own pre-registered replication, and the authors documented the retraction alongside the result. Read that against the weekly leaderboard wins. When you run the controls the leaderboards skip, hold the agent and compute fixed, report intervals, pre-register the replication, a lot of the memory advantage evaporates. That doesn’t mean memory is useless; BEAM and the long-horizon benchmarks show it clearly matters at scale. It means that on short novel-reasoning tasks, the gains people attribute to clever memory architectures are often noise, confound, or the base model doing the work. The discipline to find that out is the discipline the field is still building.
The constructive response to all of this is white-box, stage-attributed diagnostics, and this is where the methodology movement is most exciting. The old way scores the final answer: right or wrong. The problem is that a memory pipeline has stages, write, store, retrieve, generate, and a final wrong answer tells you nothing about which stage failed. Did the system never store the fact? Store it but fail to retrieve it? Retrieve it but the generator ignored it? Two 2026 papers, both called MemTrace by different teams, attack this. One traces failures back to the specific pipeline stage responsible, converting an opaque wrong answer into a per-stage diagnosis. The other reorganizes the entire unit of measurement: instead of scoring question rows, it scores knowledge points, single typed facts about the user, probing each fact repeatedly across three controlled axes, how old the memory is, what kind of question is asked, and whether the evidence is present, missing, or contradicted. Eight hundred thirty-five knowledge points expand into over two hundred thousand scored answers, and then the killer move: a diagnostic that separates “the evidence was unreachable” from “the evidence was retrievable but went unused.” That distinction is the whole ballgame. Unreachable means fix your retrieval. Unused means fix your generation or your context assembly. A single accuracy number can’t tell them apart; a stage-attributed harness can.
This same retrieval-versus-use split shows up in the conflict literature, which is where memory measurement gets genuinely subtle. MemConflict, a 2026 framework, treats memory validity not as a fixed property but as fitness-for-use conditioned on the query, and defines three conflict types that any real deployment hits. Dynamic conflict: an earlier state and a later true update coexist, and the later one should supersede, you moved cities, the new city wins. Static conflict: a later false contradiction should not overwrite a stable fact, someone misremembers your birthday, the original stands. Conditional conflict: multiple values are each valid under different conditions, and only the one matching the query applies, you like window seats on long flights and aisle on short ones. The framework evaluates six real memory systems, A-Mem, LangMem, Letta, MemOS, Mem0, and Memobase, through one common pipeline, with both black-box scoring of the final answer and white-box scoring of whether the right memory was even retrieved and how it ranked. And the diagnostic gap it surfaces, between “the supporting memory was retrieved” and “the supporting memory was actually used,” localizes failures the way nothing answer-level can.
And then there’s forgetting, which the measurement movement reveals as the field’s true blind spot, and which sets up our third movement. STALE, from Hanxiang Chao and colleagues, asks the question directly: can LLM agents know when their memories are no longer valid? Four hundred expert-validated conflict scenarios, twelve hundred queries, contexts up to a hundred fifty thousand tokens, probing belief revision over time. The best model scores fifty-five point two percent. Just above a coin flip on knowing whether what it remembers is still true. Put the LoCoMo number and the STALE number side by side: ninety-four percent on recalling what was said, fifty-five percent on knowing whether it’s still valid. That gap is the field’s self-portrait. We got very good at remembering and we are still bad at updating, and almost nobody was measuring the second thing until 2026.
Step back and look at the meta-signal here, because it’s the real state of the field. In a single quarter, the research community produced an audit showing scoring choices flip rankings, a paper showing self-evolution claims conflate activity with benefit, a benchmark showing raw trajectories beat distilled skills, two independent white-box failure-attribution harnesses, and a benchmark showing the best models are at chance on memory validity. Read together, that is a field reaching the maturity where it stops trusting its own leaderboards and starts auditing its instruments. The bottleneck in agentic memory right now is not building memory systems. It’s that we cannot trust the comparisons between them. A neutral, re-runnable harness, with explicit scoring targets, fixed-answerer controls so you isolate the memory from the model, confidence intervals instead of point estimates, cross-system evaluation, and stage-attributed diagnostics, is itself the most valuable contribution someone could ship. The systems are ahead of the science of measuring them, and that gap is the headline.
Which brings us to the third movement: what’s actually unsolved. The frontier. And I want to drive this off the real gaps, because the open problems are more specific and more tractable than the usual hand-waving about AGI.
The first frontier is forgetting and obsolescence, and it’s the thinnest-measured area in the entire field. Here’s the conceptual trap the whole field fell into: every metric we built rewards accumulation. Recall at k, did you keep the fact and find it. None of them reward correct deletion, removing a memory that’s stale, superseded, or wrong. So systems are optimized to be hoarders. The 2026 work is finally pushing back. There’s a neuroscience-inspired camp, SCM with sleep-style consolidation and explicit algorithmic forgetting, ZenBrain with a seven-layer architecture, Adaptive Memory Crystallization which actually puts numbers on it, reporting sixty-seven to eighty percent reductions in catastrophic forgetting and a sixty-two percent smaller memory footprint on robotics benchmarks. There’s an eviction-with-recall camp, cooperative memory paging that bookmarks evicted content by keyword so it can be paged back, Learning to Forget for robots that cuts memory forty-five percent while holding QA accuracy. And there’s the constrained-optimization camp, a paper called OSL-MR that charges an explicit cost for keeping stale memories and for discarding still-useful ones, and finds the learned policy keeps a smaller, evidence-denser store: on LoCoMo at a budget of one hundred twenty-eight memories, F1 of zero point three at seventy-six percent occupancy, versus a greedy baseline that fills to ninety-nine percent occupancy and scores zero point zero seven. The lesson is counterintuitive and important: deliberately keeping less, but keeping the right less, beats greedily keeping everything. What’s still missing is a shared metric, and the absence is specific enough to name. We have no standard retention curve, the analog of a forgetting rate over time. We have no agreed-on precision and recall for obsolescence decisions, no way to ask whether a pruning policy deleted the right stale items rather than just shrinking the store, because shrinking the store and curating the store look identical to a recall metric. And we have a strange evidence gap at the heart of the most popular mechanism: nearly every neuroscience-inspired system describes a consolidation step, sleep-style replay, synaptic tagging, the hippocampal-cortical metaphor, and almost none of them ship the ablation that would justify it, the run that turns consolidation off and shows long-horizon retention drops. STALE measures obsolescence detection with its own three-dimensional accuracy, Adaptive Memory Crystallization imports forward-transfer and forgetting-percent from continual reinforcement learning, but these don’t compose into a common protocol. Two forgetting papers cannot be ranked against each other today. Until a shared retention-and-obsolescence suite exists, this whole area can be admired but not compared, which is exactly the state the recall benchmarks were in three years ago before LoCoMo, and exactly the gap that made LoCoMo matter.
The second frontier is security and governance, and it’s where the persistence that makes memory useful becomes the attack surface that makes it dangerous. A stateless model has no memory to poison; the moment you give an agent a durable store, you’ve given an attacker a place to plant something that persists. The canonical attack is AgentPoison, from Zhaorun Chen and colleagues: optimize a trigger so that any query containing it retrieves a malicious memory, no fine-tuning required, just poison the store. The 2026 work shows how much nastier this gets in real systems. There’s a Trojan attack that poisons a shared agent’s memory purely through normal conversation, with a trigger that survives the memory-extraction pipeline, no privileged access needed, just talk to it. There’s ShadowMerge, the first poisoning attack tailored to graph-structured memory, where one unprivileged user’s message gets materialized as a graph relation, survives entity-resolution merging, and is later retrieved as graph-native evidence for a different user. Cross-user contamination through the merge path: one user poisons another’s answers. And there’s the finding that should worry you more than any deliberate attack, a paper on unintended long-term state poisoning, showing that memory gets corrupted without any attacker at all, just through routine interaction that gradually drifts the stored state toward harm. The defenses are forming, lineage and provenance tagging on every memory entry as in MemLineage, audit graphs of agent execution as in Agent-BOM, write-back auditing. But the gap is glaring: there’s no standardized security harness with shared metrics across attack families, poisoning success rate, induced over-refusal, cross-user leakage, provenance violations, all measured in bespoke per-paper setups. And nearly every attack targets semantic retrieval memory; poisoning of stored procedures and skills, where a corrupted skill executes instead of merely misinforming, is almost untouched.
The third frontier is synthetic-data realism, which sounds like a tooling problem and is actually a validity problem for the whole field. Almost every memory benchmark, LoCoMo and LongMemEval included, is synthesized by an LLM playing personas. So the question that undermines everything is: do these synthetic conversations look like real ones? The 2026 answer is a clear no, and it’s well-documented. OmniBehavior, built entirely from real-world behavior traces, shows that LLM user simulators converge to what the authors call a “positive average person,” with persona homogenization, hyper-activity, and a Utopian bias, losing exactly the individual quirks and long-tail behaviors that make memory hard. REALTALK contributes twenty-one days of genuine human-human messaging as a real-data anchor and exposes the same distribution gap. So you can saturate a synthetic benchmark while still failing on real users, because your synthetic users aren’t real users, they’re an averaged ghost. The constructive direction exists, controllable conflict and distractor injection from the MemConflict recipe, the quality-diversity-complexity auditing framework that measures the data itself instead of just downstream scores. But there’s no agreed fidelity metric that scores whether a synthetic memory dataset is realistic, and the benchmarks remain tiny and persona-thin, EngramaBench runs five personas, a hundred conversations, a hundred fifty queries. The scaling question, how to generate thousands of genuinely diverse personas without collapsing to the average person, is wide open.
The fourth frontier is multimodal and long-horizon recall, where the benchmarks are racing to catch up to the products. Most memory research is text-only, but agents increasingly see screens, images, and continuous sensor streams. MemLens and MemEye both, in 2026, started benchmarking whether vision-language models preserve the visual evidence needed for later recall. PersonaVLM pushes personalization into the multimodal regime, a model that remembers an individual’s visual preferences over time. And the most striking move is toward streaming, always-on input: StreamMemBench sources its tasks from real egocentric lifelog video, mining each five-minute segment for a hidden evidence anchor, a preference or plan or capability, then testing whether the agent carries it forward to a later related task without being re-prompted. That’s memory for a wearable that watches your day, and it breaks the clean-session assumption every dialogue benchmark relies on. The text-only era of memory evaluation is ending, and the multimodal era barely has a yardstick.
The fifth frontier is the cluster of production axes the literature covers least and deployments need most, and it starts with multi-user isolation. Every memory benchmark assumes one user, one memory. Real systems serve millions, and the failure mode is catastrophic and specific: one user’s memory leaking into another user’s response. ShadowMerge already showed it can happen through a graph merge. The Multi-User LLM Agents work names the problem, an agent that must maintain and isolate per-user state, but there’s essentially no benchmark that adversarially probes whether user A’s memory contaminates user B’s answers, which is a strange gap given that it’s the single risk most likely to make a real deployment a headline.
It pairs with proactivity. Every benchmark we’ve discussed is reactive: the user asks, the agent recalls. But a memory that’s only consulted on request is leaving most of its value unused. The PASK work couples long-term memory with intent inference to drive proactive behavior, the agent surfacing remembered information unprompted, and it exposes an evaluation problem nobody has solved: how do you score whether an agent should have spoken up, including the cost of false proactivity when it volunteers something unwanted at the wrong moment. Recall-style benchmarks have no way to measure that, because they only ever ask questions. And the domain deployments make the same point from the other side. LinkedIn’s hiring agent runs a production hierarchical semantic memory organized into abstraction tiers; a longitudinal health-agent framework argues memory and personalization alone are insufficient and proposes evaluation across coherence, continuity, adaptation, and agency over a patient’s trajectory. Generic recall QA captures none of that. Each high-stakes domain wants its own longitudinal criteria, and there’s no harness that lets one memory system be scored under each domain’s standard.
Underneath all of it sits cost, the dimension that turns every accuracy number into half a story. Every figure I’ve quoted has a token budget behind it, Mem0’s roughly sixty-nine hundred tokens per query, Zep’s ninety-percent latency cut, and the field has barely started treating efficiency as a first-class metric alongside accuracy. A memory system that’s two points more accurate and ten times more expensive is not obviously better, and almost no leaderboard reports the tradeoff. The procedural-memory people figured this out first, scoring reuse by inference saved as well as tasks solved; the conversational-memory people are still catching up. Memory exists to spend less compute than re-reading everything, so a memory benchmark that ignores compute is measuring the wrong thing.
Let me pull the whole arc together, because the three movements tell one story. We built the stack: working, episodic, semantic, procedural memory, with a storage-reflection-experience ladder that most systems are still climbing. We shipped the systems: Zep’s temporal graph, A-MEM’s self-organizing notes, Mem0’s lean production store, Letta’s self-editing memory blocks with sleep-time reflection, LangMem’s CoALA-shaped SDK, MemOS’s operating-system ambition, and the platform vendors, Cloudflare and Twilio, who quietly put memory in front of the most users, with multi-channel retrieval fused by weighted RRF as the highest-leverage production technique. And on top of it all, procedural skill libraries climbing toward the experience rung, from Voyager to Agent Workflow Memory to Skill1. That’s a real, shipping field.
Then we measured it and the floor moved. LoCoMo saturating at ten conversations. TIAP flipping the winner by changing the scoring target. Harness Updating Is Not Harness Benefit catching activity dressed as capability. SkillEvolBench finding raw trajectories beating distilled skills. The two MemTrace harnesses pulling failures apart into write-versus-retrieve-versus-use. STALE putting the best models at fifty-five percent on knowing whether a memory is still valid. The systems are ahead of the science of comparing them, and a neutral, stage-attributed, scoring-target-explicit, confidence-interval-reporting harness is the most valuable thing the field could build right now. And then the frontier: forgetting we can’t measure, security we can’t standardize, synthetic data that isn’t real, multimodal recall that’s barely benchmarked, multi-user isolation that production needs and research ignores.
Notice the meta-pattern under all three movements, because it’s the deepest thing here, and it traces straight back to the foundations of this whole series. The field keeps reaching for the human brain. Sleep-consolidation, hippocampal metaphors, the seven-layer architectures, the active-forgetting pathways borrowed from neuroscience. And the reason is the one we landed on at the very beginning: human memory is the only existence proof we have of a system that remembers across a lifetime, forgets gracefully without catastrophic loss, generalizes from a handful of examples, and stays coherent for decades, on a power budget smaller than a light bulb. Every architecture in this episode is a wager about which features of that system are worth copying and which are accidents of wet biology. The danger, the one the careful papers flag, is that a beautiful neuroscience metaphor can paper over the absence of a measured result. Sleep-consolidation sounds biologically plausible; the question that earns it its keep is whether there’s an ablation showing the consolidation step actually improves long-horizon retention against a no-consolidation control. Mostly, there isn’t yet.
So let me leave you where the field actually is, on the live open question, the one that subsumes the others. We have systems that store and reflect well, and we cannot yet build one that knows what to forget. Forgetting is not the absence of memory; it’s the hardest act of memory. It requires knowing that a fact is stale, that a skill is obsolete, that a preference has changed, that a memory was never true, and then having the judgment to let it go without losing what still matters. The best models are at a coin flip on the simplest version of that judgment. Every other frontier, security, multi-user isolation, long-horizon coherence, multimodal recall, runs through it, because a memory you can’t correct is a memory you can’t trust, and a memory that only grows is a memory that eventually drowns. The bet that opened this episode, that memory is a permanent layer of the stack, is settled. The next bet, the one the whole field is now placing, is that the agents worth having won’t be the ones that remember the most. They’ll be the ones that know what to keep. We’re not there. That’s the work. Thanks for listening.
Open problems
Where the literature is thin and the next contribution could land.
-
Unified multi-type white-box harness
Nothing spans semantic+episodic+procedural with stage-attributed diagnostics, explicit scoring targets (TIAP), fixed-answerer controls (EngramaBench), cross-system eval (GRAVITY) and CIs. Flagship open-source contribution.
-
Canonical procedural-memory benchmark
SkillEvolBench/SEA-Eval are days-old & unconsolidated; adopt the freeze-then-deploy arc + No-Skill / Raw-Trajectory attribution controls ('Harness Updating ≠ Benefit').
-
Forgetting / obsolescence metric suite
Thinnest area: STALE (55.2% ceiling) + AMC continual-RL metrics are the only hard numbers; standardize a retention-curve + obsolescence-precision/recall protocol for textual memory.
-
Synthetic-data realism metric
OmniBehavior/REALTALK prove the gap; build a fidelity score + controllable conflict/distractor injection (MemConflict recipe) + QDC auditing.
-
Shared memory-security harness
RSR@k / ASR / Benign + over-refusal + cross-user leakage + provenance-violation, covering episodic/procedural stores (today's attacks only hit semantic).
-
Unbenchmarked production axes
Multi-user isolation, proactive memory use, multimodal long-horizon recall.