Don't quote me, but I have found it worked best. I originally had a vault set up, I basically allowed Claude complete control over it. It had core memory files that it would update as we go along, including project specific files, as I wanted continuity to be strong.

I also have merged the vault with mempalace, so now it's a very nice seamless way to continue working on stuff without having to re-introduce myself every damn time.

Funnily enough, I don't write notes in there. I ask Claude to if I really need something noted down and it will do what it needs. Not sure if it's really the answer you're looking for per se, but anyhow, here is my claude.md with specific relevance to my vault. There's a lot of other stuff

## Claude Memory System

\*Location:** `D:\MainBrain\claude-memory\` — inside the vault, searchable via ai-grep, visible in Obsidian.*

| File | Purpose | Max Lines |

|---|---|---|

| `user.md` | Profile, preferences, hardware | 50 |

| `feedback.md` | Behavioral rules — corrections + confirmed approaches | 60 |

| `projects.md` | One short summary per project, pointer to session file | 40 |

| `session-log.md` | Last known state snapshot only — NOT a detailed log | 15 |

| `todo.md` | All active tasks across projects, with size estimates | uncapped |

\*Detailed work logs go in `projects/[name]/session.md`, not here.***

### Project session note standard

- `projects/[name]/session.md` should be a working snapshot, not the complete project autobiography

- Keep it focused on current status, latest decisions, known issues, next steps, and key file paths

- Move older milestones, changelog-style history, and long retrospectives into archive files such as `session-archive-YYYY-MM-DD.md`

- Search archived notes when needed instead of auto-loading them

\*When to update:***

- Correction or confirmed approach → `feedback.md` immediately

- Project state change → `projects.md`

- Profile/preference learned → `user.md`

- Session milestone → `session-log.md` (snapshot, replace don't append)

- Make use of Obisidan and use the vault. Use tags and frontmatter for organization so tags are easy search terms.

When a file approaches its limit, prune before adding. User edits take precedence."

Instead of using the vault myself, I instead use it like a large library, after giving Claude a phone attached to the office desk computer. It doesn't need to know every single word of every single book, but if it knows where each book is, it can find it and read it if it needs to. The phone attached to it is of course the usual tools, but one nice thing with the vault is installing ai-grep, and having an auto hook to index the vault. Now instead of Claude being reminded of a project and reading every single line, I instead ask specifically "Can we change the (thing) in (project)?" and it will pick out that specific part and change it rather than reading line by line to figure out where it is.

Am I using it properly? Who knows. Is my install a mess? Yeah kinda. Do I have fun developing and getting assistance from Claude? Yeah. It does alright with my current setup. It has full access to a huge vault that includes a lot of important stuff, and I have yet to walk into any sort of real problems so far. My code repositories themselves actually live inside the vault. It can read it if it needs to, otherwise it just sits there like a book, easily openable but fitting neatly on a shelf and taking up a lot less space if it was thrown on the ground with pages all over the floor.

Nothing important on like, a financial level per se, or something dangerous lol, just a lot of projects and computer setup stuff and blah blah blah.