Versioning & lifecycle

An agent has a published (live) version that people use, and a draft you edit. This lets you improve an agent, test it, and release it — without disrupting anyone mid-conversation.

The draft → publish flow

Edit

Click Edit agent to put the agent into a draft. Every change you make — runbook, tools, data, settings — applies only to the draft. Users keep using the live version, and a banner reminds you that you're testing your draft.

Test

Chat with the draft to try your changes. Draft conversations are private to you — users never see them, so you can iterate freely.

Publish

When the draft is ready, click Publish and confirm. The draft becomes the new live version and is available to everyone with access. After publishing, any further edits start a fresh private draft — so the cycle repeats safely.

Publishing deletes all of your draft test conversations. Every thread you created while testing the draft is removed on publish — only conversations on the live agent (yours and your users') survive. Save anything you need from a draft thread before you publish.

Swapping connections and MCP servers at publish

If your draft points at test data connections or MCP servers that differ from production, the publish step lets you map each test resource to its production equivalent. The published version then uses the production connections and servers, while your draft keeps using the test ones as you keep iterating.

Version history & rollback

The Version History panel (the clock icon in the agent toolbar) shows your current Draft and every published version, with who published each and when. The live one is badged Live.

• Discard draft throws away the draft and returns the agent to its live version — your safety net if a change isn't working out.
• You can see exactly what changed and when, giving you an audit trail of the agent over time.

For the user-facing side of this, see Versioning.