PI WEB has shipped its plugin architecture, opening the browser interface to third-party workspace panels that communicate with pi.dev agents over the decentralized messaging fabric. The first plugin to ship with the new system is the VReader feed reader, which renders an RSS management panel directly inside the PI WEB workspace.
Plugin lifecycle
PI WEB plugins are declared through a piWeb.plugins field in the package’s package.json. Each plugin registers a custom HTML element — <vreader-panel> in VReader’s case — along with lifecycle hooks for mount, unmount, and message routing.
When PI WEB starts, it scans ~/.pi-web/plugins/ for registered plugins, loads their JavaScript bundles, and inserts matching panels into the workspace shell. The plugin communicates with its paired pi.dev extension via the same A2A protocol used for agent-to-agent messaging.
Built on the agent mesh
“This is the payoff of the A2A architecture,” explained the engineering team. “The same wire protocol that lets agents talk to each other also lets browser plugins talk to agent extensions. There’s no separate API layer, no REST bridge, no WebSocket reimplementation. It’s decentralized messaging end to end.”
The VReader plugin demonstrates the pattern: when a user clicks “Refresh” in the workspace panel, the plugin sends an A2A message to apps.a2a.vreader.refresh, which the VReader extension picks up, executes the feed fetch, and returns results over the same channel.
Getting started
Plugin authors can follow the VReader package as a reference implementation. The PI WEB documentation at pi-web.dev covers the plugin registration format, the message routing API, and the custom element lifecycle.