SnapCode now installs as a Claude Code plugin — there is no repository to clone, no Docker container to run, and no GitHub or AWS account required. If you set up SnapCode the earlier way (cloning the SnapCode repository and running the setup script, with the tooling running in Docker), this page walks you through moving to the new plugin.

Step 1: Save your work

With the earlier setup, pipelines and files you created (.slp, .py, expression libraries, and exported projects) might still reside inside the cloned SnapCode folder. Copy them to a folder outside the SnapCode folder before you remove it.

macOS / Linux:

mkdir -p ~/snapcode-work
cp -R ~/path/to/SnapCode/<your-pipelines-and-files> ~/snapcode-work/

Windows (PowerShell):

New-Item -ItemType Directory -Force "$env:USERPROFILE\snapcode-work"
Copy-Item -Recurse "C:\path\to\SnapCode\<your-pipelines-and-files>" "$env:USERPROFILE\snapcode-work\"

Step 2: Remove the old setup

Work through the following items and run only those that apply to how you installed SnapCode. The first two items are the ones most likely to conflict with the new plugin, do not skip them if they apply.

If you enabled SnapCode from any directory (the global option)

The earlier setup included a command to undo the global option. Run it from inside your cloned SnapCode folder:

macOS / Linux:

./install.sh global remove

Windows (PowerShell):

.\install.cmd global remove

This removes the SnapCode skills, the slpy command shortcut, and the associated MCP connections it had registered. If you did not use the global option, skip this and use the following two checks.

Remove the old SnapCode MCP connection

The old setup registered an MCP connection named snaplogic. The plugin adds its own (plugin:snapcode:snaplogic). They do not share a name, but keeping both is redundant and confusing. Remove the old one:

claude mcp list
claude mcp remove snaplogic

If the list also shows pygen or snaplogic-platform, remove those too:

claude mcp remove pygen
claude mcp remove snaplogic-platform

Remove the old slpy command

The earlier setup placed an slpy command on PATH that can shadow the plugin's version. Remove it:

macOS / Linux:

rm ~/.local/bin/slpy

Windows (PowerShell):

Remove-Item "$env:USERPROFILE\.local\bin\slpy*"

Remove the Docker image

The earlier setup ran the tooling from a Docker image. Remove it manually:

docker rmi ghcr.io/snap-developers/sl-procode:latest
docker logout ghcr.io

Delete the cloned folder (optional)

Once your work is safely copied out (Step 1), you can delete the old SnapCode folder to reclaim disk space.

macOS / Linux:

rm -rf ~/path/to/SnapCode

Windows (PowerShell):

Remove-Item -Recurse -Force "C:\path\to\SnapCode"

Step 3: Install the new SnapCode

You are ready to install the plugin. Follow the steps in Install SnapCode. It walks you through the prerequisites, setting your credentials, and installing the plugin with two commands.

Once installed, open your saved pipelines from ~/snapcode-work (or wherever you copied them in Step 1) and continue working from any directory.