Version history

Bedrock keeps a complete history of every doc — automatic snapshots on every save, plus the git commit history — so you can look back, compare, and recover earlier text.

Opening the history

Open the History tab in the Inspector (right panel, *⌘*) to see the history for the currently open doc.

Automatic snapshots

Every save (autosave or ⌘S) writes a snapshot to .bedrock/history/:

Snapshots are deduplicated — no new entry is created if the content hasn’t changed since the last snapshot.
They are capped to keep the history useful without growing indefinitely.
Take a snapshot on demand from the command palette: ⌘K → “Save snapshot”.

Snapshots capture the exact file content including frontmatter, so you can see the state of type:, status:, and tags: at any point in the past.

Git timeline

If your workspace is a git repository, Bedrock merges the file’s commit history into the same timeline as the auto-snapshots — newest first. You see both Bedrock’s fine-grained autosaves and your real commits in one place, each labelled with its source and timestamp.

Viewing a diff

Click any entry in the History tab to see a word-level diff between that version and the current file:

Added text — highlighted green.
Removed text — highlighted red.
Changes highlighted at the word level, not just line level.

Example: you reworded a constraint two days ago. Click the snapshot from that day and see exactly which words changed, highlighted inline.

Restoring a version

From any diff view, click Restore to revert the file to that historic state:

Bedrock takes a new snapshot of the current content first (so you can get it back if you change your mind).
The historic content replaces the file.
The editor shows the restored content immediately.

Nothing is permanently lost — both the old snapshot and a pre-restore snapshot remain in the history.

Committing to git

When your workspace is a git repository, the status line shows the current branch and the number of changed files. Click Commit changes… to open the commit dialog:

A list of changed files appears (staged and unstaged).
Tick the files to include.
Write a commit message.
Click Commit.

Bedrock’s own .bedrock/ folder is always excluded from the staged file list. Open the commit dialog from the command palette: ⌘K → “Commit changes…”.

Tips

Trust autosave — every pause of more than a second is captured. You almost never need to worry about losing work.
Use ⌘S after finishing a logical section so that snapshot is easy to identify in the timeline.
Commit after finishing a doc or a set of related docs. Git commits are meaningful milestones; Bedrock snapshots capture fine-grained detail.