> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.vapi.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.vapi.ai/_mcp/server.

# Versioning with tools

> Publish tool changes, review version history, restore an earlier configuration to the draft, and select the specific tool version that an assistant uses.

## How tool versioning works

[Tools](/tools) follow the [versioning lifecycle](/assistants/versioning). Edit the draft, then publish it to create a version. Published versions do not change. To reuse an earlier configuration, restore it to the draft and publish the draft as the next version.

A tool's versions are independent of an assistant's versions. An assistant can use a specific tool version or the **Latest** version. See [How versioning works with assistants and tools](/assistants/versioning/versioning-with-assistants-and-tools).

The tool header shows the selected version. A draft appears separately when the tool has unpublished changes.

## Publish a new version

Publishing turns your current draft into a new version and makes it the **current** version.

#### Open the tool

Open the [Dashboard](https://dashboard.vapi.ai), select **Tools**, and select the tool you want to update.

#### Edit the tool

Change the tool's configuration. Vapi saves your edits automatically as a draft. The changes do not affect live calls.

#### Review the changes

Select **Publish** to compare the draft with the current published version. In the diff, you can copy individual lines, wrap long lines, move between changes, or copy the complete diff.

#### Name and describe the version

Give the version a name. You can also add a short description so teammates understand what changed and why.

#### Publish

Select **Publish** to create the version and make it current. To publish with the default settings, select **Quick Publish**. To remove the draft changes, select **Discard Changes…**.

## View version history

#### Open the tool

Open the [Dashboard](https://dashboard.vapi.ai), select **Tools**, and select the tool whose history you want to review.

#### Open the version menu

Select the version number in the tool header to see recent versions. The current published version is marked **Current**.

#### Open the full history

Select **View Full History**. Each version includes its version number, name, description, and publication time.

From the version history you can:

* Select **View changes** to compare a version with the previous version
* Select **Export** to download a version as JSON
* Select **Restore** to load a version into the draft

## Restore a previous version

#### Choose a version

Open the version history and select **Restore** for an earlier version.

#### Confirm the restore

Review the confirmation, then select **Restore**. Vapi loads the selected configuration into the editor as a draft and replaces the current draft changes.

#### Publish the restored configuration

Review the draft, then select **Publish** to create the next version and make it current.

> **Warning**
>
> Restoring a version replaces the tool's current draft changes.

Restoring a tool version does not change which version an assistant uses. The assistant continues to use the selected version or **Latest**. See [How versioning works with assistants and tools](/assistants/versioning/versioning-with-assistants-and-tools).

## Next steps

#### [Versioning overview](/assistants/versioning)

Save, publish, and restore versions of your assistants and tools.

#### [Versioning with assistants](/assistants/versioning/versioning-assistants)

Publish, view history, and restore versions of an assistant.

#### [How versioning works with assistants and tools](/assistants/versioning/versioning-with-assistants-and-tools)

Choose the tool versions an assistant uses and learn how restoring an assistant affects them.