Version history

Every project keeps a history of itself, the same way a document in Google Docs does: it saves automatically as you work, and you can name any point in that history, compare two points, or go back to an earlier one. Click Project → History in the toolbar to open it — it shares the right-hand sidebar with the AI agent panel (see Agent next to it), so opening one closes the other.

Auto-saved and named versions

• Your edits are always saved as you work, but an auto version is only created when you come back to a project after being away for a while (more than three hours by default) — it captures the project exactly as you left it at the end of your previous session, before your new edit takes effect. Editing continuously doesn’t create a stream of auto versions; there’s no timer running while you work. These aren’t meant to be read one by one — the history panel hides them behind a Show auto-saved versions switch, always keeping the very latest one visible.

• Type a message and click Commit to create a named version — a deliberate checkpoint, like “before changing the pricing logic”. If nothing has actually changed since the last version, this just names that version instead of creating an empty new one.

• A version can be renamed later from the history list, whether it started out auto-saved or named.

• Publishing a project (see the toolbar’s Publish) always creates its own named version, so a published version’s exact source is always something you can look back at and compare against later.

Comparing two versions

Opening the history panel shows, right away, whether your current unsaved work differs from the last version — the same “changes since last commit” idea as a source control tool. Click Compare to see exactly what changed, or use Compare with working copy / Compare with previous on any version in the list.

• The diff opens side by side: the earlier version on the left, the later one on the right, both read-only. Added, removed, moved, and changed icons are outlined in green, red, blue, and amber.

• Use the previous change / next change buttons to step through everything that’s different without hunting for it on the canvas yourself.

• Click any highlighted icon to see exactly which fields changed, old value next to new.
• Renamed, added, and removed documents and folders are listed too, not just changes inside one document.

Restoring an earlier version

Click Restore on any version in the history list. Your project is replaced with that version’s content — documents that didn’t exist yet at that point are removed, ones that were deleted since are brought back. A new version is created automatically right afterward recording the restore, so restoring is itself never a destructive, un-loggable action: the version you restored from is still there in the history, right where it was.

What isn’t versioned the normal way

The project’s Integrations document (your connected accounts and credentials) is versioned along with everything else so you can see which integrations were configured at any point in time — but the secret half of each credential (API keys, tokens, passwords) is never included in a version’s content, the same way it’s never included when you export a project. Restoring an old version never touches your currently stored credentials: a credential that still exists keeps its current secret value, and one that no longer exists comes back needing to be reconnected.