Versions covers how an agent's configuration is saved, published, viewed, and restored over time — every publish creates a new, permanent snapshot you can come back to.
Overview
An agent (or team) keeps a version history. Each time you publish, you create a new version — a deployable snapshot of the whole configuration. The version list lives in a Version History side panel you open from the agent; you can browse past versions, view any one read-only, and restore an earlier one. The agent's header shows the published version and when it was published, for example V3 published 2 hours ago.
What Exactly Goes Into a Version Snapshot
Publishing copies your working configuration into a frozen, numbered snapshot — versions count up from V1. The snapshot isn't just the agent's own settings: everything the agent owns is captured together at the same version — its topics, tools/actions, tasks, guardrails, agent-level knowledge wiring, and settings. If you removed a piece since the last publish, the new version drops it too, so each version is a faithful picture of the whole agent at that moment. Later edits never touch existing snapshots — whatever runs a published version keeps running it until you publish again.
How to Tell Whether Your Latest Edits Are Published
The agent's header shows the current published version and when it was published, for example V3 published 2 hours ago. Edits you make after that aren't live yet. If you've edited since the last publish, publish again to make those edits live.
How to Publish a Version
Use the Publish control on the agent. A short form opens with two fields:
Field | Description |
|---|---|
Tag this version | An optional label. Defaults to the next version number (like V3), must start with a letter, and allows letters, numbers, hyphens, and underscores (no spaces or other symbols). An invalid tag shows "Invalid format, please follow the guidelines." |
Version notes | "Describe the changes in this version." |
For agents, the form has one more option: Deploy this agent on Copilot (or Deploy the new version on Copilot once published before), checked by default. Leaving it on publishes the version and points the agent's Copilot deployment at it in one step — creating the Copilot deployment if the agent doesn't have one yet. The success message then offers Start Conversation to jump straight into Copilot with this agent.
Confirm to publish. Publishing is what makes your latest changes live and adds the version to the history.
Note: Simple agents don't have a separate Publish step. Clicking Save publishes a new version and makes it live on Copilot. The tag and notes fields apply to Advanced agents and teams.
Viewing or Comparing a Past Version
Open the Version History panel and click a version to view it. Each entry shows the version number (like V3), its tag, the version note, and {time} by {user}; the version you're viewing is highlighted. Viewing a version opens it read-only — a banner reads Viewing V{n} … deployed on {time} — so you can inspect exactly what that version's configuration looked like across the editor's sections. The live observability views (sessions, traces) are hidden in this mode because they only apply to the running agent, and the Skills section doesn't appear on a version snapshot; Capabilities does appear, read-only (its toggles show that version's choices but can't be flipped). Click another entry to switch versions while keeping the same section open.
Rolling Back to an Earlier Version
While viewing a past version, use Restore. On success it confirms the agent was restored and returns you to the live agent, now set to that version's configuration. Restoring copies that snapshot — the agent plus everything it owned in that version — back into your working configuration; it doesn't itself publish anything. Your restored setup shows as unpublished changes until you publish, at which point it becomes a new version (history is never rewritten).
Note: Restore never overwrites version history — the earlier snapshot is copied forward, not reinstated in place, so rolling back and publishing again always adds a new version number.
What the Publish Status Indicator Means
The agent's header shows its publish state at a glance. Before the first publish, it shows Last updated {time} ago. After that, it shows the current version and its tag, for example V3 published 2 hours ago. If you've edited since the last publish, publish again to make those edits live.