Runic
HISTORY

Snapshots you can name, pin and restore

Runic records the document as you save it, keeps the 50 newest automatic snapshots, and never drops the ones you name.

Try it free →Read the docs

What gets recorded

When the editor saves, the server compares the new text with the newest snapshot. If that snapshot is older than ten minutes and the text differs, a new one is stored. Autosave runs about 600 ms after you stop typing, so the first save after a ten-minute gap becomes a version. Text identical to the newest snapshot is not stored again.

Runic keeps the 50 newest evictable snapshots per document: the automatic ones, and the pre-edit snapshots MCP writes take while they still carry their automatic name. When a new one arrives, older evictable rows are deleted. Naming a snapshot pins it — an automatic one or an MCP one — and named snapshots are exempt from that count, so pinned versions never crowd recent history out. Clearing a name puts the row back in the count.

One more kind of snapshot protects people working at the same time. Every save from the editor says which version it was based on. If someone else — another tab, a teammate, Claude over MCP — changed the text in between, the save still lands, but the text it replaces is stored first as “Before a concurrent overwrite”, and the editor says so with a History button that opens on that row. These rows have a pool of their own, also capped at 50, so two people typing in one document never push the ordinary history out.

Reading the list

Open Version history with the clock icon at the top of the editor, for a process or a sequence diagram. The dialog is titled with the document name and the rule: 'automatic snapshots every ~10 minutes of editing. Name the ones worth keeping; a named snapshot is pinned and never rolls off.' Rows come newest first, up to 200 of them. Each row shows the label chip or a '+ name' button, a blue 'MCP' chip when the snapshot was taken by an edit Claude made over MCP, an amber 'OVERWRITTEN' chip when a concurrent save kept it, the timestamp, and a line reading 'N lines · same as now' or 'N lines · now +A −R' — how many lines the current text has added and removed since that snapshot — followed by the first 40 characters of the document's first line. With no snapshots yet it says 'No snapshots yet — keep editing and they’ll appear here.'

Naming and restoring

Click '+ name', type a label of up to 60 characters and press Enter or click away; the row gets a violet border and your label as a chip. Click the label again to rename it, or clear it to unpin. Esc cancels the edit.

Restore asks first: 'Restore this version?', with the document's name, the snapshot's time and how many lines change. Confirm and the text you are leaving is saved as a version, the snapshot's text goes into the editor, and a toast offers Undo, which puts the previous text straight back while the document still holds the restored one. The change saves like any other edit, so you can restore a restore.

History from Claude

The MCP server exposes list_versions, diff_versions and restore_version. list_versions prints one line per snapshot: id, ISO timestamp, line count, the label if there is one, and 'mcp' when Claude's write took it. diff_versions shows the line diff between two versions, or a version and the current text, with what the structural audit gained or lost. restore_version snapshots the current text first, labelled 'Before Claude restore (MCP)', then replaces the document. write_document goes through the same snapshot path, so an edit Claude makes can be undone from the same list.

When Claude edits a document while your tab is in the background, the next time you return Runic re-fetches the list, swaps the changed text in and shows a toast: 'Claude edited “Name” over MCP while you were away.' with a 'History' button that opens this dialog.

Limits and gotchas

History is a server feature: the clock icon only appears when you are signed in. The local mode used by the /learn tour has undo and redo but no snapshots. There is no 'Save a version' button; edit, wait for autosave, and name the row that appears.

Team viewers can open History and read every snapshot, but naming needs editor or owner access, and Restore does nothing on a document you can only view.

The newest automatic snapshot can be up to ten minutes behind your current text; a restore saves the current text as a version first, so the state you leave is never lost. A snapshot Claude took over MCP stays in the evictable pool even after you name it.

Deleting a document deletes its snapshots. Deleting your account deletes everything, versions included.

How to use it

  1. Click the clock icon
    It sits in the editor toolbar next to undo and redo, titled Version history. The dialog lists snapshots newest first.
  2. Read the rows
    Timestamp, 'N lines · now +A −R' or 'same as now', and the first line tell you which version is which. Named versions have a violet border and a label chip; an 'MCP' chip marks snapshots Claude's edits took, an 'OVERWRITTEN' chip the text a concurrent save replaced.
  3. Name the one worth keeping
    Click '+ name', type up to 60 characters, press Enter. Escape cancels. A named snapshot never rolls off.
  4. Restore
    Click Restore on a row and confirm. The current text is kept as a version, the editor takes the snapshot's text, and the toast's Undo brings the previous text back.
  5. Close with Esc
    Escape closes the dialog, like every other overlay in Runic.

Commands & shortcuts

Clock iconOpens Version history for the open document (signed in only)
+ nameLabels a snapshot (60 characters max) and pins it
Enter / EscapeCommit or cancel the label
MCP chip'Snapshot taken by an edit Claude made over MCP'
OVERWRITTEN chipText a concurrent save replaced, kept as 'Before a concurrent overwrite'
now +A −R · same as nowLines the current text has added and removed since that snapshot
RestoreAsks first, keeps the current text as a version, then restores; the toast offers Undo
EscCloses the dialog
list_versions (MCP)id · ISO time · line count · label · mcp, newest first
diff_versions (MCP)Line diff between two version ids or 'current', plus the audit delta
restore_version (MCP)Snapshots the current text as 'Before Claude restore (MCP)', then restores the given version id

Tips

  • Name a snapshot before a big rewrite. A named version survives no matter how many edits follow.
  • The first line of each row is the document's first line, so a clear opening step doubles as a version description.
  • Ask Claude: 'list the versions of Onboarding and restore the one labeled Approved'. The MCP tools do exactly that.
  • If you want a snapshot right now, edit, wait for autosave, and check History. A save more than ten minutes after the previous snapshot always creates one.
  • 'same as now' on the newest row means nothing has changed since the last snapshot; a restore to it would be a no-op.

Questions

How many versions are kept?

The 50 newest snapshots that are still automatic — including MCP rows under their own label — plus every snapshot you have named, however old. The dialog shows up to 200 rows, so pinned versions beyond the 50 still appear.

Why is my latest change not in History yet?

Snapshots are throttled to one per ten minutes. Keep editing and the next save after the window creates one.

Can a viewer restore an old version of a team document?

No. Viewers can read History; naming and restoring need editor or owner access.

Is a restore reversible?

Yes. The text you leave is saved as a version before the restore, and the toast's Undo puts it straight back.

What does the MCP chip mean?

Before Claude changes a document over MCP, Runic snapshots the text as it was, so the state before Claude's edit is one Restore away. Those rows carry the chip and are listed as 'mcp' by list_versions.

Two of us saved the same document at once. Whose text won?

The later save is what the document holds, and the earlier text is in History as 'Before a concurrent overwrite', marked OVERWRITTEN. Both people are told: the one who saved second right away, the other the next time their tab checks in. Nothing is lost silently.