Versions
Every time you save changes to a flow, Anter records a new version. Versions let you track how an agent has changed over time, promote a revised configuration to live traffic, and roll back to a known-good state if something goes wrong.
Viewing version history
Click Versions in the graph toolbar to open the version panel. Each version is listed with:
| Field | What it shows |
|---|---|
| Version number | A sequential integer starting at 1 — higher means newer |
| Status | Active (currently live), Draft (saved but not promoted), or Archived (superseded) |
| Label | An optional short name you can attach to a version for reference |
| Change note | An optional description of what changed in this version |
| Timestamps | When the version was created and when it was promoted to live |
How versioning works
When you edit and save a flow, the changes are recorded as a new draft version. The currently live configuration — what callers and the Playground are using — remains unchanged until you explicitly promote a version.
This means you can iterate on a flow and test it in the Playground without affecting production traffic. When you're satisfied, promote the draft to make it live.
The agent ID never changes across versions. Callers that reference this agent by ID continue to work — they automatically use the newly promoted version without any update to their integration.
Promoting a version
Find the version you want to make live and click Promote. A confirmation prompt appears:
Promote v[n] to live? The agent's ID stays the same — connected clients keep working and switch to v[n] automatically.
Confirm to proceed. The canvas refreshes to reflect the newly active version and the previous live version moves to Archived.
Rolling back
If a promoted version causes problems, find an earlier version in the list and click Rollback. This promotes the older version back to Active using the same mechanism as a normal promotion — the agent ID stays the same and callers switch immediately.
Add change notes before promoting
Before promoting a version, add a short change note describing what you changed and why. Version lists without notes are hard to read after a few iterations, especially when you need to roll back quickly.
Archived versions
When a version is superseded by a newer promotion, it becomes Archived. Archived versions are read-only — they can be promoted back to live via rollback, but cannot be edited. They remain in the version history indefinitely.