Anthropic Just Dropped the Feature Nobody Knew They Needed
Summary
Covers the undisclosed Auto Dream feature in Claude Code — a memory consolidation system that runs in the background, reviews session transcripts, and pruning stale or contradictory memories. Analogous to REM sleep in humans. Triggered after 24 hours + 5 sessions since last consolidation. Three phases: Orientation, Gathering Signal, Consolidation + Pruning.
Notes
- Auto Dream is distinct from Auto Memory — Auto Memory adds notes; Auto Dream consolidates and prunes them
- Runs in background, doesn’t interrupt active Claude Code use; uses a lock file to prevent simultaneous runs
- Read-only access to project files; write access only to memory files
- MEMORY.md should be an index pointing to sub-files, not contain memories directly
- The dreaming metaphor: agents modelled on human behaviour — sub-agent teams like organisations, dreaming like sleep for memory consolidation
- Activate with
/memory→ confirm Auto-dream: on
Wiki
Transcript
Intro
0:00 ·
The Feature
0:54 · So you would have noticed this if you went to your .claude folder, went to projects, and in all your projects there would be a memory folder with memories about that particular project. And these memories would automatically be inserted into the context window whenever you’re working.
1:08 · But then this introduced a brand new problem, whereby in Session 1 you would have a pretty fresh, clean, and relevant memory. And then as you go on, you would notice that Claude Code decides to add more and more stuff to its memory, and you get noise and contradictions and stuff like that. And then by Session 20, you notice your memory is just full of noise, has a bunch of contradictions, and it is kind of making the model perform worse. And Claude did have some instructions in the system prompt telling it to verify that the memory is still correct and up-to-date. But that didn’t really do a good job.
1:39 · But then the Claude Code team added a brand new feature that they haven’t yet announced, called Auto Dream. So if you do /memory in your project, then you’ll notice it says Auto-dream: on over here, and you can turn this off and on. And then you can also open your project’s memory folder from here as well. And I think that by naming the feature, they were kind of inspired by humans. Because if you’re a human watching the video, not an AI agent, then throughout your day, your brain is taking in a lot of new information: conversations, decisions, things that you read.
2:07 · And all of this goes into a short-term memory. And if everything just stayed there in the short-term memory, you’d quickly become overwhelmed. But when you sleep, at least during REM sleep, your brain can replay the day’s events and consolidate them and strengthens what matters, and then also deletes what doesn’t matter and organizes everything into long-term memory. And that is the reason why people who don’t sleep enough literally can’t form long-term memories. Their short-term memory fills up, and then they start confusing things and making contradictory decisions.
2:36 · And until now, even though Claude Code had an auto-memory feature, it was kind of sleep-deprived, where it kept adding random things to memory that may have not been relevant. But now with this Auto Dream mode, essentially what Claude Code is doing is it gathers all the memories together, and then figures out what is relevant, adds new things to the memories, and then deletes old, stale memories that are not relevant.
2:56 · And you can see this in action by first enabling Auto-Dream by doing /memory and making sure that is on. And right now, the /dream command doesn’t work because it hasn’t officially been rolled out to everyone, this particular skill. But if you just kind of tell Claude Code like “dream auto dream autodream”, then you can see right here it started dreaming. So if I do /tasks, there I can see that dreaming in action. So you can see it says Memory Consolidation, reviewing 913 sessions.
The Implications
3:27 · So it’s saying starting memory consolidation dream. Let me orient first. So maybe if you’re watching this later on, the /dream thing will actually work. Now you can see what it’s doing is it’s going through all the previous sessions. So it says, “Let me gather recent signal from the transcripts. I’ll search for key patterns across the 913 sessions.” So it’s searching for user feedback, corrections, important decisions, and recurring themes automatically in the background.
3:52 · So whilst we’re waiting for this to complete, I’ll quickly explain what’s happening behind the scenes. So we essentially have three different phases of this Auto Dreaming process. Phase 1: Orientation, which you can see that it’s currently doing, where it said, “I will orient myself first.” And essentially what it does is it reads through the current memory directory to kind of figure out, like, “okay, what do we have so far?” And then kind of figures out what it needs to be searching based on previous sessions. And then it starts to gather recent signal. So it starts to go through the session transcripts of all your previous Claude Code sessions, which are stored locally on your computer in these JSONL files.
4:29 · And it basically starts searching for all of them to try and find any relevant signal, new information, and identify drifted or stale memories that it can then remove. And then Phase 3 is the Consolidation phase, whereby it merges new information into existing topics. It writes any dates as well. So for example, if the memory says the words “today” or “yesterday”, then it would get the exact date, and it would remove and organize any contradictions.
4:55 · And the reason I know that this is happening behind the scenes is because I used a proxy to extract the exact system prompts that are being used. And it kind of looks like this over here. So we have Phase 1: Orientation, Phase 2: Gathering Signal, Phase 3: Consolidating, and then we have one more phase called Pruning and Indexing. Because the main MEMORY.md file for your project should be an index referencing other types of memories rather than being the memories itself.
5:22 · Six minutes later, it’s still underway reviewing the memories. And do bear in mind that during this process, we can be using Claude Code normally, and it will be dreaming in the background. So this dreaming does not actually stop you from using Claude Code. Now, before continuing, if you spend all day in Claude Code like me, then you may want to sign up to my free Claude Code newsletter. I send it out every time I find something interesting in Claude Code, and signing up does give you access to a bunch of free videos covering ideas that you won’t find anywhere else on YouTube.
5:49 · Now, this Auto Dream feature does not run constantly behind the scenes. It checks two conditions. Firstly, has 24 hours passed since the last consolidation? And secondly, have more than five sessions happened since then? And you don’t have to worry about it accidentally making changes to your project’s files because it runs in a read-only mode when it comes to your project code, but has write access to the memory files themselves. And secondly, there is a lock file, which means that two instances of Auto Dream can’t run at the same time on the same project.
6:20 · Anyway, we can see that after about 8-9 minutes, it consolidated those memories behind the scenes. And then I can see the consolidated files here. So there’s one about me and my own role, there’s another one about any recent activity inside the project, and then there’s the main index file, and then a previous file that didn’t need changing. Now, as a meta-point, what I’ve been finding interesting is that when making agents, we’ve kind of been modeling it after human behavior and human organizations: so sub-agent teams and sub-agents can interact with each other, kind of like an organization would. And now we have this whole idea of agents dreaming, kind of like people, to consolidate their memories.
6:55 · Now, it is worth bearing in mind that even though the feature is working inside of Claude Code, it hasn’t officially been announced, so they may make changes to it in some way. And finally, if you want to learn to become a Claude Code power user, because this is increasingly the best tool to be using in 2026, then I do have a masterclass all about this. It is the most comprehensive and the first class all about Claude Code. Many people from some of the world’s biggest organizations have taken this and have gone on to be the best Claude Code users at their companies. So if you want to learn to master the most important tool of 2026, then there will be a link down below to sign up.