Extensions · optional trusted code
Choose a recommended add-on for a richer setup, use the source as a template, or inspect experimental work separately.
Recommended add-ons
These optional extensions cover broadly useful workflows. They are not core pi-web and are not installed automatically; inspect the source, copy the file from a checkout, then reload.
Keep a small machine-global planner beside every session without automatically adding its contents to model context.
Keep a machine-global planner beside every session.
mkdir -p .pi/web/extensions && cp examples/pi-web-extensions/notepad.ts .pi/web/extensions/
/reload“Adapt the notepad example to track project decisions. Keep automatic model context off.”
Bring pull requests and issues into the Git surface and attach selected repository context to the composer.
Browse repository work and attach selected context.
Requires an authenticated gh CLI and a GitHub remote.
mkdir -p .pi/web/extensions && cp examples/pi-web-extensions/github-repo-panel.ts .pi/web/extensions/
/reload“Adapt the GitHub tab to show open reviews assigned to me.”
Generate a terse handoff from the current session through a header action when a model is configured.
Generate a terse handoff from the current session.
mkdir -p .pi/web/extensions && cp examples/pi-web-extensions/recap.ts .pi/web/extensions/
/reload“Turn recap into three bullets: done, open, next.”
Inspect artifact metadata and produce a correctly escaped Markdown link directly from the preview action.
Show artifact metadata and a ready-to-copy Markdown link.
mkdir -p .pi/web/extensions && cp examples/pi-web-extensions/artifact-reference.ts .pi/web/extensions/
/reload“Adapt this action to include an artifact reference in a project handoff.”
Keep branch and working-tree state below the composer, refreshed through the extension invalidation surface.
Show branch and working-tree state below the composer.
mkdir -p .pi/web/extensions && cp examples/pi-web-extensions/git-footer.ts .pi/web/extensions/
/reload“Emphasize untracked files and hide clean-state text.”
Templates · build your own
Choose a panel, action, tab, footer, or setting example. Copy it from a repository checkout and run /reload.
Read the trusted TypeScript, change the workflow for your project, and keep only the permissions and surfaces it needs.
Build-your-own workflow →The extension documentation is the canonical reference when none of the templates is close enough.
Read the extension API ↗Experimental · opt-in
This source has additional setup and a wider behavioral boundary. Treat it as something to evaluate, not a recommended default.
Spawned workers remain ordinary, visible pi-web sessions with their relationship to the coordinator. This extension is not a recommended default and does not work from the TypeScript file alone.
Spawn and monitor ordinary worker sessions.
Experimental · opt-in. Requires the companion skill and configured model categories.
mkdir -p .pi/web/extensions && cp examples/pi-web-extensions/session-orchestrator.ts .pi/web/extensions/
/reload“Review the orchestrator and companion skill before proposing a research category.”
Session orchestration also needs its companion skill ↗ and configured model categories.
Trusted code
Extensions run locally through pi and may access files, invoke commands, affect agent behavior, or render trusted HTML. Delete the copied file and run /reload to remove one.
Need a different workflow?