Packages
Pi packages bundle extensions, skills, prompt templates, and themes for distribution via npm or git.
Installation
By default, installs go to global settings. Use -l for project-level (.pi/settings.json).
Temporary testing:
Management:
Package Sources
npm
Format: npm:@scope/pkg@1.2.3. Versioned specs prevent updates. Global installs use -g, project installs go to .pi/npm/.
Git
Formats: git:github.com/user/repo@v1, HTTPS, SSH, git://. Cloned to ~/.pi/agent/git/<host>/<path> (global) or .pi/git/<host>/<path> (project).
Local Paths
Reference disk files directly. No copying.
Creating Packages
Paths support glob patterns and !exclusions. Include pi-package keyword for gallery visibility.
Gallery metadata:
video: MP4image: PNG, JPEG, GIF, WebP
Auto-Discovery
Without explicit manifest:
extensions/→.tsand.jsfilesskills/→SKILL.mdfolders and top-level.mdfilesprompts/→.mdfilesthemes/→.jsonfiles
Dependencies
Runtime deps in dependencies. Core peer deps with "*" range, not bundled.
Filtering
- Omit keys → load all
[]→ load nothing!pattern→ exclude+path→ force-include-path→ force-exclude
Scope & Deduplication
Project settings take precedence over global. Identity matching by package name (npm), repo URL (git), or absolute path (local).
Pi packages run with full system access. Extensions execute arbitrary code, and skills can instruct the model to perform any action.