Skip to content

Upgrading Producer Pal

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

1. Download New Files

Get the latest version (v2.1.0) — what's new?:

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.

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.

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 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)

For Other Setups

  • Using npx producer-pal: npx usually fetches the latest version automatically, so no action is needed. But it can also serve a stale cached copy — or skip fetching entirely if you once ran npm install -g producer-pal (it runs your global copy instead). If Producer Pal stops working after an upgrade — often with a misleading error like "cannot connect to MCP server" — force the latest version:

    bash
    npm install -g producer-pal@latest

    Then restart your AI app. See npx is running an old version for details.

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 for more help.

Version History

See the full release history on GitHub.

Released under the GPL-3.0 License.