Versioning & checkpoints

Iterating with an AI should feel safe. Waveform records the before-state of every change it makes, so nothing you try in conversation is irreversible.

Change history

Every tool action that touches your site is logged with what changed and what was there before. You can ask "what changed today?" or browse the history rail in the workspace to see each step, with file-level diffs.

Undo

• Last change: say "undo that" or use /undo.
• A specific change: point at it — "undo the pricing section rewrite from earlier".

Undo restores the recorded before-state; it doesn't try to reconstruct or re-generate anything.

Checkpoints

Before a big experiment — a redesign, a restructure — save a checkpoint:

"Save a checkpoint called before-redesign."

If the new direction doesn't work out:

"Restore the before-redesign checkpoint."

Checkpoints capture your site source as a named, restorable state. Use them like save points; they're cheap.

Automatic safety net

Waveform also protects itself: if a change breaks the build, it repairs or reverts automatically rather than leaving your preview broken. Combined with the quality gate, the system is designed so that the version of your site you see is always a working one.

What versioning does not cover

Published deployments have their own history and their own rollback — see Previews & publishing. Undoing a source change does not automatically un-publish a deployed release.