Claude Memory Dreaming: Background Notes in Claude Code

Memory dreaming, in the Claude Code context, refers to a background process that consolidates and reorganizes the memory notes Claude Code has accumulated during active sessions. Rather than a biological metaphor, it is a maintenance step: Claude Code reviews its stored notes, removes redundant entries, strengthens connections between related facts and writes an updated version. Tools like fenbs keep the reviewed lessons and decisions that matter in a shared record outside Claude's notes files, so important conclusions survive any changes to those files.

The key word is "background." The process runs when Claude Code is not actively working on a task, which means you may return to a session and find that memory files have changed without you being present for those changes. Understanding what changed and why is what this guide covers.

What Claude Code stores in memory notes

Claude Code stores information in several files that it reads at the start of each session. CLAUDE.md at the project root holds project-level instructions and context. CLAUDE.md files in subdirectories can hold folder-specific context. Claude Code also maintains its own notes in a memory location that varies by installation.

These notes contain things Claude has learned during sessions: patterns it noticed in the codebase, preferences you expressed, recurring tasks, and context it added to help future sessions. The memory dreaming process works on these stored notes.

The Claude Code memory guide explains the full memory architecture, including where files are stored and how Claude Code loads them. The Claude project memory guide covers project-level memory specifically.

How to check what the background process changed

After a period of Claude Code inactivity, check whether its memory files have changed before starting a new session. The simplest way is to look at the modification timestamp of the CLAUDE.md files and any other memory files in your project. If a file was modified at a time you were not actively working, the background process may have made changes.

Read the changed file and compare it to what you remember. Look for additions, removals or reorganizations. A useful consolidation removes duplicate entries and makes the file clearer. An unhelpful one removes context you still need or adds inaccurate inferences.

If you use version control for your project, commit your CLAUDE.md files before extended Claude Code use. That gives you a clean diff when you check what changed.

Why automatic consolidation is not the same as human review

Memory dreaming is an optimization step, not a decision step. Claude Code cannot verify whether a remembered pattern is still accurate, whether a preference you expressed once still applies, or whether a simplified version of a rule preserves its meaning. It reorganizes what it has; it cannot audit whether what it has is correct.

That is why important decisions and standing rules belong in a record a person can review, not only in an AI notes file. An AI notes file is a convenience for the model. A shared record in fenbs is a source of truth that people and models read together.

What to keep in fenbs versus what stays in Claude's notes

Claude's memory notes are well suited for low-stakes preferences and codebase patterns that improve session quality: "this project uses named exports throughout," "tests live in the __tests__ directory next to the source file," "the linter is configured at the repo root."

Decisions that a person made, rules that must be followed, and lessons learned from significant failures belong in a shared record that is not subject to background modification. A rule that was agreed by a person should not be quietly reorganized out of the file during a consolidation pass.

Store those in fenbs as Decisions and rules and Lessons learned. A connected Claude Code session reads them at the start of each run, and they are visible to teammates. That also means the next session that connects to the project reads both the Claude notes and the shared decisions, rather than only one or the other.

How to respond when a consolidation removes something you needed

If a memory dreaming pass removes a note you needed, add it back. If the same note gets removed repeatedly, move it out of the memory notes file and into a more permanent location: CLAUDE.md directly, the project's documentation, or a Decisions and rules entry in fenbs.

Repeated removal is a signal that the memory system considers the note low priority for retention. If it matters to you, keep it somewhere more durable than a notes file that is subject to background optimization.

How to do this with fenbs

1. Create a free account and add the project. Move important decisions and rules out of CLAUDE.md memory notes and into fenbs as Decisions and rules. They are now in a record a person maintains, not one a background process reorganizes.
2. Add significant debugging findings and lessons as Lessons learned in fenbs. The next Claude Code session reads them before starting similar work.
3. Connect Claude Code over MCP from Integrations. At the start of each session, ask it to read the project context. It reads both the CLAUDE.md file and the fenbs record.
4. After you notice a background consolidation, check the changed files with a diff. Restore anything that was removed incorrectly, and move repeatedly-removed items to a more durable location.
5. Treat fenbs as the durable layer and Claude Code's notes as the session layer. The notes optimize the model's performance; fenbs carries the decisions and lessons that must survive any consolidation pass.