Revisions

Agent revisions separate the configuration you are editing from the configuration users receive. Saving a draft does not replace the published revision.

Save and test

Agent configuration changes save automatically. Saves during an editing session can update the same working draft rather than creating a history entry for every edit. Once a revision has been used by a Playground turn or published, later edits create a new draft instead of changing that saved configuration.

The Playground runs the latest saved revision, including an unpublished draft. You do not need to publish to test it.

Publish

Choose Publish or Publish changes when the draft is ready. Publishing makes that revision the agent's published configuration; the previously published revision remains in history as superseded.

New turns in the installed assistant resolve the published configuration when they start, including turns in an existing conversation. Publishing does not switch the configuration of a turn already running. A turn waiting for approval resumes with the agent revision it started with.

Publish the agent before using it through an installation that selects it. An unpublished draft is available in the Playground, not as that installation's agent configuration.

Read history and restore

Open the agent's History to see saved revisions, their status, save time, and author. Select a revision to compare it with the saved version it was based on.

Use Restore this revision as a new draft on an earlier revision to copy its configuration into a new draft. Restore does not overwrite the earlier revision or change what users receive. Review or test the restored draft, then publish it to roll back the agent configuration.

Changes outside the agent revision

An agent revision records its configuration, not a frozen copy of everything the agent can access:

• Documentation has its own release process. Releasing a doc within the agent's knowledge scope does not require republishing the agent.
• Skill instructions are published separately. Publishing an update to an already granted skill does not require republishing the agent; changing the agent's skill grants does.
• Action definitions and policies live in the shared action catalog. Updating an existing catalog action can affect agents that already grant it without republishing them. Adding a new grant still requires an agent revision.

Restoring an agent revision restores its configuration, not earlier versions of those shared resources.