# Upgrading Producer Pal

When installing a new version of Producer Pal, follow these steps:

## 1. Download New Files

Get the latest version (v{{ $frontmatter.version }}) —
[what's new?](https://github.com/adamjmurray/producer-pal/releases/latest):

- [Producer_Pal.amxd](https://github.com/adamjmurray/producer-pal/releases/latest/download/Producer_Pal.amxd) -
  Max for Live device
- [Producer_Pal.mcpb](https://github.com/adamjmurray/producer-pal/releases/latest/download/Producer_Pal.mcpb) -
  Claude Desktop extension (if applicable)

## 2. Replace the Max Device

Replace `Producer_Pal.amxd` in the location where you originally saved it (e.g.
in your Live User Library). Live projects referencing this location will
automatically use the new version.

**Exception:** If you saved projects with "Collect All and Save" (with device
files included), those have their own copy of Producer Pal. For those projects,
drag the new `.amxd` into Live to replace the old version.

Check the version number in the device UI to confirm you're running the latest
version.

<!-- Version-scoped: remove this warning once nobody is still arriving from a
     pre-2.1.0 device. The tip below it is the permanent text.
     See dev/decisions/0015-project-context-param-rename.md -->

::: warning Upgrading to 2.1.0? Copy your project context first — one time only

**Before you replace the device**, open each Set that has project context you
care about, select the text in the device's Context tab, and copy it somewhere
safe. Paste it back into the new device once it's in place.

Replacing the `.amxd` gives you a fresh, empty device, and no earlier version
wrote a backup to restore from — so anything only stored in the old device is
lost. Version 2.1.0 adds that backup (a `Producer Pal Project Context.md` file
saved in each Live Project folder), which is why **this is the last upgrade that
needs the manual step.**

:::

::: tip From 2.1.0 onward, your project context carries over

Project context is backed up in your Live Project folder and restored the first
time the AI uses a tool on the new device — see
[the one exception](/support/known-issues#recent-project-context-can-be-lost-on-a-device-upgrade-pre-2-1-0-devices)
if you changed it right before a first save.

**Coming from a pre-2.1.0 device?** That one never wrote the backup, so there's
nothing to restore from. Copy your project context out of the old device before
you replace it.

:::

## 3. Update Platform-Specific Files

### For Claude Desktop Users

1. Go to Settings → Extensions
2. Click the `...` menu on the old Producer Pal extension and select "Uninstall"
3. Install the new `Producer_Pal.mcpb` file (see
   [Claude Desktop installation](./claude-desktop))

### For Other Setups

- **Using `npx producer-pal@latest`:** no action needed — the `@latest` makes
  `npx` fetch the current version on every launch.

- **Using plain `npx producer-pal`:** change your MCP config to
  `producer-pal@latest`. Without a version tag, `npx` runs any `producer-pal`
  already installed globally or in your project's `node_modules`, skipping the
  fetch — so the bridge can stay on an old version while the device moves
  forward. That mismatch usually shows up as a misleading error like "cannot
  connect to MCP server". See
  [`npx` is running an old version](/support/troubleshooting#npx-is-running-an-old-version).

## 4. Restart Your AI App

Restart your AI application to ensure it picks up the changes.

## Troubleshooting After Upgrade

If Producer Pal stops working after upgrading:

- **Claude Desktop users:** Make sure you uninstalled the old extension before
  installing the new one
- **All users:** Verify you replaced the `.amxd` device (and the `.mcpb`
  extension if applicable)
- Try deleting and re-adding the Producer Pal device in Ableton Live
- Restart your AI app completely
- Start a fresh conversation

See the [Troubleshooting Guide](/support/troubleshooting) for more help.

## Version History

See the full
[release history](https://github.com/adamjmurray/producer-pal/releases) on
GitHub.