Agent StudioDevelopment and Testing

Plugin Management

How to edit, delete, and manage your plugins in Agent Studio.
View as Markdown

Edit a Plugin

You can edit any plugin directly from Agent Studio.

  1. Go to Agent Studio and select Plugins from the left-hand menu.
  2. Select the plugin you want to edit.
  3. Update any fields as needed: triggers, slots, activities, control flow, or conversation process configuration.
  4. Continue through each step until you can Save or Publish the plugin.
  5. Test your plugin to confirm it works as expected.


Editing Execution Logic

The execution logic for a plugin depends on the plugin type. Inside the plugin editor, the Body section shows the linked resource with a direct link to open it.

  • Conversational plugins: Edit the associated Conversation Process.
  • System or ambient agent plugins: Edit the associated Listener &Compound Action.


Editing Production Plugins

If you edit a plugin that is already launched to production, your changes go live immediately once you save. To avoid this, remove the plugin from production first, make your edits, then re-launch. Alternatively, use a sandbox environment.

Delete a Plugin

  1. Go to Agent Studio and select Plugins.
  2. Find the plugin you want to delete.
  3. Click the three-dot menu (⋮) on the right side of the plugin row.
  4. Select Delete.


Note

It may take up to 30 seconds for the plugin list to refresh after deletion.

Launch and Remove from Production

Launch to Production

  1. Open your plugin in Agent Studio.
  2. Use the launch configuration settings to control who can access the plugin.
  3. Launch the plugin to make it available to your selected audience.


Remove from Production

  1. Open the plugin.
  2. Go to launch configuration.
  3. Remove the plugin from production. This stops it from being available to users, but does not delete it.

Plugin Versioning

Agent Studio records a new numbered version every time you publish an asset, along with the author, timestamp, and an optional commit message. You can review earlier versions, open any version in the editor, and revert to a previous known-good state without keeping external backups.

Version History is available for Plugins, Conversational Processes, Data Types, Actions (HTTP and Script), Event and Webhook Listeners, and MCP Servers. Only published assets are versioned; drafts are not.

View the current version

The plugin list shows a version badge next to each plugin’s description, for example V2 · PUBLISHED. The same version chip appears in the editor header and in the tab strip so you always know which version is open.

Plugin list entry showing a V2 PUBLISHED version badge below the plugin description.

View version history

  1. Open the plugin (or asset) in Agent Studio.
  2. Open its Version history.

Each entry lists the version number, its commit message (if one was provided), when it was last edited, and who edited it. The currently published version is labeled PUBLISHED.

When Moveworks applies schema migrations or other platform changes to an asset, those updates also appear as versions attributed to a Moveworks administrator, so version numbers can advance without a developer publish.

Version history panel for a plugin showing Version 2 marked as PUBLISHED and Version 1 below it.

Open a version in the editor

Click the Open in editor icon on any version to view that version’s configuration. There is no side-by-side diff view yet, so to compare two versions, open each one.

You can also Publish from an opened earlier version to create a new version based on that content.

Version history for an HTTP action with the Open in editor button highlighted on Version 8.

Revert to a previous version

  1. In Version history, click the Revert icon on the version you want to restore.
  2. Review the confirmation dialog. It shows the currently published version and the version it will revert to.
  3. Optionally, add a Commit message (up to 500 characters) describing why you are reverting.
  4. Click Confirm.

Revert is additive and non-destructive. For example, reverting an asset from V4 back to V3 creates a new V5 containing V3’s contents. V4 remains in the history, and the revert itself can be reverted later. The confirmation dialog also lists any related child artifacts the revert will affect, so review it carefully before proceeding.

Confirm revert and publish dialog showing Version 2 reverting to Version 1, a warning about Triggering Config, and an optional commit message field.
Some sub-configurations cannot be reverted

Plugin triggering configuration, plugin utterances, certain Data Type sub-configurations, and slot resolution strategies inside Conversational Processes are versioned and viewable but cannot be reverted today. Agent Studio flags these inline. To change them, open the asset in the editor and publish a new version.

Revert applies to one asset at a time; there is no batch revert or cross-asset activity log.

Best practices

  • Add a commit message when you publish or revert so your team can scan the history and understand each version at a glance.
  • Review the revert confirmation dialog to understand which child artifacts will be affected before you confirm.
  • Use a sandbox environment for testing before applying changes to production. Publishing still replaces the live asset immediately, and drafts cannot yet be tested in a staged mode.
  • Export plugins when you need a copy outside Agent Studio, for example to move them between environments (see Plugin Promotion).