Agent Studio Version Control

What’s new

Agent Studio now provides Version History and Revert for Agent Studio assets, a new version-control capability that records every publish and makes it simple to inspect or return to a previous known-good state.

Release type: New capability

Product area: Agent Studio

Availability: All customers, all data centers. No configuration required.

🧭 What’s included

Version History tab on Plugins, Conversational Processes, Data Types, Actions (HTTP and Script), Event and Webhook Listeners, and MCP Servers.
Commit messages: the Publish modal accepts an optional message describing the change.
Version chips in the editor header and in the tab strip to show which version is open.
Open any earlier version directly in the editor to inspect its contents.
Publish from an opened earlier version to create a new version based on that content.
One-click revert with a confirmation modal that lists related child artifacts the revert will affect.

🌟 Why this matters

Before this release, publishing an update overwrote the prior asset immediately and teams needed external backups to keep a change history or recover from mistakes. With Version History and Revert:

Developers get an auditable history of publishes (author, timestamp, optional commit message).
Teams can easily inspect previous versions without rebuilding from scratch.
Reverting to a previous version is simple and safe, reducing risk and speeding recovery from bad publishes.

✋ How revert behaves

Revert is additive and non-destructive:

Reverting an asset, for example, currently at V4 back to V3 will create a new version V5 containing V3’s contents. V4 remains in the history and is still viewable.
Nothing is deleted so a revert itself can be reverted later.
The revert confirmation modal lists the child artifacts that will be impacted so you can confirm the downstream scope before proceeding.

⚠️ Known limitations

Revert unavailable for some sub-configurations: plugin utterances, certain Data Type sub-configs, plugin triggering configuration, and slot resolution strategies inside Conversational Processes are versioned and viewable, but cannot be reverted today. Agent Studio surfaces inline flags where these limitations apply. Support for revert on these items is planned as a fast follow.
Drafts are not versioned: Version History applies only to published assets.
Platform updates are recorded: When Moveworks applies schema migrations or other platform changes to an asset, those updates appear as versions attributed to a Moveworks administrator. Version numbers can advance without a developer publish.
No side-by-side diff: To compare two versions, open each one. A diff view is planned for a future release.
No staged testing of drafts: You cannot test an unpublished Conversational Process in a staging mode that prevents immediate replacement of the live asset in this release. Staged testing is planned for a future update.
One-asset revert only: There is no batch revert and no cross-asset activity log in this release.

📌 Notes for developers and admins

Every publish is recorded with an author and timestamp. Consider adding a descriptive commit message when publishing to make history easier to scan.
Because reverts create new versions rather than deleting history, you can always traverse and restore any prior state.
Review the revert confirmation modal carefully — it shows child artifacts that will be affected so you can understand impact before proceeding.

📚 Learn more

Detailed documentation and usage guidance is available in the Agent Studio docs. If you have immediate questions or feedback, please post them in the community forum and our team will respond.

Thanks,

The Agent Studio Team