Drafts, versions & going live

Every team has two lives: the live version callers are on, and the draft that is free to break. Nothing moves from one to the other until Go live is pressed.

Edits land in a draft

Every change — a Builder chat edit, a tweak in the agent editor — autosaves into the draft within seconds. There is no Save button, and no way to publish by accident: 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 shows where things stand. With a draft open: an amber DRAFT badge, what it is based on, when it last autosaved, chips for what changed — and History, Discard and Go live. With no draft: the clean live state — LIVE · v3, who published it and when.

Going live

Go live opens a confirm showing the version transition and an AI-written summary of what changed, editable before it is saved onto the version. Calls in progress are never interrupted; new calls use the new version the moment it is live. A toast confirms it: v3 is now live — v2 saved to history.

Rolling back

History lists every version, newest first, with its summary, author and changed-field chips; the live row is marked taking calls now. Restore as draft on any other version makes it the new draft to check, test and publish — restoring never touches callers. Restoring over a draft with unsaved edits warns first.

Discarding a draft

Discard throws the draft away and returns to the live version, untouched. If any endpoints were connected to the draft, 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 real callers. One deliberate exception: an endpoint chosen to connect while drafting answers the draft right away — it is marked connected to draft on the graph and stays connected when the team goes live.