Versions

A version is a numbered record of an agent's whole setup at one moment: its persona, its per-channel personas, its knowledge and its tools. The Versions tab in the agent studio lets you publish a new version, read every version you have published, compare any two, and roll back.

Who can do this: workspace owners and admins.

What a version is, and what it is not #

Customers are always served the agent's saved settings. A version does not hold changes back until you publish. Saving on the Persona tab, flipping a tool switch or attaching a knowledge base is live from the next message, whether or not you publish. See When your changes reach customers.

What publishing gives you:

• A record. Each version keeps exactly what the agent was set to, who published it and when, so you can see what was live on a given day.
• A point to come back to. You can compare against any version and roll the agent back to it.
• The first deployment. An agent must be published once before it can be deployed to any channel.

A version records:

A version never changes once it is written. To change anything you publish another one.

Publish a version #

You can publish from the Overview tab (Publish first version or Publish new version) or from Versions (Publish, Publish new version, or Review & publish on the Unpublished changes card). All of them open the same dialog.

Publishing something you already published #

If the agent's setup matches an earlier version exactly, no duplicate is written. The dialog is titled Make Version 2 current and says This is exactly Version 2. Publishing makes it current again; no new version is written. After publishing, the toast reads This matches Version 2, so that version is live again.

If nothing differs from the current version, the dialog says Nothing has changed since Version 4. and Publish is disabled.

When knowledge content has refreshed but nothing you typed has changed, the dialog says No visible changes. Knowledge content has been refreshed since the last version. Publishing then records the new content revisions.

Unpublished changes #

When you have saved anything since the current version, an Unpublished changes card sits at the top of the Versions tab. It reads Saved edits since Version 4. They're already live, but not yet recorded as a version.

• Open the card to see the changes, in the same layout as the version history.
• Review & publish opens the publish dialog.
• Discard puts the agent back to exactly the current version. The dialog is titled Discard unpublished changes? and confirms with Discard changes. Because your saved edits are live, discarding also changes what customers get, straight away.

Read the version history #

Versions are listed newest first, like a commit log. Each row shows:

• the heading, or Untitled version
• Current on the version the agent is on, and Rollback of v2 on a version a rollback created
• the version number (v4), who published it, and when
• the first seven characters of its configuration hash. Two versions with the same hash have identical setups.
• how much it changed from the version before it, as added and removed lines plus a count of changed settings, or First version
• Roll back, on versions you can roll back to

Open a row to see Changes from Version 3 to Version 4.

How changes are shown #

Only what changed is shown. A Show 3 unchanged settings link (the number varies) reveals the rest of a section.

Compare any two versions #

Choose Compare at the top of the tab. It appears once there are at least two versions.

Pick a base on the left and a version to compare on the right. Unpublished draft is available on either side when you have unpublished changes, so you can answer "what is different between Version 2 and what customers get today?". The panel shows how many sections changed. If you pick the same version twice it says Pick two different versions to compare., and two identical versions read These two are identical.

Roll back to an earlier version #

Rollback is how you undo a change that went wrong.

What happens:

• That version's instructions, persona, per-channel personas, settings, tools and knowledge are copied back onto the agent and published as a new version. History only moves forward: rolling back to Version 2 from Version 4 writes Version 5, marked Rollback of v2. You can roll forward again the same way.
• It takes effect on every channel straight away, and it replaces any unpublished edits.
• Deployments keep serving the agent. You do not need to redeploy.
• The toast reads Rolled back. Version 5 is live, restored from Version 2.

Limits:

• A knowledge base deleted since that version cannot come back. It is skipped and the console warns 1 knowledge base was deleted since then and couldn’t be restored.
• If that version required knowledge and none of its knowledge bases are left ready, the rollback is refused before anything changes: Version 1 answers from knowledge that is no longer available. Attach a ready knowledge base instead.
• Rolling back to the version that is already live, with nothing unpublished, is refused with Version 4 is already live. The console hides Roll back in that case.
• A rollback restores the agent. It does not change a deployment's own settings, such as a phone number's greeting or voice. Those are edited on the deployment. See Deployments.

Troubleshooting #

Where to go next #