> ## Documentation Index > Fetch the complete documentation index at: https://docs.avocadostudio.dev/llms.txt > Use this file to discover all available pages before exploring further. # Review, undo and versions > Every way back — undo, the History drawer, restoring an earlier version of a page, and restoring a published snapshot — and when each one is the right tool. Nothing in the editor is a one-way door. There are several ways back, and they are genuinely different tools, not several names for the same button. ## The approval gate: before it happens Ordinary edits apply straight away, because undo is one click. **A few kinds of request do not.** The chat stops and shows you the plan first when it would: * delete a page, * change more than one page at once, * remove three or more blocks, or * remove more than half of the blocks on a page. The message lists what is about to happen, with two buttons: **Apply changes** (**Delete page** when a page is going) and **Discard**. Nothing happens until you choose. This is nearly the only place in the editor where you are asked to confirm something, which is deliberate: a confirmation on every action trains everyone to click through confirmations. If you want to see a plan before *any* change, say so: *"show me a plan first"*. The change is applied to your draft and the message offers **Keep** and **Revert**. ## Undo: the last thing **Ctrl+Z** (**Cmd+Z** on a Mac), or the undo button above the composer. **Ctrl+Y** (or **Cmd+Shift+Z**) redoes. Each message in the chat also carries its own **Undo** on the change it produced, which is what you want when you have made three edits and only the second one was wrong. Undo is recorded on the server. It survives a page reload, a browser restart, and coming back tomorrow — it is not a browser-level undo buffer. Undo history is deep but not infinite: **50 steps per page, per direction.** Each page keeps its own stack, so undoing on `/pricing` never disturbs `/about`. ## The History drawer: every step, and any version **Activity** in the top bar opens the **History** drawer beside the preview. It is the full record, newest first, grouped by day. Every step is kept, and you can go back to any of them. ### What each step shows Each row says what the step was, who made it — **You**, **AI chat**, or **Synced from the site** when content came in from the site — and when. Under that, it shows **what changed**: * each changed field as **before → after**, with images as thumbnails, old beside new; * **Page settings** for the SEO title, description, social image and URL; * sections that were **added**, **removed**, or **moved** from one position to another; * **Created this page** or **Deleted this page**. Long steps show the first three fields and a **Show all *n* changes** button. Undo and redo are steps too, and say what they undid: *Undid "Updated Hero heading"*. A step with nothing earlier to compare against says *No earlier state is kept to compare this step with*. ### This page or all pages The drawer opens on **This page**, so the timeline you are reading is the page you are looking at. **All pages** shows every page's steps together, each with its page name. The **Show changes by** menu narrows the list to **People** or **AI chat**. ### Restore this version Every row except the newest has one action: **Restore this version**. It puts the page back exactly as it was right after that step. Hover it and the tooltip names the clock time you are going back to. The newest step is marked **You are here** — that is what the page shows now. Restoring is a step itself, so nothing is lost. It appears at the top of the list as *Restored the version from 14:32*, and undo or a later restore takes you forward again. A restore changes one page: the page that step belongs to. **To drop one change from earlier and keep the rest**, there is no separate tool: restore the step just *before* that change. Be aware that this also takes back every later change on that page, because they were made on top of it. Read the steps above it before you press the button. The History drawer shows the most recent 50 steps, and the site keeps the last **100**. ### Publishes in the list Publishes appear in the History drawer too, marked **Live**, **Deploying…** or **Failed**, with how many pages actually changed (*"3 of 9 pages changed"*) and a **View deploy** link where your host provides one. A failed publish has a **Show details** button with the error. ## Published snapshots: going back after it went live On sites that publish by committing content to a Git repository, each publish is also kept as a **snapshot**. Open the **Sites** page (**View all sites** in the site menu), and press the clock button on a site's card. **Version history** lists each snapshot with its commit, page count, home-page heading and date. **Restore** replaces your *whole draft* — every page — with that snapshot and opens the editor. The live site is not touched until you publish again. Any unpublished edits in your draft are replaced, so publish or note them first. On sites that publish elsewhere, such as a CMS, the list says *No snapshots available yet*. Use the History drawer, or your CMS's own history. ## Which one do I want? | Situation | Use | | - | - | | It just did something wrong | **Undo** (Ctrl+Z) | | The third message of five was wrong | The **Undo** on that message | | I want this page back to how it was this morning | **Restore this version** on that step, in the History drawer | | One change from Tuesday has to go | **Restore this version** on the step before it — later edits to that page go too | | We published something wrong and it is live | Fix or restore it in the draft, then publish again. On Git-backed sites, a snapshot **Restore** gets you a whole earlier draft | | It is about to delete something | Just press **Discard** on the plan | ## Feedback on a bad result Every assistant message carries **Good response** and **Bad response** buttons, and the bad one takes an optional note. That is not a support ticket — it is the record the planner's prompts get tuned against, so a specific note (*"kept rewriting the heading I told it to leave alone"*) is worth more than a rating. ## What to read next Choosing what goes live, and confirming it did. Why the live site looks unchanged, and where your work is held. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.