If it didn't come out right
Mistakes are cheap here. Until you say “yes”, customers don't see anything; and what's already done comes back with one word.
“Undo”
The shortest way back is to say it right in the conversation as soon as you see something wrong:
Undo
No, put it back the way it was
“Undo” applies to your latest change to the agent, whichever of your chats you made it in: you changed the tone in one chat and changed your mind in a new one — say it there. It doesn't take back someone else's change: what a teammate did, or what you did with a button in the panel, is rolled back in the change log below.
The whole last turn comes back together — not “almost everything”, but everything the builder did in response to one message of yours. If it created an action and then immediately added to the character for it, both come back: half of a canceled idea is worse than either of its whole versions.
Small things don't ask for permission precisely because they're easy to take back
The builder changes the tone, name, greeting or knowledge without asking — and tells you right away that it can be undone. The rule is simple: what was done without asking comes back with one word.
What can't be undone
Some changes are physically impossible to reverse, and the platform doesn't promise what can't happen:
- a connected channel — reconnecting issues a new incoming address, and the other messenger would have to be set up again;
- an overwritten key — the old value can't be read, so there's nothing to bring back;
- files in the agent's persistent folder — what the agent rewrote or deleted there during its turn (or you did with a button in the panel) can't be restored: the platform doesn't take snapshots of the folder.
If the last turn included something like this, the builder says so plainly and offers to fix it by hand, instead of pretending it rolled it back.
The log: what has changed at all
You can undo more than just the last thing. The panel on the right has a “What changed — and undo” row: it shows everything the builder did with the agent, as a set per conversation turn — when, who (you or someone on your team) and what exactly.
Each set is rolled back with a button and as a whole, by the same rule: half of a canceled idea is worse than either of its whole versions. That's why the rest of a set's changes are visible right away, without expanding — so you can see what you're agreeing to.
A set that included something irreversible doesn't offer the button and says exactly why: a reconnected channel would get a new address, and there's no way to read the old value of a key.
If you deleted an agent
I accidentally deleted the bot, bring it back
A deleted agent stays in the recovery window for a limited time — the builder shows which ones can still be brought back and until what date. It doesn't ask for confirmation: bringing it back doesn't break anything, while waiting does, because the window is finite.
“Put it back the way it was yesterday”
Undo answers a question about one change. A question about a moment in time is answered by restore points.
Put the agent back the way it was before yesterday's edits
The builder shows a list of points in words — when each was taken and why — and asks which one to go back to. You don't need to remember any numbers.
What it brings back: the agent's character, its flow and its triggers.
What it doesn't bring back: the builder names this separately, together with the question. Agreeing to “bring back everything” and getting only part of it is worse than not restoring at all, so the list of what won't come back is in the question, not in a report afterwards.
Where these points come from
You don't create them. The platform takes a point on its own, before every conversation in which something changes — one per conversation, not one per message in it. The last twenty are kept: that's roughly a month of work on an agent.
If needed, you can ask for a point to be taken now — before doing something big:
Make a restore point, I want to experiment
In reply, the builder names the point's number: that's what you'll use later to ask to go back (“go back to point 7”). It also tells you what the snapshot doesn't cover — worth knowing now, not when you need it.
Change log
Everything done to the agent leaves a trace: a set of changes for each turn, when it happened, who made it, and whether it can still be undone. The log opens from the panel with the “What changed — and undo” row.
It shows the latest changes, not the whole history: older ones stay in the log but don't fit in this list. If you're looking for something old, it's easier to ask the builder in the conversation — or get the full log via the API.
If you change your mind mid-turn
A turn that has already started doesn't stop on the server. If you reload the page or the connection drops, the work still gets finished, and what was done stays.
So after an interrupted turn:
- look at the cards — they show what managed to apply;
- don't repeat the same request — what was done would be repeated too (a second agent would appear, a second email would go out);
- ask only for what's missing, or say “undo”.
If the banner says “nothing was changed”, it's safe to repeat.
Next
- When something breaks — when the problem isn't your changes.