pi-my-setup

Save your Pi package and global skills setup as one copy-paste restore command. No git clone, no manifest file, no repo checkout.

Move your Pi setup to another machine

On the machine that already has your Pi packages and skills configured:

npx pi-my-setup

or explicitly:

npx pi-my-setup save

The restore command is printed and copied to your clipboard when a supported clipboard command is available. It looks like this:

npx pi-my-setup restore pisetup:v2:eNqV...

On a fresh machine, paste and run that command. pi-my-setup decodes the setup code, shows the package and skill list, opens the checkbox installer, runs pi install <source> for selected packages, and runs grouped npx --yes skills add <repo> -g --yes --full-depth --skill ... commands for selected skills.

Setup codes include shareable Pi package sources from ~/.pi/agent/settings.json, lock-managed global skills from ~/.agents/.skill-lock.json, and git-backed skill repos under ~/.pi/agent/skills. They do not include secrets, npm tokens, API keys, local paths, manifest files, or machine-specific files.

What gets restored

pi-my-setup does not carry over your full Pi settings. It saves and restores:

• shareable Pi package entries — the npm/git packages that Pi can install, typically packages that provide extensions, skills, tools, or providers
• global skills that have installer metadata in ~/.agents/.skill-lock.json
• git-backed skill repos under ~/.pi/agent/skills

It does not copy:

• Pi settings/preferences
• model/provider API keys
• auth tokens or npm credentials
• local-only skills or extensions without installer metadata
• local file paths
• machine-specific config

Packaged Pi skills are restored when they come from a saved npm/git Pi package. Global skills installed by the Skills CLI are restored from their lockfile metadata, and git-backed skill folders under ~/.pi/agent/skills are restored from their origin remote. Skills are grouped by source repo for efficient installs. Standalone local skill folders without .agents/.skill-lock.json metadata or a git origin remote are detected during save and reported as a warning, but they are not included in the setup code.

If a skill or extension is only present as a local file on one machine, install it through the Skills CLI, keep it in a git repo with an origin remote, or package it as an npm/git Pi package before expecting pi-my-setup to restore it elsewhere.

Optional global install

You can also install the tool globally if you do not want to type npx each time:

npm install -g pi-my-setup
pi-my-setup save

Then restore on another machine with the printed command:

pi-my-setup restore pisetup:v2:eNqV...

Commands

npx pi-my-setup                         # print one restore command from Pi packages, Skills CLI lockfile, and git-backed Pi skills
npx pi-my-setup save                    # same as default
npx pi-my-setup restore <setup-code>    # decode and install selected packages and skills
npx pi-my-setup decode <setup-code>     # print packages and skills without installing
npx pi-my-setup --version               # print pi-my-setup version
npx pi-my-setup -v                      # print pi-my-setup version

Options:

--yes, -y      # skip checkbox UI and install every decoded item
--dry-run      # print restore commands without running them
--version, -v  # print pi-my-setup version
--help, -h     # show help