Undo, but for an entire site

Ctrl+Z works inside a single editing session. It doesn't help you when the site you're looking at today is subtly worse than the one from last week and you can't remember which change did it. That's the gap Version History closes.

Every save is a snapshot

Every meaningful write to a page's component tree — a canvas edit, an AI chat generation, a code editor save, a change made through an MCP tool like push_files — records a full database snapshot, not just a diff. Open the panel and you're looking at a real timeline you can preview and restore from, not a best-effort undo stack.

The part that used to be confusing

If you make an edit through Claude or another MCP client while the dashboard is open in a different tab, the dashboard used to keep showing the stale version until you refreshed. The panel now polls for exactly that case — changes made outside the open tab — so the history list stays accurate without you having to remember to hit refresh.

When to actually use it

• Before a risky AI regeneration on a page you like — snapshot first, prompt second.
• After noticing a visual regression you can't immediately explain.
• When two people on a team edit the same page close together and you want to see who changed what.

It's not a replacement for git-style branching — there's one linear timeline per page. For a marketing site or a client project, that's almost always the right amount of complexity: enough to undo a mistake with confidence, not so much you need a merge strategy.