Saving and versions

Work in a project saves itself, every save is kept as a version, and nothing is ever overwritten.

Saving is automatic #

Work in a project saves itself a moment after you stop. There's no Save button to remember. The status pill in the bar shows where you stand; see The save status.

If the connection drops, your work stays safe on this computer and saves when you're back. If a save fails, click the badge to retry.

Work that isn't in a project (Local) saves in this browser only. See Local only.

Every save is a version #

Each save of a scheme is kept as a version. Quick saves while you work are bundled, so the history stays readable. Nothing is ever overwritten.

A snapshot is a version you freeze under a label, like "Issued for permit". Snapshots are how you mark the versions that matter. See Snapshots.

Go back to an earlier state #

In this session: use Undo, Redo or History in the bar. See Undo and history.
To a snapshot: restore it from Share / Snapshots in the tool, or from Snapshots on the project page. The current state is snapshotted first ("Auto — before restore"), so nothing is lost. See Restore and copy.
To any version: an AI assistant connected through the AI connector can compare versions and, for some tools, restore one for you.

Two people at once #

When several people edit one scheme, each save lands on top of the latest version. If someone else saved first, the tool merges their changes into yours and says so:

Someone saved first — their changes are merged in; yours save next.
Merged in changes someone else saved, with how many edits overlapped. Where you both changed the same thing, your edit on screen is kept.

The tool also checks for newer versions while you have it open, so you see teammates' work as they save it.

Deleted schemes #

A deleted scheme or project can be restored for a while from Recently deleted. See Recently deleted.