Keep every important change recoverable

How version history works

Browser edits and MCP writes share one revision and history policy. Versions support review and recovery, while revision checks prevent stale content from silently replacing newer work.

Membership and retention limits

Version history is a Lifetime benefit. Each document can retain 1–100 versions, while the whole account shares a cap of 100; the oldest entries are pruned first when a limit is exceeded.

Core capabilities

• Throttled snapshots — Regular browser edits are grouped over time instead of creating a version on every autosave.
• Flexible limits — Enable or disable history and choose a per-document retention limit from 1 to 100.
• Safety snapshot — Even with full MCP history off, the latest recoverable state is kept before an agent replacement.
• Conflict detection — Updates require the latest revision. A stale write fails instead of replacing newer content.
• Undoable restores — The current state is saved before restoring an older version, so the restore can be reversed.

Review and restore on the web

1. Open Version history from the editor toolbar to see the versions retained for the current document.
2. Each entry records its time and source: web editor, MCP agent, or a previous restore.
3. Restoring makes that version current while preserving the pre-restore state as another recovery point.

Version policy for MCP writes

• Choose separately whether agent writes retain full history.
• Turning full history off does not remove the safety snapshot for whole-document replacement.
• Authorized read/write MCP clients can inspect and update the policy; read-only tokens can only inspect it.

Recommended settings

Keep version history and full MCP history enabled for important documents. Balance the per-document value against the shared 100-version account cap, and have agents read the latest revision before replacing a document.