Docs / Your first automation
What saving actually does
Saving does not make anything live. Here is what each kind of save does, and what it takes to reach your users.
Two buttons
At the top of the agent page you will see one of two buttons.
- Save as version when your changes affect how the agent behaves: the prompt fields, the model, the reply language, the name, the script, the resources it can use, or its schedules.
- Save when they do not, for example availability or the description. These take effect as soon as you press it.
Save as version writes a numbered version and changes nothing for your users. The bar then reads "Saved as version N. Make it active", with a link through to Versions & Availability. Your agent carries on answering on whatever version was already active until you activate the new one. See Agent versions for how to do that and how to go back.
We keep the words activate, apply and publish out of the save button on purpose, because saving no longer makes anything live.
Finding your unsaved work
An Unsaved changes marker, with a purple dot, sits in the bar at the top of the agent page whichever tab you are on. A matching purple dot appears on each tab that has unsaved work, so you can see where your changes are before you save them as one version.

Scripts, functions and widgets
These do not all behave the same way, and the difference catches people out.
| What you changed | Does it keep its own versions? | What makes it live |
|---|---|---|
| A script | No. A script belongs to one agent and is saved as part of that agent's versions | Save the agent as a version, then activate that version |
| A function | Yes, with its own Publish step | Publish it. Every agent that uses it picks it up straight away |
| A widget | Yes, with its own Publish step | Publish it. Every agent that uses it picks it up straight away |
| A connection | No. An operation is enabled or it is not | Immediately, for everything using it |
An agent's version records which functions and widgets it uses, not which version of each. So publishing a new version of a function changes behavior for every agent that calls it, including agents you were not thinking about, and going back to an older agent version does not undo it. Before you publish a function, check which agents use it in Monitor, then Topology.
Things to be aware of
A reply already under way finishes on the version it started with. Everyone moves onto the newly active version from their next message.
Connections have no version history at all. Revoking an operation takes effect immediately for everything using it, including a conversation already running. That is what makes it the emergency lever, and it is also why there is no undo beyond enabling it again.