Docs/Right sidebar/History
History
Every time a note is saved, Minerva keeps a copy of what it looked like before. This panel is where you read that record: a list of versions with the date, the time, and a line saying what produced each one — your own edit, a thinking tool, a restore. Pick a version to see what changed since, and put it back with one click if you'd rather have it.
Nothing here needs setting up, and none of it is a commit. History is kept automatically, on this machine, for every note — including the .csv, .ttl and .py notes, not just the markdown ones. It lives in the .minerva folder beside your notes and never leaves your computer, so it isn't part of publishing and doesn't travel with a note you export. Renaming or moving a note — or a whole folder — takes its history along with it.
Reading the timeline
Versions are listed newest first. Each row carries two lines: when the version was saved, and what caused it.
Comparing and restoring
Click any version to compare it with the note as it stands now. The count at the top says how many lines would be added and removed, and the lines themselves are listed below — added in green, removed in red.
Naming a version
A date and time tells you when something happened, not why it mattered. Right-click any version and choose Label Version… to give it a name — before rewrite, submitted draft, last good copy — and it becomes easy to find weeks later. Right-clicking a version that already has one offers Rename Label… and Remove Label instead.
Unnamed versions are dropped once they age out of the retention window or fall off the per-note limit (see Settings → Versioning). A named version is exempt from both — naming one is how you keep a particular state of a note indefinitely.
Naming several notes at once
A restore point is often bigger than one note. In the Notes panel, select the notes (or a folder) you're about to change, right-click and choose Label Version…: the current version of every note in the selection gets the same name. One name, one moment, however many notes — the thing to reach for before a refactor or a big AI-assisted pass.
Nothing is written into the notes themselves; the name is attached to their history, exactly as it would be from this panel. Notes that can't be labelled are reported afterwards, and the rest still get their restore point.
Looking back across several notes
This panel follows one note. To see what happened to a set of them — a folder after a big AI-assisted pass, say — select the notes or folder in the Notes panel (or right-click the thoughtbase itself), right-click and choose View Local History…. One timeline opens for everything in the selection, newest first, including notes that have since been deleted. Each row gives the time, whether the note was added, modified or deleted, its path, and what caused it.
A note Minerva has never recorded a version of — one added by another app and never edited here — has no history to say when it appeared, so it counts as not existing yet at any past moment, and reverting removes it. The preview marks it will remove; read the list before you press Revert.
Deleted notes keep their history
Deleting a note records its final text and then a Deleted marker, so its history outlives it. A deleted note no longer has a row in the Notes panel to right-click, but its old folder does: select that folder (or right-click the thoughtbase itself) and choose View Local History…, and the note is in the timeline. Pick a moment from before it was deleted and revert — that's how you bring a deleted note back. The marker is never pruned; the text ages out under the same limits as any other unnamed version.
How much is kept
By default a note keeps its unnamed versions for 30 days, up to 500 of them, and files over 1 MB aren't recorded at all. Versions you've named and delete markers are kept regardless. All three limits are adjustable — see Settings → Versioning.