Versioned Save and notes that remember

Markdown Locker 1.5.4 is out. The headline is quiet on purpose: when you overwrite a note, the previous body is kept on disk, and the live file says when it changed.

What Versioned Save does

Save an existing note with a real change to the body and the app:

writes a copy under versions// with a UTC timestamp name, then updates the live note’s frontmatter with updated, a bumped version, and a previous path pointing at that archive.

If the body did not change, nothing is archived. New notes do not invent history. Explore still lists the top-level files — the archive tree stays out of the way until you need it.

Why it matters for agents

Models are better when they can see how a brief evolved, not only the latest paste. Frontmatter is a cheap chronology. The archive files are ordinary markdown if something needs a full read. Same folder humans already own; no second database.

Separately, we shipped a small native MCP in the repo — search_notes, read_note, list_recent — so Grok Build and other agents can attach to the Locker without treating it as a generic home directory. Setup stays on the machine: read-only, path-scoped. Details: Connect Grok.

What we did not put in the DMG

MCP is not a cloud connector inside the app binary. It is a local process you point an agent at. In-app “copy MCP config” belongs next to identity and keys — settings territory — and will follow. Versioned Save is the piece that had to ship in the Mac build so every save path behaves the same.

Download: v1.5.4. Positioning: notes for AI agents.