Version & roll back an agent
Publish versions of an agent and restore an earlier one when needed.
Advanced · ~10 min · Prerequisites: a published agent
Building and editing agents is admin-only. Members can run and observe agents, but only admins can create or change them.
What you'll do
Learn how every publish creates a numbered version, how to browse that history, and how to restore an earlier version when a recent change breaks something.
Every publish is a version
Each time you click Publish in the builder at /admin/agents/<slug>/edit, AgentForce snapshots your current draft — instructions, model, tools, identity — into a new numbered version. The previously published version stays live for members until the snapshot is complete.
This means iterating is safe by design: members always see a stable published version while you work on the draft. See Versions & publishing for the full versioning model.
Open Version history
In the builder at /admin/agents/<slug>/edit, click Version history (typically accessible from the top toolbar or the overflow menu). The panel lists every published version with:
- A version number (increments on each publish)
- A timestamp showing when it was published
- A preview of the instructions snapshot for that version
Keep this panel in mind before you publish a significant change — it's your safety net.
Restore an earlier version
To go back to a previous version:
- Open Version history in the builder.
- Find the version you want — scroll down if the list is long.
- Click Restore next to that version. AgentForce loads the snapshot as your current draft (instructions, tools, model, and identity).
- Review the restored draft in the editor and test it in the test panel.
- Click Publish to make the restored version live, or continue editing.
The restore loads a copy — your current draft history is not erased. If the restore isn't right either, you can restore again from a different version.
When to roll back
Roll back when:
- A recent publish caused the agent to give wrong, incomplete, or off-topic answers.
- You enabled a tool that's firing in unintended ways.
- You changed the instructions and the tone or behavior drifted from what members expect.
- A model change produced latency or quality regressions.
If you're not sure which publish introduced the problem, restore one version at a time and test between each restore to narrow it down.
If you want to keep the broken publish for reference, note its version number before restoring — the version list is permanent, so you can always compare the snapshots later.