Every team has two lives: the live version your callers are on, and the draft you're free to break. Nothing moves from one to the other until you press Go live.
Edits land in a draft
Every change — a Builder chat edit, a tweak in the agent editor — autosaves into the draft within seconds. There's no Save button and nothing to remember; equally, there's no way to accidentally publish, because publishing is always the explicit Go live press. Versions cover the whole team: going live publishes all its agents together.
The version bar
A sticky bar above the canvas always tells you where you stand. With a draft open it shows an amber DRAFT badge, what it's based on, when it last autosaved, how many edits it holds, and chips for what changed — plus History, Discard and Go live. With no draft it shows the clean live state — LIVE · v3, who published it and when — and a reminder that new edits will autosave as a fresh draft.
Going live
Go live opens a confirm showing the version transition and an AI-written summary of what changed, which you can edit before it's saved onto the version — future-you will thank you for a clear one. Calls in progress are never interrupted; new calls use the new version the moment it's live, and a toast confirms it: v3 is now live — v2 saved to history.
Rolling back
History lists every version, newest first, each with its summary, author and changed-field chips; the live row is marked taking calls now. Every other version has Restore as draft — restoring never touches your callers, it just makes that version the new draft for you to check, test and publish. Restoring over a draft with unsaved edits warns you first, because those edits will be lost.
When you troubleshoot an older call, the Builder tells you which version actually answered it and whether the team has changed since — so you know if the problem you're chasing may already be fixed.
Discarding a draft
Discard throws the draft away and returns you to the live version, untouched. If you connected any endpoints to the draft while working, the confirm lists them under will be disconnected — discarding hangs them up.
Numbers, drafts and real callers
Numbers route to the live version, so drafts never answer your real callers. There is one deliberate exception: an endpoint you choose to connect while drafting answers the draft right away — it's marked connected to draft on the graph and stays connected when you go live. Existing deployments always keep answering live until then.
Test buttons always talk to the draft while one exists. That's the workflow in one line: edit freely, test the draft, go live when it sounds right.