Launch bonus Yearly plans 20% 40% off

Version History and Provenance

The agent edits your map for you, so you need two things to trust the result: a way to see exactly what it changed, and a way to step back. Agent Bayes keeps recent versions of every mindmap, shows any change as a colored comparison you can partly revert, and lets you save named versions you can return to months later. Every claim also keeps its citations, so you can trace it to the page it came from.

Undo and redo

The arrows at the top of the map undo and redo changes. The shortcuts are ⌘Z and ⌘⇧Z on a Mac, or Ctrl+Z and Ctrl+Shift+Z elsewhere.

  • One step is one version. A batch of your own edits is one step. The agent saves a version each time it applies edits, so one answer that edited the map in several passes takes several undos.
  • The last 20 versions are kept for each mindmap, so you can undo about 19 steps back.
  • A new edit after an undo replaces the redo path. Redo only works until you change the map again.
  • Undo waits for the agent. Undo and redo are off while the agent is working on the map.

For anything you may want to return to later than 20 steps, save a snapshot (see below).

Review what changed

The eye icon opens a comparison of the map before and after a change. You can open it from three places:

  • Review last change, the eye icon between undo and redo, compares the map with the version before the latest one.
  • Review Edits, the eye icon on an "Applying mindmap edits" card in the chat, shows what that one step of the agent's work changed.
  • Review what this answer changed, the eye icon under an agent answer, shows everything the answer changed, from before its first edit to after its last.

While you review, a banner at the top of the map names what you are comparing and counts the changes. Changed claims are colored:

  • Green for claims that were added.
  • Red, struck through, for claims that were removed.
  • Yellow for claims whose text changed, with the removed words struck through.
  • Green at the new place and faded red at the old place for claims that moved.

Press Esc or click the × in the banner to leave the review.

Reviews are available while the versions they compare are still among the last 20. When newer versions exist, a review becomes read-only and says so in the banner.

Revert one change

The agent's edits are already applied, so you never have to accept them. You only revert the ones you do not want. In a review, select a changed claim and a button appears above it:

  • Remove added node for a claim the change added.
  • Restore removed node for a claim it removed.
  • Move back or Restore order for a claim it moved.
  • Restore text, Restore citations, or both, for a claim it rewrote.

The same actions are in the right-click menu. When a revert would break the map, for example restoring a claim whose parent was also removed, the button is disabled and its tooltip says what to revert first.

You can keep editing during a review. Your edits and reverts are held until you leave the review, then applied together.

Save versions with snapshots

The 20-version history rolls forward as you work. A snapshot is a named version that stays until you delete it, so save one before a big restructure or before each supervisor meeting.

Click the Snapshots icon at the top of the map, type a name, and click Save. Without a name, the snapshot is named after the date and time.

Each snapshot has four actions:

  • Compare with current opens the same review as above, comparing the snapshot with the map as it is now. You can revert single changes from there.
  • Restore this snapshot replaces the map with the snapshot. The restore is itself a new version, so undo brings back what you had.
  • Rename and Delete. Deleting a snapshot never changes the map.

Each mindmap holds up to 50 snapshots. You cannot save or restore one while the agent is working on the map.

Compare with the published version

If you published the map as a public link, the Share menu has a Diff button that compares the published version with the map as it is now. Use it to see what readers of the link will get, then Republish when you want them to see the current map.

Trace a claim to its source

Provenance in Agent Bayes lives in the citations. Every claim the agent writes carries citations to passages in your library, with the author, year, and page.

  • Click a citation chip on the map to see its passage in the sidebar.
  • Click the reference there to open the PDF at that page.
  • Select a claim and open the Indexed Citations tab to see all of its citations and the key points of each passage.

To see which answer produced which claims, use the review icons in the chat: they show exactly what each answer added, moved, or rewrote.

A claim itself does not record who wrote it or when, and there is no list of past versions to browse. For a lasting record of how the map developed, save snapshots at the points that matter, such as before a restructure, after a supervisor meeting, or when a chapter draft is done.

From Claude Code

If you use Agent Bayes through the MCP server, the same history is available to your agent: it can list the recent versions of a map and undo or redo them.

What's next