Agentic Memory System

The field moved fast in 2026. Every major harness now ships some memory primitive, and the open question is no longer whether agents need memory but which shape survives contact with a 40-session workload. Our own bake-off found retrieval latency and recall precision diverge sharply above ~50k tokens of history, which is exactly where enterprise support and claims agents live. Vendors are converging on a three-store design (working, episodic, semantic) but the consolidation step — turning episodes into reusable knowledge — is still hand-rolled everywhere we looked.

Three live client patterns (banking servicing, insurance claims triage, retail merchandising) hit the same wall: the agent forgets what it decided last week and re-derives it, expensively and sometimes differently. A defensible default for the memory layer is worth more to delivery this quarter than any model choice. It also gates two near fields — Learning Agents and Personal Wiki — which assume a memory substrate exists.

Long-running agents need a memory layer that separates what happened from what was learned; raw vector recall over transcripts is the wrong abstraction and will be replaced by structured episodic stores with summarised recall. That is the lab's one-line position on it, which is not the same as an explanation.

The shape the field is converging on, from the most authoritative source in it: Retrieval latency exceeds generation latency for naive vector memory once history passes ~50k tokens.signal

This is the section a page most needs a person for, and the one composition is worst at. Nobody has written the plain-language version — what the idea is, in words that assume nothing — and it is the first thing a reader who has never met the term needs.

The lab opened this field on 2026-02-10 and it reached mainstream awareness on 2026-06-15. The gap between those two dates is the lead time the lab is measured on.

A term arrived: Two agent platforms ship 'memory' primitives in the same week That is the earliest reliable signal of a field being born — the vocabulary settles before the capability does.signal

What shipped: Two agent platforms ship 'memory' primitives in the same week (Vendor changelogs, 2026-08-06). Tooling arriving is what moves a field from argument to something a team could try.signal

Demand is rising on it rather than steady — “Why does the agent make a different call on the same case two weeks apart?” — which is the difference between a field worth watching and one worth doing something about.demand

What changes, concretely: Structured episodic store with summarised recall beat raw vector recall on a 40-session support corpus: +19 points recall precision, 0.6× latency at 50k+ tokens of history (x-memory-bench).signal

Measured rather than argued: Validated. Episodic+summary beat vector recall by 19 points precision at 50k+ tokens and ran at 0.6× its p50 latency. Graph memory won only on entity-lookup. Consolidation cut repeat-decision variance from 31% to 8%. Published as r-memory-layer; g-vector-memory-v1 superseded.experiment

There is already a shipped default — memory.store = episodic-summarised · skill: cavendish/memory-layer — so a team adopting this is changing a setting rather than starting a project.

The binding constraint is reliability: it works and is not yet dependable enough to put near a customer. Everything upstream of that is solved and everything downstream of it is waiting.

Workforce readiness is medium: Consolidation policy still needs a research engineer. Agent-estimated. A recommendation needing skills the firm does not hold is an aspiration rather than an action, and it routes to the enablement agenda instead of the delivery one.

Something here has already been killed: Vector-store memory as the agent's long-term memory, on the memory bake-off answered the question with a different design: structured episodic store with summarised recall beat raw vector recall on precision and latency above 50k tokens of history.graveyard

The argued case against it is the red team's, further down this page, and it is deliberately one-sided — this section is what stands in the way mechanically, not what somebody thinks of it.