Editor & AI
Accept, reject or undo an operation
Every change to a post goes through a named operation, visible in the history and reversible. Depending on where you are, you decide before — “Accept,” “Apply” — or after, with “Undo.”
On this page5
Nothing changes a post quietly. Every change — yours as much as the AI’s — is an operation: it has a name, it lands in the session history, it can be undone. That is the editor’s underlying rule, and it explains why the buttons are not the same everywhere.
Three moments to decide
Before: “Accept” or “Reject”
AI actions on a single field — reworking a slide title, a caption, an image description, a post’s text — suggest first. The change appears as a before/after, word by word: what goes away is struck through, what arrives is underlined. Two buttons: “Accept” (⌘ ↵) and “Reject.” Nothing has moved yet. This pattern exists in both editors.
Before: “Apply” or “Reject”
The text editor’s assistant works the same way, at the scale of the whole post: “Ask for a rewrite: the assistant suggests, you approve.” The suggestion shows a before/after per post, and “Apply” takes it in one block.
After: “Undo”
The slides editor’s assistant, on the other hand, applies right away. In exchange, every reply carries its own “Undo” — “Undo 3 changes” when there are several — which puts the document back exactly as it was.
What an operation tells you
Every operation comes with a plain sentence, the same one in the assistant thread and in the history: “Slide 3 · title and text,” “Slide 5 · moved to position 2,” “Caption updated,” “Palette updated,” “Post added to the thread,” “Text rewritten.” The ones that come from the AI are prefixed “AI: …” and are spotted at a glance.
The session history
The toolbar keeps the two universal buttons: “Undo” and “Redo,” or ⌘ Z and ⌘ ⇧ Z on the keyboard. Next to them, a “Session history” menu lists every entry, yours and the AI’s, and “Go back to before…” returns the document to any point.
What doesn’t undo the same way
- An image generation in progress is not undone: it is stopped. The button is called “Stop.” Once the image lands, it becomes a history entry like any other.
- Image versions are kept alongside, each with its recipe: “Use” goes back to an earlier version without touching the history, and a retouch creates a new version without erasing the old one. See image versions, comparing and retouching.
- Post versions are another thing again: “Saved versions” holds complete states you named yourself, independent of step-by-step undo. Thirty days after a post is published, only its “Published” version remains, as it went out.
What’s next
You now know who decides, and when. What is left is the most visible part: generate a consistent image series. When the assistant is the one starting them, images are in fact the only action that asks for your go-ahead first.
Was this article helpful?
Thanks, noted.