pi-extensions

⚠️ Warning: The code in this repo is complete Vibeslop, written by clankers and not reviewed by me. Use at your own risk. I do use all these extensions all the time.

A collection of pi extensions. Each extension lives in its own directory with its own README.

• annotate/ – Plannotator feedback for the latest assistant message
• plan-md/ – Branch-based planning workflow with persisted plan files and Plannotator browser review
• task-subagents/ – Standalone subagents / steer_subagent delegation tools with recursion disabled in spawned child sessions
• diff-review/ – Plannotator browser diff review with feedback sent directly to the agent
• review/ – Interactive review mode with target selection, structured findings capture, and triage
• side/ – Ephemeral floating read-only side chat with summarized and live parent-session context
• answer/ – Interactive Q&A workflow for extracting questions and sending compiled answers
• cache-expiry-warning/ – Above-editor warning when a configured prompt cache may expire between turns
• herdr-integration/ – Herdr blocked-state reporting when Pi requires user input
• mention-skills/ – $skill-name autocomplete with submit-time expansion to SKILL.md paths
• prompt-save/ – Session-wide saved prompt picker with save, restore, copy, and delete shortcuts
• prompt-thinking/ – ^thinking-level overrides and session thinking-level shortcuts
• session-paths/ – Cross-platform session lookup for equivalent macOS and Linux home paths
• openai-params/ – OpenAI settings UI for fast mode, 24-hour cache retention, and verbosity
• fetch-url/ – URL fetch tool with main-content extraction and markdown/html/raw output
• web-search/ – Brave Search web_search tool for single or multi-query result sets
• status/ – Live status widget for model, repo, timing, and PR context
• tool-display/ – Compact built-in tool rendering overrides for read, write, edit, bash, grep, find, and ls

See each extension’s README for setup and usage. Developer notes live in AGENTS.md.

• Keep pi runtime packages in each extension's peerDependencies (@earendil-works/pi-*, typebox where needed). This is what published npm packages rely on.
• Keep the same runtime packages in the workspace root devDependencies so local symlinked extensions resolve the same imports during development.
• Run pnpm run check:peer-runtime before publishing. This verifies that all extension peerDependencies are represented in root devDependencies.
• Run pnpm run check:package-boundaries before publishing. This verifies that packaged runtime source files stay within their package boundaries.
• Use scripts/publish-npmjs.sh --all --only-unpublished to publish only package versions that are not already on npm (--dry-run is supported). Outside dry-run mode, the script checks npm auth first and runs npm login if needed.
• Run pnpm install at the repo root after pulling changes so workspace links and runtime deps are present.