Skip to content

History & Checkpoints

vord writes a checkpoint when a turn ends. Each checkpoint is a local commit on a hidden ref (refs/vord/checkpoints/…). It is not a branch, and nothing is pushed. Files over 50 MiB are left out of the checkpoint.

The Inspector’s Timeline tab lists the checkpoints of the selected session, newest first. A row shows the turn, when it was saved, and how many files changed. Select a row to open that turn’s diff. Back returns to the list.

A row can carry these badges:

  • Before restore — the safety checkpoint written immediately before a restore.
  • Restored here — a restore landed on this checkpoint.
  • A commit count, when commits from the session are tied to this checkpoint.
  • A fork count, when other sessions were branched off from this checkpoint.
  • Parallel, when other sessions worked in the same folder during that turn. Hover the badge for their names.

Show Timeline in the session menu opens the same tab.

Restore to here… puts the session’s files back at that checkpoint. vord writes a safety checkpoint first, so the files you have now are kept as their own point. HEAD and the index stay unchanged. The agent is told once, on its next prompt, and not again on later turns.

vord does not restore while the agent is working. Wait until the turn has finished.

Branch off from here starts a new session in its own worktree, with a fresh conversation. The session you branched from stays as it is.

Settings → Workspace → Sessions & Opening has Keep checkpoints for. The stepper runs from 7 to 365 days. The default is 30. Older checkpoints of a session are removed when vord starts, once that session is no longer running.

In Cowork mode the Timeline tab shows the project’s saved states, newest first. A row shows when the state was saved and how many files changed; hover a row to see the file names.

Restore this saved state… puts the files back at that state. vord keeps the current files first as their own saved state, so nothing is lost. While an answer is running, restoring is locked — wait until the current answer has finished.

Start a new conversation from here restores the state and then starts a new session in the same project with a fresh conversation.

Select a state to see its changes against the previous saved state. Each changed file offers Looks good (a checkmark, just for you — nothing is sent) and Please change… (a wish in your own words, added as a review comment on that file). Comments are sent to the session with the same review bar as in code mode.

The session’s “…” menu opens the same timeline as a sheet, newest first. Tap a row for that turn’s diff, comment on lines, and send the review. Restore to here… and Branch off from here (Cowork: New conversation from here) ask for confirmation on the button you tapped. An older Mac, or a Headless host that does not announce the feature, hides the menu entry. Guests of a shared session do not see it.