About & credits
A personal collection, built for Pi
Section titled “A personal collection, built for Pi”Pi Plugins is maintained by Spencer Boucher. It collects focused changes to the coding session: long-running work, planning, review, context awareness and terminal ergonomics.
This documentation covers the Pi suite at justmytwospence/pi-plugins. It is an independent personal project, not the official Pi documentation. For Pi itself, start at pi.dev.
All 19 components are exposed as selectable entries from one Git package. They can be independently enabled, not independently version-pinned within the suite.
Source and attribution
Section titled “Source and attribution”The suite preserves original repository history and MIT attribution. Component licenses remain with their source.
- Plan mode began as a fork of narumiruna/pi-extensions’ plan-mode package, originally published as
@narumitw/pi-plan-mode. Its planner was subsequently rebuilt around in-process Pi sessions. - Subagent UI adapts the widget, FleetView and conversation viewer from tintinweb/pi-subagents, ported to this component’s RPC children and run records.
- The documentation is built with Astro and Starlight. Search is provided by Pagefind. Self-hosted fonts are DM Sans and IBM Plex Mono, distributed under the SIL Open Font License through Fontsource.
See the suite license, individual packages/<name>/LICENSE files, and initial source provenance.
Related projects
Section titled “Related projects”Some components share implementation or configuration conventions with projects for other harnesses. These are related links, not products installed by this suite, a migration path, or a promise of feature parity:
- opencode-herdr
- opencode-marimo and claude-marimo
- claude-cache-guard, opencode-cache-guard and codex-cache-guard
About the illustrations
Section titled “About the illustrations”The landing-page terminal is a CSS illustration of a possible workflow. It is labeled as an example, not a screenshot or evidence of a measured run. Times, percentages and status text in examples are illustrative.
Documentation boundaries
Section titled “Documentation boundaries”Reference pages are grounded in the repository’s README files, implementation and tests. External provider behavior and upstream terminal APIs can change. Test results establish what a test exercises, not an unrestricted support guarantee.
Found a mismatch? Open an issue with the relevant source path and a minimal reproduction. Do not include credentials or private session content.