Agent Versioning
Every agent is versioned. Each time you publish, ScaleAI saves a snapshot of your agent's full setup as a version. You can keep editing without fear, revisit exactly what a caller experienced on an older call, and reuse any past version when you need to.
How Versioning Works
Each agent moves between two states:
| State | What it means |
|---|---|
| Draft | A working copy. Your edits are saved here automatically. Drafts are never used for live calls. |
| Published | A saved snapshot with a version number (e.g. v3). One published version is the current version — the one that handles live calls. |
The flow is simple:
- Edit — when you edit the current version, ScaleAI makes a copy (a new draft) and saves your changes there. The current version stays untouched and keeps handling calls.
- Publish — clicking Publish saves the draft as a new version and makes it current. New calls use this version from now on.
- Repeat — your next edit starts a fresh draft from the latest current version, and the cycle continues.
Versions are only created when you actually change something — switching fields without editing won't create empty drafts. Only one draft can exist per agent at a time.
Choosing a Version
The agent details page shows the version you're viewing (e.g. v3 · current) in a dropdown next to the agent name. Open it to:
- Browse every version — labelled
v{n} · draft,v{n} · current, or justv{n}for older versions. - Search by version number, status, or agent ID.
- Switch versions — selecting one opens it in the details page. Older versions open in read-only mode (a badge in the header tells you this).
The agent list also shows each agent's current version. Call logs record the agent name and version that handled each call — so you always know which setup a caller experienced.
Working with Older Versions
Older published versions are read-only: fields, tabs, and tools are locked so history is never accidentally changed. Instead, you can:
- Create from this — the button that replaces Publish on an older version. It creates a new current version from the selected version's setup. If a draft is pending, you'll be asked to confirm — the draft will be deleted and replaced by the new version.
- Share — share links can only be created for the current version.
Creating a new version from an older one deletes any in-progress draft. Publish or review your draft first if it has work you want to keep.
Autosave & Publishing Recap
- All tabs autosave into the draft after a short pause (see Agent Configuration).
- Publish requires an agent name and prompt; the welcome message must be within its length limit.
- After publishing, the autosave indicator returns to idle and further edits fork the next draft automatically.
Versioning in the API
You can also manage versions through the API:
| Endpoint | Purpose |
|---|---|
GET /api/v1/workspaces/{workspace_id}/projects/{project_id}/agents/{agent_id}/versions | List all versions of an agent. |
POST /api/v1/workspaces/{workspace_id}/projects/{project_id}/agents/{agent_id}/versions/{version}/restore | Create a new current version from a specific version. |
See the API Reference for request/response details.
Next Steps
- Agent Configuration: the tabs that make up a version's setup.
- Agent Behaviour: the prompt and welcome message that get versioned.
- Test your agent: validate a draft before publishing it.
- Call Logs: see which version handled each call.