Optional trusted code

Describe the workflow. Ask your agent to add it.

Core pi-web works without extensions. For more, choose a recommended add-on, adapt a template, or write source you can inspect, reload, and refine.

Available now

A real extension

The workflow appears inside pi-web.

A launch decisions extension open in pi-web beside its source session
A project workflow rendered through pi-web’s real extension contribution API.
View its source

Templates · build your own

Ask → write → reload.

Ask
“Read docs/pi-web-extensions.md. Add a project-local panel for this workflow.”
Write
.pi/web/extensions/my-workflow.ts
Use
/reload

Examples are templates, not an installer: start from a checkout, copy the closest file, inspect and edit it, then use /reload.

Choose the scope

Shared agent behavior or browser UI?

.pi/extensions/*.tsRegular pi extensionTools, commands, prompts, events.
.pi/web/extensions/*.tspi-web extensionPanels, actions, tabs, settings.

Both currently run through pi's extension runtime. Project-local or global source is trusted local code: read it before reloading.

Settings and recovery

Keep the extension observable.

Extensions can contribute settings alongside panels and actions. pi-web surfaces extension, skill, and prompt diagnostics so local source problems are visible; use /reload to refresh pi resources, extensions, skills, prompts, and models after a change.

Supported surfaces

Add only what the workflow needs.

FooterHeader actionArtifact actionGit tabRight panelFABSettings

Harness-neutral add-ons are design direction, not something available extensions can target today.

Working source

Start from an add-on or template. Make it yours.