Publish
By the end of this page you will have promoted a version of your AI Agent to production.
Prerequisites
- A saved, tested draft version (Versioning & promotion).
- Admin or Developer role.
What publishing does
Publishing promotes the current version to PRODUCTION, making it the live version for all traffic. Any previous production version is replaced.
Publish a version
Save and test first
Make sure the version is saved and behaves correctly in the preview. The Publish button is disabled until the agent has a saved version, and it can’t publish a version that’s already in production.
Click Publish
In the header, click Publish. A dialog titled Publish to Production opens: “This will make this version live for all users.”
Add a changelog (optional)
Optionally describe what changed in this version. If a production version already exists, the dialog notes that publishing will replace the current production version.
Confirm
Click Publish to Production. The version is promoted (it moves to READY and then PRODUCTION), and the header updates. You’ll see a confirmation that the version was published.
Promotion is immediate. The previous production version is replaced. To revert, open the Versions panel, select the previous version, duplicate it into a new version, and publish that.
Common issues
- Publish is disabled — Save your work first, or the current version is already in production. Save, or switch to a draft.
- “No version selected. Please save first.” — Click Save to create a version, then publish.
- Published, but a deployment still serves the old behavior — Publishing sets the production version; a deployment picks up the latest production version. Confirm the agent is added to the deployment. See Deploy.