pi-lazy-setup
v3.2.0
Published
Initialize the Pi agent environment from a curated snapshot
Readme
pi-setup
Initialize the Pi agent environment from a curated snapshot.
npx pi-lazy-setupWhat it does
- Deploys configs — overwrites
~/.pi/agentfrom bundledconfigs/pi/(binary install is out of scope:pimust already be on PATH). - Deploys the
/pi-setupextension — copiesconfigs/pi/extensions/pi-setup.jsinto~/.pi/agent/extensions/so Pi auto-discovers it on the next start. - Deploys reference docs — copies into
~/.pi/agent/pi-setup/.
Then, inside Pi, run /pi-setup: it interactively installs packages (pi install <source>), skills (npx skills add, https://skills.sh/), and CLI tools (officecli: skill file from https://officecli.ai/SKILL.md + binary via curl -fsSL https://d.officecli.ai/install.sh | bash). Every item is confirmed individually, and already-installed items are skipped. Pattern follows the /rpiv-setup command of @juicesharp/rpiv-pi.
The candidate lists (packages, skills, CLI tools) live as snapshot data inside the extension file itself.
Flags
| Flag | Description |
| --- | --- |
| [agents...] | pi. Omit to run directly. |
| --dry-run | Preview planned actions, touch nothing. |
| --backup | Tar the existing Pi home before overwrite. |
Snapshot Philosophy
This is a snapshot, not a generic installer. Configs ship exactly as the author uses them — personal proxies, extension lists, etc. No templating.
Scope
Pi (https://github.com/mariozechner/pi-coding-agent). The CLI installs nothing: it only deploys the declaration file (mcp.json) and config files (settings.json, models.json, AGENTS.md, prompts/, extensions/pi-setup.js). MCP server binaries are not installed either. Everything interactive (packages, skills, CLI tools) happens via /pi-setup inside Pi.
For skill management, see @kkmila/isc.
Development
npm install # required for local development
node bin/pi-setup.mjs --dry-run # preview
node bin/pi-setup.mjs # real run
npm test # process-seam testsReleasing
Create a GitHub Release to trigger npm publish:
npm version <major|minor|patch>
git push
gh release create v1.2.0 --generate-notesThe workflow runs tests (continue-on-error: true) then npm publish. Requires NPM_TOKEN secret.
License
MIT
