Versions History — Track, Compare and Publish Agent Changes
Written By Anand Raj
Last updated 27 days ago
Every change to your agent is tracked as a version. From the Versions panel in the Agent Builder you can see what is live, what is still a draft, who changed what and when — and compare any two versions side by side before you publish.
Opening Versions
Open your agent in the Agent Builder and click the version badge (for example V2) in the top toolbar. The Versions panel slides in from the right with two sections:
Drafts — work in progress that is not live yet. Each draft shows which version it was created from (e.g. Draft (V5) — From V2).
Published — every release that has gone live. The one currently serving calls is marked Current.
Full version tracking
Nothing is overwritten. Each time you save, your changes live in a draft; each time you publish, a new published version is created. Older published versions stay in the list, so you can always look back at exactly what your agent was doing at any point in time.
Timestamped change log
Every entry in the list shows:
Version number — e.g. V3.
Release name — the name given at publish time (e.g. V3 — New new changes).
Timestamp — the exact date and time it was published.
Author — the user who published it, or System for platform-generated versions such as the initial V1.
Status — Published, Current or Drafts.
Pre-publish issue detection
Before a draft can go live, the system scans your whole workflow and flags anything that looks wrong. If issues are found, the toolbar shows an issues button (e.g. 5 issues) instead of a clean publish state. Click it to see them grouped by node.
Typical checks include:
Missing worksheet — a Note Taking node has no worksheet attached, so the agent doesn't know what fields to capture.
Unused tool — a tool such as create_appointment is selected but never referenced in the prompt.
Lightweight prompt — a prompt is too thin to cover tone, objections and edge cases.
Workflow missing — no fallback path exists, for example when the calendar has no available slots.
Typos — misspellings detected inside a prompt, with the line number.
Each issue comes with a short suggestion so you know how to fix it.
Errors block publishing, warnings don't. If any error is flagged, the Publish button stays disabled until you fix it. Warnings are advisory — you can still publish the draft, but it's worth reviewing them first.
Testing a draft safely
Use Test Workflow to try a draft before it goes live. The test runs against the draft you are editing and does not affect the currently published version — live calls keep using the Current version until you publish.
Named releases and diff views
Click Publish and a panel slides in from the right where you describe the release before it goes live:
Name — the version number (e.g. V5-) is filled in for you; add a short, meaningful title such as "Agent Leena New Release" . This is what shows up in the version list later.
Version Description — an optional longer note explaining what changed and why, so anyone reviewing the history later has the full context.
Show Changes — expand this to review exactly what's being published before you confirm.
Use Cancel to close the panel without publishing — your draft stays exactly as it was. Under Show Changes, changes are presented in two ways:
Semantic Diff — a plain-language summary of what was added, removed or changed, grouped by node or workflow (e.g. Book_Appointment — 1 changed).
JSON Diff — the full line-by-line technical detail, with removed lines in red and added lines in green.
Comparing any two versions
You don't have to be publishing to compare. In the Versions panel, click the three-dot menu on any entry and choose Compare Version. Then pick the two versions you want in the dropdowns — published or draft, in any combination — and switch between Semantic Diff and JSON Diff.
The same menu also lets you:
Create Draft — start a new draft from an existing published version (useful for rolling back or branching off an older release).
Delete Version — remove a draft you no longer need.