[Late catch] Anthropic on agent memory: letting Claude reread its work logs and fix its notes with "dreaming"
What is it?
Anthropic wrote up its experiments on giving Claude memory that carries across sessions. Two pieces matter most. First, Claude writes important details to a memory folder as it works. Second, during idle time it rereads past transcripts to correct and merge those notes, a step Anthropic calls dreaming. The experiments ran on Claude Managed Agents with a memory folder that persisted between sessions.
Why does it matter?
The most common problem teams hit when they add memory to an agent is a wrong note that sticks around and causes the same mistake again. According to the post, dreaming let Claude check notes against the original logs and fix bad ones, and on a set of questions about a company's documents, scaling dreaming from 2 sessions to 128 raised the score from 13% to 48%Vendor claim. Another useful point for design: telling Claude what memory is for worked better than spelling out how to use it.
Maturity
ResearchThis is an engineering post about internal experiments, not a product launch. There's no separate API or setting called dreaming.
How to track it
- Productization: watch the Claude Managed Agents docs and the Claude Platform release notes for background memory cleanup like dreaming shipping as a feature.
- Benchmark release: follow the Anthropic engineering blog to see if CL-Bench 1.0, used in the post, becomes public so other models can be compared.