Drafts and publishing

By default, every change you save to an agent reaches all of its channels at once. Turn on versioning to work in a draft instead: your users keep talking to the published version until you publish the draft, and every release is kept so you can go back to it.

Versioning is set per agent. Agents that never turn it on behave exactly as before.

Turn on versioning

Open the agent. A panel at the top of the form shows Changes go live immediately. Select Turn on versioning.

The configuration running at that moment becomes version 1, so you always have a starting point to return to. From then on, Update Agent saves to the draft.

You need the agents.publish permission to turn versioning on or off, publish, approve, and restore. Editing the draft only needs agents.edit. See Users and roles.

What the draft holds

The draft covers the agent’s behaviour:

System prompt
Model settings
Harness and initial memory
Knowledge bases, tools, predefined tools, MCP servers, sub-agents and skills
Voice model and language

Everything else, such as the name, description and channel credentials, applies as soon as you save, with or without versioning. Rolling back last week’s prompt never rolls back a bot token you rotated yesterday.

There is one version for all channels. You can’t publish a change to web chat only.

Changes made by the Agent Builder are not staged: they apply to the live agent directly, even with versioning on.

Publish a draft

Edit the agent and select Update Agent. The panel changes to Unpublished changes and lists what differs from the live version.
Select Review changes to see a line-by-line comparison of the draft against what is live.
Optionally, evaluate the draft. Under Evaluate this draft against, pick a dataset and select Run. The agent is not modified. See Evaluations.
Optionally, describe the change in What changed, in your words (optional). The note is kept in the version history.
Select Publish. The draft goes live on every channel as a new version.

To throw the draft away instead, select the trash icon next to Publish. The agent returns to what is live.

What an evaluation of a draft covers

A draft evaluation tests the draft’s system prompt and model settings. Tools, knowledge and harness come from the live agent. If your draft also changes those, the confirmation names the changes the run does not reflect.

Publishing policy

Two optional rules sit at the bottom of the panel.

Setting	What it does
Someone else has to approve a publish	Publish becomes Request review. The draft goes live only when another person with `agents.publish` approves it.
Refuse to publish below … % on its last evaluation	Publishing is refused when the agent’s most recent evaluation scored below this pass rate. Leave it empty for no bar.

The panel always shows the Last evaluation result next to the publish button, whether or not you set a bar.

Reviews

When approval is required, a request shows Waiting for review with its note and time.

A reviewer selects Approve and publish or Reject. Rejecting leaves the draft untouched.
You cannot approve your own request.
Approving publishes exactly what was reviewed, even if the draft changed after the request was made.
A new request replaces the open one. Select Withdraw to cancel a request.

History and rollback

Select History to see every published version with its date, its evaluation score, and its note. The version your users are getting is marked live.

To go back, select Restore on an earlier version. It goes live immediately as a new version at the top of the history, so the record of what happened is never rewritten.

Restoring skips both the approval step and the pass-rate bar. A bad release is live, and retreating from it should not wait.

Turn versioning off

Select Turn versioning off. Any pending draft is published first, and from then on saved changes go live immediately again.