Version history

Web pages, email templates, email drafts, documents, blog posts and social posts keep a history of the versions they've been through. If a change isn't what you wanted — yours, a teammate's or the assistant's — you can take it back with Undo, put it back with Redo, or open History to look at any earlier version and go back to it. Nothing is lost along the way: going back saves the earlier version as a new one, so a change that went too far can itself be undone.

This covers web artifacts, email templates and emails while they're still drafts, and documents (Markdown documents only), blog posts and social posts.

What's recorded

You don't save versions yourself. The app records them as you work:

One version per stretch of editing. Edits you make by hand within a few minutes of each other are grouped into one version, so a session of tweaking a headline doesn't leave dozens of near-identical entries.
One version per assistant reply that changed the item. However many small edits the assistant makes while answering a single request, they count as one version, so a single Undo takes back everything it did in that reply.
Publishing closes a version. For a web page, a blog post or a social post, the version you published is kept as its own entry, and edits after it start a new one.
Every undo, redo and restore is a version too. Going back never overwrites anything; it adds a new version that matches the one you went back to.

Each version remembers who made it (you, a teammate, the assistant, or the app itself), when, and a short description of what changed.

Undo and Redo

Open the item and look at the toolbar in its preview panel. Undo, Redo and History sit right after the pencil, separated from the download buttons by a thin divider. They appear on the tab that shows the item's content:

a web page's Preview tab (including pages that have no pencil because they draw themselves with their own script);
an email template's preview;
an email draft's Template tab;
a document's or a blog post's preview;
a social post's network tabs.

Undo takes back the latest change, whoever made it. Redo puts back what Undo took back. Redo lights up only straight after an Undo: any other change — an edit, a message to the assistant, a restore — ends the chain, the way it does in any editor. Undo twice and you can Redo twice.

Hover over either button to see what it will do before you click, for example "Undo the assistant's change · New headline and hero image · 2 min ago". While the change is being applied the button you clicked shows a spinner, and Undo, Redo, Edit and Refresh wait until the new version is back.

A teammate's change

Undoing your own change or the assistant's never asks. If the change Undo would take back was a teammate's, you're asked first ("Undo a teammate's change?"). The confirmation says what they changed and when, and reminds you that their change stays in History, so it can be restored.

While you're editing

Undo and Redo are turned off while the editor is open; hovering them says "Close edit to undo saved versions". The editor has its own undo for typing (Cmd+Z, or Ctrl+Z on Windows), and your stretch of typing becomes one version when it saves, which a single Undo then takes back. History stays available while you edit, but restoring a version waits until you close the editor.

If it changed while you were looking

Undo, Redo and Restore act on the version you're looking at. If someone else — the assistant or a teammate — saved a change in the meantime, nothing is applied. The panel reloads the newest version and tells you:

This changed since you opened it — showing the newest version. Nothing was undone.

Click again if you still want to go back. If an Undo or Redo fails for another reason, the panel says "Undo failed" or "Redo failed"; try again in a moment.

The History list

Click History to open the list of versions over the right side of the panel, newest first and grouped by day (Today, Yesterday, then dates). It shows up to the 50 most recent versions. Click History again, press Esc, click the × or click outside the list to close it.

Opening History always checks for the latest versions. If the assistant or a teammate saved a change since the panel loaded, the panel also reloads to show it, so the version marked Current is the one you see. While the editor is open the panel keeps your text; it catches up when you close the editor.

Every entry says who made the change, when, and what changed:

You, A teammate, Assistant or System (imports, the starting point and automatic changes). Other people show as "A teammate" rather than by name.
A short description from the version's own note. Changes made by hand read "Edited by hand", and Undo, Redo and Restore appear as your own entries ("Undo", "Redo", "Restored version 2").
A Current badge on the version you're looking at, Published on the version that's live (web pages, blog posts and social posts), and Sent on the version that went out (emails).
A name, if someone gave the version one (see below), shown above the description.

The oldest entry is always Original: the item's first saved version. For something the assistant created, that is the first version it made. For an item that already existed before version history was switched on, it is the earliest version on record, and the entry says "The earliest saved version". It replaces the old "Revert to original" link in the editor.

Looking at an older version

Click an entry to see that version, read-only. A web page looks as it does in the Preview tab, because its own script runs, but walled off from the app: it can't see your sign-in or stored data, and its forms are switched off, so nothing is submitted. Emails and email templates show with scripts switched off, and a previewed email draft shows its subject above the body. A social post shows its base text, then one card for each network. If a version's content can't be read any more, the preview says so.

On a narrow panel the version takes over the list, with a back arrow to return to it. On a wide panel, or the full-page view of an artifact, the list stays on the right and the version fills the panel beside it, under a line that says "Viewing the version from …". Either way, Restore this version and Name this version sit at the bottom of the History list, and on a wide panel so does Back to current.

Restoring a version

Click Restore this version. The app asks first ("Restore this version?"), because a restore can jump over several changes. The item goes back to how it was at that moment, and the version you left stays in History. The button isn't shown on the current version.

Restoring doesn't touch a published page: the restored version is a new draft version, and the Published badge stays on the live version until you publish again.

Restore the original works the same way, from the Original entry; its confirmation reads "Go back to the original?". It restores the item's first saved version, for every kind of item, and everything since then, including your edits, stays in History. Like any restore, it's refused while the inline editor is open: close the editor first.

To drop your hand edits since the assistant's last change, use Undo, or open History and restore the assistant's latest version. Restore the original goes all the way back to the start.

Naming a version

Click Name this version, type a name of up to 128 characters, and press Enter (or Save). Esc cancels. The name appears as a tag on that entry, which makes a version you care about easy to find again — "Approved by legal", say.

Read-only items

A sent email and an archived item keep their History so you can look at what went out or what was there, but they can't change: the toolbar shows only History (and the downloads), and there's no Undo, Redo or Restore. The list says "This email was sent, so its versions are view-only. Ask the assistant to start a new draft from any of them." (or "This item is archived, so its versions are view-only.").

Asking the assistant to go back

You can do the same thing in the chat, in your own words, while the item is the one you're working on:

"Undo that."
"Put the old headline back."
"Go back to how it was before you changed the layout."
"Actually, redo it."
"Restore the version from this morning."

The assistant looks at the item's recent versions, restores the one you mean, and tells you what it undid. After an undo, it reminds you that you can ask it to redo the change. When it undoes or redoes something it shows up in History as a change you made, the same as the buttons.

When the assistant asks first

If the choice isn't obvious, the assistant asks before it changes anything, showing the candidate versions with who made them and when. It asks when:

the latest change wasn't the assistant's own — you or a teammate edited the item after it, so "undo" could mean more than one thing;
going back would throw away a teammate's edits;
the request is vague, such as "a few versions back" or "how it was this morning".

Pick the version you want and the assistant restores it. For anything older than the last 10 versions, open History and restore it yourself.

These work the same way, with a few differences:

Archived blog posts and social posts can't be changed, so they can't be taken back to an earlier version either. Their History is view-only.
A social post's version covers every network at once. Restoring brings back the base text and each network's own text together.
On a social post, going back changes what a scheduled post will publish. If the post has scheduled sends waiting, the assistant tells you so when it restores an earlier version. Posts already published on a network don't change, and neither do a post's images, first comment and links — only the text comes back.

Limits

History shows the 50 most recent versions, and the assistant works with the last 10. If you want something older, the assistant will say so rather than guess.
A published page changes only after you publish again. Going back changes the draft. The live page stays exactly as visitors see it until you click Publish (or Publish changes) in the preview panel.
A sent email can't change. Only drafts can be restored. An email that has been sent, or that is scheduled or has failed, can't be taken back to an earlier version — ask the assistant to draft a new one instead.
Archived items can't change. Once a web page, template, blog post or social post is archived, it can't be taken back to an earlier version.
Only Markdown documents have a history. A document saved in another format can't be taken back to an earlier version.
Emails already sent don't change when a template does. A restored template is used for sends from now on.

FAQ

Q: Can I undo something I did by hand, not through the assistant? A: Yes. Click Undo in the preview panel once you've closed the editor, or ask the assistant. Undo takes back the latest saved version, whoever made it.

Q: Undo is greyed out. Why? A: Either the editor is open (close it first), the item is read-only (a sent email, or an archived item), or there's nothing earlier to go back to. Hover over the button to see which.

Q: Redo is greyed out. Why? A: Redo only works straight after an Undo. If you've made a change since — by hand, through the assistant or by restoring a version — there's nothing to redo. Find the version in History instead and restore it.

Q: Did going back delete the version I went back from? A: No. Going back adds a new version that matches the earlier one, and the version you left stays in the list. Redo, or restore it from History, and it comes back.

Q: What happened to "Revert to original"? A: It moved into History. Open History and choose the Original entry at the bottom of the list, then Restore the original. The Original is the item's first saved version (for an item that existed before version history, the earliest version on record), and everything since then stays in History. It no longer means "the assistant's latest version": to drop your own edits since the assistant's last change, use Undo or restore the assistant's latest version from History.

Q: I asked the assistant for an undo, and it asked me a question instead of doing it. Why? A: The assistant only undoes straight away when its own change is the latest one. If you or a teammate edited the item since, or the request could mean several versions, it checks with you so it doesn't throw away work you wanted to keep.

Q: Why did I get "This changed since you opened it"? A: Someone else — the assistant or a teammate — saved a change after you opened the item, so the panel stopped before overwriting it. It now shows the newest version, and nothing was undone. Click Undo again if you still want to.