> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/agent-studio/development-and-testing/managing-plugins/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# Plugin Management

# 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.

![](https://files.readme.io/8cc15d86f58b36ba60bab4f8bf36385aaf5a72b86251d4e0247c20cd2ee00c37-CleanShot_2026-02-06_at_16.13.24.png)

\


> **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**.

![](https://files.readme.io/84ae8f13fab21affc65cca1746c10bf521329c4c8a7bd04a376a497e7ad0d893-CleanShot_2026-02-06_at_16.15.09.png)

\


> **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**.

![](https://files.readme.io/1f7ad36b4b948dd8c17e2939b93e348317a2b99d73930ad89a2208c39811e725-CleanShot_2026-02-06_at_16.17.38.png)

\


> **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](/agent-studio/access-control/end-user-access-control/launch-configuration) to control who can access the plugin.
3. Launch the plugin to make it available to your selected audience.

![](https://files.readme.io/e2ac3e28387c633f39c4e01162e228ba0f5474aad262771ba695bdcc9bbd2885-CleanShot_2026-02-06_at_16.18.38.png)

\


## 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. Each version includes the author, timestamp, and an optional commit message. Use version history to review an earlier configuration or restore it as a new published version.

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.

Watch this walkthrough to publish an HTTP action, inspect its history, and restore an earlier version. The video includes burned-in captions.

## Publish a new version

1. Open the asset in the editor and make your changes.
2. Click **Publish**.
3. Optionally, add a **Commit message** that describes the change, such as "Remove the search query parameter."
4. Click **Publish** in the dialog.

The version number increases, and the editor shows the new version as **PUBLISHED**. Publishing updates the live asset immediately.

## 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.](/_fern-img/9e01a4835a83e26a01883962fd7e9c50872726be270123d38a490c9100254aed.webp)

## 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.](/_fern-img/8d9a0cc99fb19873e3f904e2e21e03f8217384b857b74a6305729a55225e7e12.webp)

## 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.

To restore the configuration you are viewing, click **Revert** in the editor and review the confirmation dialog.

![Version history for an HTTP action with the Open in editor button highlighted on Version 8.](/_fern-img/a50739757ef4aed18c6fcc69a3dc5015c3e6de21cf20ab256fa5ed68d1331e48.webp)

## 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. Check the current and target versions, affected child assets, and warnings about dependent assets that the revert can break.
3. Optionally, add a **Commit message** (up to 500 characters) describing why you are reverting.
4. Click **Confirm**.

Reverting creates a new published version and keeps the existing history. In the video, V7 removes a search query parameter from an HTTP action. Reverting to V6 creates V8 with the parameter restored. V7 remains in the history.

After the revert, check that the new version is labeled **PUBLISHED** in version history. Open it in the editor to confirm that it contains the configuration you restored.

![Confirm revert and publish dialog showing Version 2 reverting to Version 1, a warning about Triggering Config, and an optional commit message field.](/_fern-img/9bef7e054c34b574571c893a3942fe778b0a10b4ef5324f8179926e6098940b3.webp)

> **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](/agent-studio/development-and-testing/managing-plugins/plugin-promotion)).

## Docs

- [Plugin Promotion](https://docs.moveworks.com/agent-studio/development-and-testing/managing-plugins/plugin-promotion.md): Export & import your plugins across instances to move it from a development sandbox to production.