Connect your coding agent's memory
Attaching an agent's memory folder needs 1.4.3 or later.
Your coding agent writes down what it learns: the rules of the project, the
traps it paid for once, the decisions it should not have to make twice. That
adds up to a few hundred kilobytes, and almost every line is useful. The notes
sit on your disk in .claude/, .cursor/, .aider/ or .continue/, next to
the code.
From 1.4.3 you can point a vault at that folder and ask your memory what your agent knows.
Dot folders are accepted
DocWatch reads a folder whose name starts with a dot once you have declared
it. You can watch the memory folder of Claude Code, Cursor, Aider or Continue.
Inside it, DocWatch still skips dot entries: a .git or a .DS_Store stays
out.
Create a dedicated vault
Do not add this folder to an existing vault, create a new one.
Mnemosyne OS looks the answer up in a vault, and you pick that vault by its name. Call it Claude memory and you will always know where to aim. Let it mix with your project vault, and one question reaches both.
Attach the folder
Open Configure DocWatch in the vault's Sources:
- Folder to watch: the agent's memory folder.
- File extensions:
md. The notes are Markdown, and this extension leaves the rest of the folder out. - Scan and preview lists the files before it reads a single one.
Press Save this watch
The Save this watch button starts the watch. Files arrive after you press it.
The same dialog holds the optional settings: a description of the folder, a forced spine type, the auto-approve patterns and the maturation delay.
Past 150 files, the app asks you
A Large catch-up screen opens and waits for your answer: Start, Start slowed or Not now. Every watched folder follows this rule.

Two things to keep in mind:
- The number on screen is a minimum. More files can be waiting.
- Answer while the screen is open. If you choose Not now and close the app, reopen the source to get the proposal back.
What to give it
Give it the notes and the rule files: the memory folder, and the CLAUDE.md
or AGENTS.md at the root of your project. Those files hold one conclusion at
a time, each with its own reason, and recall finds them well.
The md extension leaves the rest out: the session transcripts, which are
large and hold few conclusions, and the settings files such as settings.json
or .mcp.json, which hold API keys.
Read the sources, not the score
The answer lists the files it stood on. Those tell you whether your question was covered.
For the other direction, letting Claude or Cursor read your memory, see Connect Claude to Mnemosyne OS. The engine behind this page is DocWatch.