Skip to main content

Vaults, and how to create one

A vault is an isolated memory store. Mnemosyne does not keep one large memory: it keeps several, one per domain of your life, and each lives in its own database file on your machine. Code in one, notes in another, a private journal in a third.

That separation is not cosmetic. It is what makes it possible to say "this memory never leaves the machine" without promising anything about the rest, and it is what stops a question about your work from surfacing your personal notes.

Creating a vault​

In the Vaults window, "+ New Vault" opens the creation dialog. You give it a name and the vault exists. If you have none yet, the window offers to create the first one directly.

An empty vault does nothing until something enters it. Two ways to fill one:

  • declare one or more watched folders with "Add a folder to watch", and Mnemosyne ingests what is there and then follows changes;
  • write into it from the chat or from an app, when a conversation produces something worth keeping.

What lives in a vault​

Each memory is a chronicle: some content, a type (an architecture note, code, a decision, a session), and a vector that lets it be found by meaning rather than by exact words. One watched file can produce several chronicles, because a long document is split before being indexed.

Several vaults in one answer​

By default a question queries every active vault at once, and the answer may blend what it found across them. That is the federated scope.

You can also name a single vault for a question, and the answer will read only that one. The attention slider does the same thing durably, without having to repeat it every time.