Guides
Memories
Claude Code’s auto-memory saves notes in projects/<name>/memory/, one Markdown file per memory, plus a MEMORY.md index that Claude reads at the start of every session in that project. The memories of your home folder’s project act as general memories: they load whenever you start Claude Code from your home.
Browse
Pick a profile and a project in the list (on the left, or above on a phone). By default only projects with memories are listed; tick also show projects without memories to see every project, for example to pick a destination.
Each memory shows its name, type (user, feedback, project, reference) and description, taken from the file’s frontmatter. Two problems are flagged:
- not in MEMORY.md: the file exists but the index does not list it, so Claude may never read it.
- MEMORY.md lists files that do not exist: the index points to a deleted file.
Edit
Click a memory to open it in the editor. Save keeps the previous version in a backup; Cancel puts back what was last saved.
Move
Move… sends a memory to another project, in the same profile or a different one. The line is removed from the source MEMORY.md and added to the target’s (created if needed). Moving fails if the target already has a memory with the same file name.
Typical uses:
- a memory saved in the wrong project
- a preference that is about you, not one project: move it to your home project so it applies everywhere
- a work memory that ended up in a personal profile
Share with another profile
A project you open with two accounts can keep one memory: what Claude learns about it in one profile, the other knows too. Pick the profile that holds the memories and the project, then Share with… and the other profile. The window says what happens to that profile’s own memories of the project before anything changes.
- The other profile’s memory folder becomes a link to this one (
~/.claude-work/projects/<project>/memory → ../../../.claude/projects/<project>/memory), as with sharing. Claude Code reads and writes through it, so both profiles see the same files. - Its own memories of the project join the shared ones, with their
MEMORY.mdlines. One with a file name already there keeps the shared version; its own goes to the backup. - A profile that never opened the project gets it, with the shared memory only.
- Only the memory is shared. Conversations, prompt history and the project’s settings stay per profile, and so does the login.
The project list marks such projects shared. In the other profile the project says Shared: the same memories as the holder, with Separate; in the holder, Stop sharing next to each profile does the same. Separating gives that profile its own copy of the memories as they are: from then on changes no longer cross.
While other profiles use a project’s memory, the holder’s project cannot be moved, relinked, merged or deleted, and the holder profile cannot be deleted: their links would point to nothing. Separate first. Moving the project of a profile that uses a shared memory keeps the link in the new profile; relinking it to another folder gives it a copy of its own. Every step is in a backup and can be undone.
Delete
Delete removes the line from MEMORY.md and moves the file to the backup.
Example: a preference saved in one project
While working on ~/code/blog you told Claude “answer in Italian”, and it saved a feedback memory there. You want it in every project.
- In the Memories tab, pick the profile and
~/code/blog. The memory is listed with its type and description. - Click it to check the text, and fix it in the editor if needed. Save.
- Click Move… and choose your home project (
~) in the same profile.
From the next session it is one of your general memories, like the others of your home project. The MEMORY.md of both projects is updated, and the move is in the Backups tab.
Good practice
- Memories that contradict the current code are worse than no memory: Claude follows them confidently. Delete memories about things you removed.
- When the same preference shows up in several projects, merge it into one memory in your home project.
- For context that must always apply in a profile (“in this profile you work for …”), use the profile’s
CLAUDE.mdinstead: it is always loaded, while memories are recalled when relevant. See Settings.
Something wrong, unclear or missing on this page? Open an issue on GitHub