@aquaticcalf/pi-plugins

A pnpm workspace and distributable pi package containing independently loadable plugins.

Plugins

Plugin	Location	Purpose
ClickUp	plugins/clickup/	Command-gated ClickUp API access with CRUD permissions
GitHub	plugins/github/	Settings-style GitHub PR, checks, issue, and repository workflow
Casino Mode	plugins/casino/	Optional refined casino-lounge theme toggled by /casino
HIG	plugins/hig/	Always-loaded calm, readable visual baseline
Prompt loader	plugins/prompts/	Appends repository text prompts to the system prompt
Server	plugins/server/	Runs and manages the persistent pi host daemon
Web Search	plugins/web-search/	Multi-backend HTTP web search plus temporary Brave browser tools
RTK	plugins/rtk/	Rewrites supported bash commands through Rust Token Killer for compact output

More integrations can be added under plugins/<name>/ without changing the collection architecture.

RTK setup

The RTK plugin is included in the package, but the rtk binary is installed separately. On Windows, install the official release and ensure rtk.exe is on PATH. The plugin then rewrites supported bash commands automatically. Use /rtk to toggle rewriting and show its status. The preference persists like Casino Mode.

Try without cloning or permanently installing

This package uses pnpm's catalog: protocol. npm cannot parse that protocol, and pi uses npm by default. Configure pi to use pnpm before running the commands below.

To set this automatically while preserving your other pi settings, run this once:

node -e "const fs=require('fs'),path=require('path'),file=path.join(process.env.HOME||process.env.USERPROFILE,'.pi','agent','settings.json');fs.mkdirSync(path.dirname(file),{recursive:true});const settings=fs.existsSync(file)?JSON.parse(fs.readFileSync(file,'utf8')):{};settings.npmCommand=['pnpm'];fs.writeFileSync(file,JSON.stringify(settings,null,2)+String.fromCharCode(10))"

This adds the following to ~/.pi/agent/settings.json:

{
  "npmCommand": ["pnpm"]
}

Then run the published GitHub package for one pi session:

pi -e git:github.com/aquaticcalf/pi-plugins@master

This uses pi's temporary extension loading. It does not add the package to your pi settings. See each plugin's README for its commands.

Selective plugin loading

The root package discovers plugin entrypoints with ./plugins/*/index.ts and plugin themes with ./plugins/*/themes/*.json. To load only selected plugins from a package installation, use a filtered package entry in pi settings:

{
  "packages": [
    {
      "source": "git:github.com/aquaticcalf/pi-plugins@master",
      "extensions": ["plugins/clickup/index.ts"]
    }
  ]
}

You can also use pi config to enable or disable individual extensions.

Permanent installation

pi install git:github.com/aquaticcalf/pi-plugins@master

From a local checkout:

pnpm install
pi install .

pnpm workspace development

This repository uses pnpm workspaces and a shared catalog for all dependency versions, including Pi SDK packages:

pnpm install
pnpm typecheck

Pi uses npm by default for package operations, so the npmCommand setting above is required for this repository. The packageManager field pins the workspace to pnpm 11.17.0. A new terminal may be needed after installing pnpm so it is on PATH.

Adding a plugin

Create a new workspace package:

plugins/my-plugin/
├── package.json
├── README.md
└── index.ts

Add its entrypoint under plugins/my-plugin/index.ts. The root Pi manifest discovers it automatically, while package filters let users choose which plugins load.