Skip to content

Topic

Agent Memory Systems

Persistent memory layers that let AI agents retain lessons, fixes and environment facts across sessions, forming a category alongside Mem0, Letta and LangMem.

Current stories

productOne report1 publisher

Anthropic's dreams job merges duplicate agent memories into a second store

Anthropic's dreams job reads an agent's memory store and 1 to 100 past sessions, then writes a reorganized copy. The original is never modified, so a team can review the copy and discard it.

Reality

Evidence40
Adoption
Not scored
Hype gap−5
Incentives
Not scored
Confidence70
buildOne report1 publisher

Agent memory handoffs cut replaced context 98.65% by moving verbatim text out of the prompt

Memory handoffs cut replaced agent context by 98.65% across 10,241 completed runs, according to an audit published on dev.to. For agent builders, the open risk now sits in whether the agent recalls the right stored text, since lossy summaries are no longer the failure point.

Publishers:dev.to

Reality

Evidence55
Adoption15
Hype gap+10
Incentives
Not scored
Confidence45
buildOne report1 publisher

Throughline's recall receipts separate an empty archive from a search that never ran

Throughline's on-call agent returns a three-way coverage verdict with every memory recall, so a timed-out search cannot pass as "no prior incidents". Its author hit the same error-as-empty trap in CockroachDB's managed MCP server, where failures come back as HTTP 200.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap−10
Incentives30
Confidence40
buildOne report1 publisher

An Obsidian vault pipeline re-validates JSON from a model stripped of write tools

Every 10 minutes an unattended job summarizes Claude Code and Codex logs into an Obsidian vault and pushes the commit, so the pipeline treats the summarizer's own JSON as text that may carry pasted keys or injected instructions.

Publishers:dev.to

Reality

Evidence58
Adoption6
Hype gap+10
Incentives20
Confidence55
buildOne report1 publisher

Enforcing agent memory isolation at the storage prefix costs one dataset per user

A runnable two-agent example moves every refusal into the catalog that vends credentials, because a key covers a storage prefix and there are no rows at the point of enforcement. The author works on that catalog.

Publishers:dev.to

Reality

Evidence44
Adoption
Not scored
Hype gap+12
Incentives82
Confidence55
buildOne report1 publisher

Keying agent memory by session produced six copies of one test user's risk tolerance

A dev.to writeup by nasiko_labs describes a semantic memory tier whose first version inserted a row per session, so one agent could read "cautious" and "aggressive" at once. The rewrite keys each belief by fact type and archives the superseded version.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+12
Incentives55
Confidence45
buildOne report1 publisher

Tagging tool calls with source at write time turns the reverse audit into one traversal

A Strands hook recorder writes each agent step into Neo4j through Neo4j Labs' agent-memory SDK. The audit query that finds every decision touching a bad source depends on a dict lookup keyed by tool name.

Publishers:dev.to

Reality

Evidence50
Adoption
Not scored
Hype gap+20
Incentives65
Confidence55
buildOne report1 publisher

Claude Code's per-repository memory store lost a rule set for all projects

Both terminal agents recalled planted facts inside a single project across three two-session tests on identical Node repos. Only Grok Build carried a stated convention into an unrelated repo, at about a third of the reported cost.

Publishers:thenewstack.io

Reality

Evidence58
Adoption25
Hype gap+14
Incentives40
Confidence62
buildOne report1 publisher

Instinct's reported memory relies on keyword matching, not semantic search, with a once-a-day write job

Dhravya Shah spent three days probing the personal agent from the outside and reports git-tracked Markdown searched by keyword, with a background pass he clocked taking 23 hours and 16 minutes to commit one preference.

Publishers:runtimewire.com

Reality

Evidence42
Adoption24
Hype gap+28
Incentives76
Confidence58
buildOne report1 publisher

A smaller model rewrites the middle of a Claude Code session at about 160K tokens

A dev.to walkthrough of Claude Code compaction says the system prompt and the last 10 to 15 turns survive while the messages between them are summarized and deleted without an error. Constraints you need later belong in a file.

Publishers:dev.to

Reality

Evidence20
Adoption
Not scored
Hype gap+35
Incentives45
Confidence60
buildOne report1 publisher

A memory agent that keeps the option to stay silent lifts Terminal-Bench 2.0 pass@1 by 8.3 points

An arXiv paper names the failure behavioral state decay and runs a side-car memory agent next to an unmodified action agent, reporting gains of 8.3 and 6.8 points of pass@1 on two long-horizon benchmarks.

Publishers:arxiv.org

Reality

Evidence52
Adoption
Not scored
Hype gap+18
Incentives60
Confidence57
buildOne report1 publisher

A cache-config guess hardens into an institutional claim after three memory passes

In a dev.to account of self-reinforcing memory loops, an agent's own hedged inference is captured as a flat fact, retrieved a week later as context, and generalised until the store recommends replacing the cache layer.

Publishers:dev.to

Reality

Evidence33
Adoption
Not scored
Hype gap+20
Incentives40
Confidence50
buildOne report1 publisher

Four substitutions turn a Hopfield update into scaled dot-product attention

Ramsauer and colleagues proved the equality in 2020, three years after attention was published. It holds for a single retrieval step inside a forward pass, and the capacity figures quoted alongside it come from a different model.

Publishers:dev.to

Reality

Evidence74
Adoption
Not scored
Hype gap−8
Incentives62
Confidence66
buildOne report1 publisher

Only one of six agent-memory systems documents an edge that changes on read

Mem0, Zep, Cognee, Letta, Supermemory and Mnemoverse all ship a knowledge graph, and each one's docs mean something different by a node. Read-time behaviour is the part a buyer can settle from the documentation.

Publishers:dev.to

Reality

Evidence64
Adoption
Not scored
Hype gap−8
Incentives78
Confidence52
buildOne report1 publisher

This OpenCode plugin keeps a coding agent's memory in Markdown you can open and fix

The opencode-agent-memory plugin gives an OpenCode agent scoped Markdown blocks it rewrites through three tools, plus an opt-in journal it can search locally but never revise. The maintainer documents the failure modes himself.

Publishers:dev.to

Reality

Evidence34
Adoption14
Hype gap−12
Incentives38
Confidence52
productOne report1 publisher

Turing Post turns the agent postmortem into a question of where the fix gets stored

Turing Post talked through agent feedback with Salesforce's chief AI scientist at Dreamforce. A correction lands in one of four places: the context, persistent memory, the software around the model, or the weights.

Publishers:turingpost.com

Reality

Evidence46
Adoption20
Hype gap+12
Incentives62
Confidence48
buildOne report1 publisher

Persistent memory and MCP tools make 27B enough for a local assistant on 24 GB

Serge Kernbach's dev.to build notes put a 9B to 27B assistant on two RTX 4070s totalling 24 GB and argue that integration beats raw model quality. The figures he publishes are power draw and PCIe bandwidth.

Publishers:dev.to

Reality

Evidence32
Adoption12
Hype gap+30
Incentives22
Confidence42
buildOne report1 publisher

A docs audit splits agent memory into four capabilities the five coding tools answer differently

Vendor pages for Claude Code, Cursor, Codex, VS Code and Windsurf, re-checked on 2026-09-12, show that all five resume a previous session. The complaint about agents forgetting points at the other three questions.

Publishers:dev.to

Reality

Evidence80
Adoption
Not scored
Hype gap+10
Incentives45
Confidence68
buildOne report1 publisher

A coding agent followed the pointer to its rules file in 4 of 81 sessions

A developer instrumented 89 coding sessions to test whether rules the agent had already read changed what it did. Enforcement only started working once the rule was rewritten into something a hook could see.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap−10
Incentives30
Confidence55

Earlier coverage