Skip to main content
Agents is in private beta, so things may change. If you hit a problem, tell us via Support & feedback.
Editing an Agent never changes what’s running. Your changes are saved as a draft, and your Agent carries on with the published version until you click Publish. The buttons sit in the bar above every Build page, so they follow you between Instructions, Integrations, Triggers, and the rest.
Version switcher listing v6 as published alongside earlier versions

What do Save and Publish do?

The bar always tells you where you are: unsaved changes, saving, a draft that isn’t published yet, an older version you’ve opened, or a save that didn’t work. Press Cmd + S / Ctrl + S to save.
Drafts don’t save themselves. Nothing is kept until you press Save, so a half-finished idea is never left for a teammate to find.
On a phone, Publish keeps its button and Save and Discard move into the menu.

How do I go back to an earlier version?

1

Open the version list

Click the version name in the bar.
2

Pick a version

Choose the one you want. It opens in the editor so you can read it first.
3

Publish it

Click Publish to make it live.
Opening a version doesn’t make it live. Going back is the same Save and Publish as any other change, so nothing happens on a single click.
Opening a version replaces whatever’s in the editor, saved or not. Publish or discard what you’re working on first. Hercules warns you when there’s something to lose.

What’s saved in a version?

Everything that makes the Agent what it is: its instructions, model, integrations and which of their tools it can use, skills, subagents, and issue access. These go into your draft, and you’ll see them in the version history. Everything else saves the moment you change it, and doesn’t create a version: triggers, channels, guardrails, run limits, description, tags, and starter prompts.
Going back to an old version doesn’t undo those. You get its instructions and tools back, and your triggers, channels, and guardrails stay exactly as they are today. Change those back yourself.

Additional FAQ

Yes. The version history shows each version next to the one before it, so you can read exactly what changed in the instructions and see a summary line for everything else.
A saved draft isn’t a version. The next Save or Publish writes over it. If it matters, publish it.
A run finishes with the version it started on. Publishing only affects runs that start afterwards.
Yes, that’s what a baseline is for. An evaluation lets you pick which version answers, so you can run the same questions against two versions and compare them.