An agent is never finished. You tighten the instructions after a confusing conversation, add a tool for the new booking system, swap the greeting for the summer. Most changes make it better. Now and then one makes it worse, and until now the only way back was to remember what it said before.
From this week every change leaves a version. Agents and MCP servers have a new History tab, under Setup in the editor, and every tool in the Tools library has its own history. Here is what it keeps and how to use it.
What a version holds
A version is everything that shapes how the agent answers and looks:
- The prompt (or, for an MCP server, its instructions) and the behaviour settings.
- Translations: titles, greetings and suggested questions in each language.
- The widget look, the welcome menus, the logo and the cover.
- The feedback form and the guardrails.
- Which tools and knowledge bases are attached, and the videos.
Some things are left out on purpose: price and billing, status and visibility, who has access, verification, the team, channels and the custom domain. Restoring those could cost money, lock people out or break a connection, so a restore never touches them.
Every change, from every place
A version records who made the change and where: the dashboard, the API, MCP or an import. That matters more than it sounds. If an assistant edits your agent through MCP at night, or a script updates it through the API, the change is in History like any other, with a short note of what changed: "Prompt edited", "Tool added: Booking", "Language added: Polish".
Quick saves by the same person merge. Five saves within two minutes while you polish one paragraph show up as one version, so the timeline reads like a list of decisions rather than keystrokes. A save that changes nothing that a version holds, a price change for example, makes no version at all.
Compare, then restore
Open History
The timeline shows every version with who saved it and when, and the live one at the top. Filter to Checkpoints to see only the versions you named.
Open a version
See what that version changed, or compare it with the live one: "If you restore v12, this changes:", area by area: the prompt, settings, languages, tools, knowledge and the rest.
Restore this version
Everything it holds goes back to how it was, for everyone, right away. Tools or knowledge bases deleted since are left out, and the restore tells you which.
Undo, if you need to
A restore is recorded as a new version, so the state you left is still in History, one click away.
Checkpoints for the versions that matter
Before a big change, press Save checkpoint and give the live version a name: "Before Black Friday", "Launch version", "Signed off by legal". Named checkpoints are kept for good and never count against the number of versions your plan keeps, so you can always come back to them, however many changes follow.
Undo right after you save
Not every mistake waits to be found. After each save a small Undo appears; it takes the agent back to how it was just before your change. It only undoes your own recent change, so you never reverse a colleague's work by accident.
Two people, one agent
Version history also fixes an older, quieter problem. If you opened the editor in the morning and a colleague, an API script or a restore changed the agent since, your Save is now stopped with a short message saying who changed it, and a Reload button that brings in their change while keeping your unsaved edits. Two people can no longer overwrite each other without knowing.
Tools have their own history
A tool can be used by several agents, so it keeps its own timeline in the Tools library: name, description, inputs, the instructions for the agent and the action settings. The last 10 versions of each tool are kept. Restoring one shows which agents and MCP servers use it, because the change applies everywhere at once.
Who can do what
Every member of the workspace can read History. Owners and admins can restore versions and name them. How many versions are kept depends on your plan, and the History tab tells you; named checkpoints are always kept. Pair it with answer feedback: when a change makes the 👎 count rise, you know exactly which version to go back to.
Frequently asked questions
Can I restore an earlier version of my AI agent?
Yes. Open the History tab in the agent editor, pick the version, compare it with the live one and press Restore this version. The restore is itself a new version, so you can undo it.
What does a restore not change?
Price and billing, status and visibility, access lists, verification, the team, channels and the custom domain. Restoring those could cost money, lock people out or break a connection, so they are never part of a version.
Are changes made through the API or MCP recorded?
Yes. Changes from the dashboard, the API, MCP and imports all leave a version, marked with where they came from and who made them.
How long are versions kept?
Your plan sets how many versions each agent and MCP server keeps; the History tab shows the number. Named checkpoints are always kept. Each tool keeps its last 10 versions.
Who can restore a version?
Owners and admins of the workspace. Other members can see the history but not restore or name versions.
