For a Chinese version of this document, see README.zh.md.
A collection of Pi coding-agent extensions maintained by brglng.
| Package | Description | Differences from upstream | Upstream |
|---|---|---|---|
| @brglng/pi-permission-system | Centralized, deterministic permission gates over tool, bash, MCP, skill, and special operations for the Pi coding agent. | Adds a fullCommand field to permission results (and the review log) so an authorizer link such as @brglng/pi-auto-review receives the full chained bash command instead of only the matched sub-command. |
Pi Packages · NPM · Repository |
| @brglng/pi-auto-review | A model-backed boundary approval broker that integrates with pi-permission-system as an authorizer-chain link. | Prefers the fullCommand field from @brglng/pi-permission-system so a chained command is reviewed as a whole; type imports and the peer dependency point at the brglng fork. |
Pi Packages · NPM · Repository |
| @brglng/pi-portable-sessions | Renames Pi's per-project session directories to portable, machine-independent names (home prefix → HOME, other roots → ROOT, remainder URL-encoded), with a /portable-sessions command. |
— (original; no upstream) | — |
| @brglng/pi-bailian | Aliyun Bailian Token Plan and Coding Plan provider with configurable workspace IDs and model discovery, using Responses or Chat Completions as appropriate. | — (original; no upstream) | — |
| @brglng/pi-custom-providers | Configurable multi-provider model discovery extension supporting per-model endpoints, API types, and metadata overrides. | — (original; no upstream) | — |
Each package is a standalone npm package and can be published and installed independently:
cd packages/<name>
npm publishTo publish all packages at once from the repository root (requires pnpm):
pnpm install
pnpm run publish:allNew packages may be added over time; when they are not forks of an existing
upstream, list the upstream as — and leave the differences column as —.
Original code in this repository is licensed under the MPL-2.0.
Forked extensions under packages/ follow their respective upstream
licenses, as stated in each package's own LICENSE file.