keep Pi Coding Agent sessions alive after browser disconnects;
run agents inside real repositories and git worktrees;
supervise multiple sessions in parallel;
switch between laptop, phone, tablet, and desktop;
use a server, workstation, or remote dev box as your agent runtime;
manage projects, workspaces, files, terminals, sessions, and remote machines from one web UI.

Your browser is the control surface. The work stays where it can keep running.

Quick start

Requirements:

Node.js 22 or newer
npm
Pi Coding Agent configured for your user
git and the development tools your agents need

Install and start PI WEB as per-user services:

npm install -g @jmfederico/pi-web
pi-web install
pi-web doctor

Then open:

http://127.0.0.1:8504

Useful commands:

pi-web status
pi-web logs
pi-web restart
pi-web doctor
pi-web version
pi-web uninstall

For more install options, including one-line install, Pi package install, WSL/manual usage, and remote access, see the installation guide.

Common alternatives:

curl -fsSL https://raw.githubusercontent.com/jmfederico/pi-web/main/install.sh | sh

PI WEB is also published as a Pi package:

pi install npm:@jmfederico/pi-web

In Pi, use /pi-web install, /pi-web status, /pi-web logs, /pi-web restart, /pi-web doctor, and /pi-web version.

Core model

PI WEB organizes work like this:

Machine     a local or remote PI WEB runtime endpoint
Project     a folder on that machine
Workspace   a git worktree, or the project folder for non-git projects
Session     a Pi Coding Agent chat running inside a workspace

A typical flow:

Add a project.
Choose a workspace or git worktree.
Start a session.
Let the agent work.
Come back later from any browser.

Remote-first development

PI WEB is designed for remote AI-driven development.

Instead of tying agent work to your laptop session, run PI WEB on a machine that stays available: a server, desktop, cloud VM, home lab machine, or remote dev box.

Use a private network, SSH tunnel, trusted reverse proxy, or federated PI WEB machine setup when accessing it remotely.

Machines and fleets

PI WEB can register other PI WEB runtimes as remote machines. One browser-facing PI WEB instance can proxy projects, files, git state, sessions, terminals, and activity from trusted remote machines.

Plugins

PI WEB supports trusted local browser-side plugins that can add actions, workspace panels, and workspace metadata.

Configuration

Global config lives at:

$PI_WEB_CONFIG
~/.config/pi-web/config.json

Project-local PI WEB config lives at:

<project>/.pi-web/config.json

Common configuration includes host/port, path access, uploads, plugins, shortcuts, and session daemon options.

Development

Clone the repository and run:

npm install
npm run dev

Open the Vite URL, usually:

http://localhost:8505

For the split development setup:

npm run dev:sessiond
npm run dev:web
npm run dev:client

Or install the split development setup as native per-user services from the checkout:

pi-web install --dev

pi-web install --dev writes the session daemon plus a UI development service using the native user-service backend. pi-web uninstall removes both production and development service files; no uninstall flags are needed.

dev:web also watches bundled plugin TypeScript and rebuilds the browser-loaded plugin JavaScript under dist/pi-web-plugins/. You can restart dev:web or dev:client without stopping active Pi sessions.

For a production-style run from a checkout:

npm run build
npm run start:sessiond
PI_WEB_PORT=8504 npm start

Validate changes with:

npm run verify

Security model

PI WEB assumes trusted users, trusted repositories, and trusted server paths.

It is not a sandbox, permission system, or multi-tenant platform. Do not expose it directly to the public internet without a trusted network, firewall, VPN, SSH tunnel, or authenticated reverse proxy.

README.md

PI WEB

Why PI WEB?