Pi Coding Agent web UI

# The web UI for Pi Coding Agent sessions that keep working.

PI WEB keeps Pi Coding Agent sessions running in real server-side workspaces, even after your browser leaves, and gives you a fast web UI to supervise, redirect, and review work from any device.

Local development made sense when humans drove every keystroke. Agentic development works better when the environment is persistent, remote, and always available.

Install in minutes Read the docs
Persistent sessions survive browser disconnects
Parallel projects, worktrees, and agents
Yours runs on your machine or server
agent-hub.local

    $ pi-web status
    ✓ session daemon running
    ✓ web server listening on 127.0.0.1:8504

    $ open http://127.0.0.1:8504
    # laptop, phone, tablet — same live sessions

    $ pi-web doctor
    ✓ login shell can find node >= 22
    ✓ native service shell can find pi
    ✓ ready for persistent agent work

Workspaces, sessions, transcripts, files — one Pi web UI on every screen. Bring your own repositories.
Desktop: chat beside workspace file preview.
Tablet: the same session from a wider touch screen.
Mobile: the chat stays readable on the go.

The mental shift

## Developer tools were built for a world that no longer exists.

Editors and terminals assume the work lives with you, on your device, inside your session. AI agents break that assumption: their work should persist, continue, and evolve independently of your laptop.

PI WEB makes persistence first-class. Sessions live outside the browser, agents keep working, and every device becomes a control surface for supervising, redirecting, and reviewing progress.

Persistence should not be something you bolt on after the fact.

The work should not disappear the moment your session ends.

You do not carry the work. You guide it.

Remote AI-driven development

## Your laptop is a window, not the workstation.

Local-only development can become the blocker: one device owns the tools, terminals, build cache, editor, and agent runtime. PI WEB moves the working environment to a machine that stays on, so agents can keep making progress while every browser becomes a control surface.

▣

### The workstation becomes remote

Keep repositories, dependencies, secrets, build caches, and long-running agent sessions on the machine designed to run them.

⇄

### Any browser can supervise the work

Your device is replaceable. The sessions are not. Move between laptop, phone, tablet, and desktop without moving the development environment. Under the hood, PI WEB coordinates the running sessions, files, terminals, and remote machines like a browser-based control plane.

↯

### Agents become persistent workers

Start work, leave, return later, review progress, and keep multiple streams running in parallel from one stable environment.

Read the remote-first philosophy

Why it feels different

## Not another tab. A persistent place for agent work.

↻

### Come back later

Active sessions live in a long-running daemon, not in your browser tab. Close the lid, reconnect from a phone, and continue supervising the same work.

⌘

### Use real workspaces

Add projects once, discover git worktrees automatically, and start agents where the code actually lives.

### Keep control

Watch transcript history, status, shell activity, context usage, and costs while redirecting the agent in realtime.

Quick install

## Run PI WEB as user services.

1. Install the package globally with npm.
2. Run the installer to create native per-user services.
3. Open the local URL, or tunnel it from a remote machine.

Complete installation guide Troubleshooting FAQ
User service install

    $ npm install -g @jmfederico/pi-web
    $ pi-web install
    $ pi-web doctor
    $ pi-web version
    # Open http://127.0.0.1:8504

### WSL and containers?

Use `pi-web install` where a supported per-user service manager is available. WSL works with the installer when systemd is enabled; otherwise use the manual run path.

Read compatibility notes →

### Local UI plugins?

Ask AI agents to add trusted local UI plugins from `~/.pi-web/plugins` without rebuilding or restarting the session daemon.

Build a plugin →

### Node or tools not found?

Services run login shells. If tools work in your interactive terminal but not in PI WEB, fix PATH in your login shell startup files and run the doctor command.

Fix PATH issues →