Autosave and undo

How your work is saved, what undo covers, and what it does not.

There is no save button

The save status capsule

The canvas saves itself. Changes are batched and written after about 1.5 seconds of inactivity, and at most 3 seconds during continuous editing.

A status capsule at the top left shows where you are:

Status	Meaning
Pending	Changes are queued
Saving	Being written
Saved	Everything is stored
Save failed	Something went wrong — do not close the tab

Closing the tab or leaving the canvas forces a final save first.

Undo has limits worth knowing

Undo holds 40 steps, lives only in the current session, and is cleared when you switch canvases. Reloading the page empties it.

More importantly, undo does not cover everything.

Can be undone

Moving nodes · Resizing · Resizing a text window · Aligning · Deleting nodes · Deleting a connection · Making a connection · Setting a color tag · Editing text · Editing an annotation

Cannot be undone

Creating a node · Pasting · Duplicating · Uploading · AI generation results · Creating a group · Creating or deleting a canvas

The practical consequence: if you paste twenty nodes by accident, ⌘Z will not take them back. You have to select and delete them — and that deletion is undoable.

⌘Z undoes, ⌘⇧Z redoes (Ctrl+Y also works on Windows). The viewport control bar has buttons for both.

Real-time sync

Canvases sync between people working on them. Incoming changes from teammates are applied to your board without a refresh.

WJI holds an incoming change back briefly if you are mid-interaction, and ignores the echo of your own writes, so a teammate’s edit does not interrupt a drag you are in the middle of.

There are no presence indicators — no cursors, no avatars, no highlight showing what a teammate has selected. You see the results of their edits, not their pointer.

What is not stored

Undo history and your current selection are session-only. Viewport position, performance mode, and panel widths are remembered locally in your browser, per canvas.