wtf is pi-share?

pi-share is an extension for the Pi coding agent that lets you export your personal Pi configuration so it can be shared with someone else, along with a small backend service that stores and serves those shared configurations. By default, it packages up files such as your settings, keyboard shortcuts, agent instruction files, extensions, skills, prompts, and themes from your local Pi configuration folder, while leaving out anything related to authentication, session history, trust decisions, backup files, and anything that looks like a secret or an environment file. Once installed as a Pi extension, it adds a set of chat style commands: exporting your configuration under a chosen name, optionally with a password, previewing or importing someone else's shared configuration by its ID, and deleting a share using a delete token you received when you created it. An export made without a password is stored as plain, readable data for the easiest sharing experience, while a password protected export is encrypted on your own machine first, using scrypt and AES-256-GCM, so the backend server only ever stores scrambled data it cannot read. The backend that stores and serves shares is built as a Cloudflare Worker, using Cloudflare R2 for the actual configuration files and Cloudflare D1, a small SQL database, for the metadata about each share. It exposes a simple API for creating, fetching, and deleting a share. Setting it up requires the Bun JavaScript runtime and the Wrangler command line tool, creating an R2 bucket and a D1 database, copying an example configuration file and filling in the new database ID, then running a database migration and deploying the worker. There is also a local development mode that runs the same backend on your own machine for testing before deploying it for real. The project can also be installed directly from a local folder rather than from the npm registry, which is useful while working on it.