A local version on every write, kept whether or not you use Git.
Every time a note is written, Mindex keeps a version of it. This happens automatically, on the machine, with no repository required.
Undo has a horizon and ends when the app closes. Git records what you decided to commit. Local history covers the gap between them: the paragraph you deleted an hour ago and only now realise you wanted.
The clock in the tab row opens a note's history.
The left column is the timeline, newest first and grouped by day, each entry carrying the time, the file's size and how much it grew or shrank against the version before it. The right side is the difference between the version you picked and the file as it stands now, side by side, with unchanged runs collapsed into a band you can click open.
Revert to … takes the version you have selected. It asks first, and it does not erase anything: reverting is itself a write, so it becomes the newest version and the one you replaced stays in the list. The act of reverting is undoable.
Two kinds of version are labelled, because two are worth telling apart from your own typing:
| Label | What happened |
|---|---|
| Agent | the assistant wrote it, while it was running |
| External | something outside Mindex changed the file — another editor, a git operation, a sync client |
A version is written a second or so after a change settles, so a burst of typing is one version rather than thirty.
History is for text. Images, audio, video, archives, fonts and PDFs are skipped, as is any file over 2 MB — 10 MB for a drawing.
On your disk, inside the vault's metadata. It is not uploaded anywhere, because there is nowhere for it to be uploaded to — and it is not published either: Mindex git-ignores that folder, so history stays on the machine it was made on.
| Local history | Git | |
|---|---|---|
| Records | Every write | What you commit |
| Needs setup | No | A repository |
| Travels with the vault | No | Yes |
| Answers | "What did this say before?" | "What changed, and why?" |