# What is dreaming in Claude? Agent memory explained

> Dreaming is an offline pass where Claude reads past transcripts, fixes wrong notes and builds a wiki. What Anthropic measured, and how to try it.

- Published: 2026-11-07
- Publisher: Rig Labs (https://riglabs.ai/)
- Canonical: https://riglabs.ai/blog/claude-dreaming-agent-memory/
- Answers: what is dreaming claude

---

Dreaming is an offline process where an agent reviews its own logs or transcripts to fix mistakes and write new notes and memory representations. Anthropic described how Claude uses it in an engineering post on November 6, 2026.

## What does dreaming do for an AI agent?

Dreaming lets an agent improve its memory between sessions, instead of learning only while it works. [Anthropic's post](https://www.anthropic.com/research/components-of-agent-memory) says Claude can use it to correct mistakes, create notes, build representations such as wikis, and shape what gets loaded into future sessions.

This answers a plain problem. A note written early can be wrong, and a later session will trust it. Dreaming checks notes against the original transcripts.

## How much does dreaming improve an agent?

Anthropic's results for dreaming are from its own evaluations, on a few specific tasks:

| Test | Result Anthropic reports |
|---|---|
| Wiki built from about 350,000 files, 25 questions, wiki only | 13% to 48% of graded criteria, as dreaming scaled from 2 sessions to 128 |
| Same wiki with search | 61%, against 53% for search alone |
| Merger questions needing several documents, with the wiki | 87%, against 73% for search alone |

The same post gives limits. Dreaming costs compute, so checking every memory all the time may not be practical. The wiki showed no clear gain on one task where a text search of a single document could find most answers. On another task the wiki grew larger than the documents themselves.

## How can you try dreaming today?

Anthropic's [cookbook entry](https://platform.claude.com/cookbook/managed-agents-cma-dreaming-with-a-dynamic-workflow) builds a small working dream on Claude Managed Agents, and it needs Managed Agents beta access. It reads finished sessions, or a bundled example set, and writes a wiki-style memory store with small linked files and an index. Future sessions mount the store read-only, and the cookbook shows how to run it every night from cron.

| Run | Cost at list price | Time |
|---|---|---|
| Example set, 11 files, 283 KB | $0.36 | about 2.5 minutes |
| About 50 long transcripts, about 12 MB | about $8 | about 10 minutes |

Those are the author's runs. Dreams itself is a separate Managed Agents research preview, which takes session IDs directly.

## What are the risks of dreaming?

The main risk of dreaming is a bad note reaching your agent with nobody checking it. The cookbook says there is no review by default, so a bad transcript can reach your agent the next morning. Each run saves a copy of the store's files first, so you can go back. It also notes that Managed Agents sessions are not eligible for zero data retention or HIPAA, and that a session stores what its agents read until it is deleted.

## Does Claude Code use dreaming?

Anthropic's post does not say Claude Code uses dreaming. It describes Claude Code's auto memory, which loads the first 200 lines or 25 KB of `MEMORY.md`, as a separate example. The advice in the post carries over to any agent with logs: keep the always-loaded layer small, use it as an index to deeper notes, and pair a wiki with search.

Last checked 2026-11-07.

Sources:
- [The components of agent memory, Anthropic](https://www.anthropic.com/research/components-of-agent-memory)
- [Dreaming with a dynamic workflow, Claude Cookbook](https://platform.claude.com/cookbook/managed-agents-cma-dreaming-with-a-dynamic-workflow)
