pi-web

English | 한국어 | 简体中文 | 日本語 | Español | Português (BR) | Français | Русский | Deutsch

Desktop

Tablet	Mobile

Installation

Install the latest GitHub release binary:

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

The installer and pi-web update install the default trusted plugins when no local plugins are installed: toast notifications, file browser, Git viewer, sidebar, chat composer, Discord notifications, and Telegram notifications. Set PI_WEB_INSTALL_DEFAULT_PLUGINS=never to skip them or always to reinstall them.

Update the installed binary:

pi-web update

Run after installation:

pi-web
# Listens on 0.0.0.0:8732. Open http://127.0.0.1:8732

pi-web --port 9999
# Open http://127.0.0.1:9999

Introduction

A web UI for viewing and controlling the local pi coding agent in your browser. It bundles an Astro-based frontend and a Go backend into a single executable, so you can run the workspace/session UI in a local browser without configuring a separate server.

Features

• Workspace management: Open local folders, switch recent workspaces, delete saved workspaces, and clone Git repositories before opening them.
• Session UI: Browse workspace sessions, create/rename/delete sessions, resume previous conversations, and stream prompts/responses in real time.
• Prompt controls: Send prompts with multiple attachments, keep per-session drafts, cancel or steer active runs, and answer pi fallback choice prompts inline.
• Transcript rendering: Render markdown, syntax-highlighted code, tool output, streamed design decks, and long transcripts with virtualization.
• File browsing and editing: Browse the workspace file tree with Material Icon Theme icons, search files, preview supported formats, create/rename/delete/upload files, edit text files, and save changes from the UI.
• Git insight: View workspace Git status, file decorations, commit history, and individual commit details.
• Local command execution: Run shell commands in the selected workspace and inspect command history/results.
• Settings and auth: Manage project/global pi settings, API keys, OAuth login for Claude/Codex/Copilot subscriptions, runtime model/thinking settings, and quota/status checks.
• Voice and notifications: Read responses aloud, use browser or local Whisper speech transcription, and configure Discord/Telegram completion notifications.
• Internationalized UI: Switch the browser UI across English, Korean, Chinese, Japanese, Spanish, Portuguese, French, Russian, and German.
• AG-UI bridge: Expose session runs through an AG-UI-compatible SSE endpoint for client integrations.
• Plugins (in development): Load trusted local/GitHub JavaScript plugins that can add UI panels, call pi-web APIs, and optionally delegate plugin-specific work to a local backend script.
• Single executable: Distribute the Astro static build embedded in a Go binary with built-in update support.

Plugins (in development)

Plugins are experimental and intended for trusted local code. The API can still change before it is treated as stable.

Install plugins from Settings → Plugins with either a local folder path or a GitHub owner/repo value. A plugin folder must contain a plugin.json manifest and an entry JavaScript module.

{
  "id": "hello-panel",
  "name": "Hello Panel",
  "version": "0.1.0",
  "entry": "index.js",
  "backend": "backend.js"
}

entry is required. backend is optional. Both paths must stay inside the plugin folder.

export function activate(context) {
  const panel = document.createElement("section");
  panel.dataset.pluginPanel = context.plugin.id;
  panel.textContent = `Hello from ${context.plugin.name}`;
  context.app.querySelector("[data-plugin-sidebar]")?.append(panel);

  return () => {
    panel.remove();
  };
}

The entry module may export activate(context) or default(context). Returning a function, or an object with deactivate()/dispose(), lets pi-web clean up the plugin during reload, disable, or uninstall. A module-level deactivate(context) export is also supported.

The plugin context includes:

• context.app: the <pi-app> element.
• context.plugin: the parsed manifest.
• context.rxjs: the RxJS namespace provided by pi-web core.
• context.api.get(path) / context.api.post(path, body): call pi-web HTTP APIs.
• context.backend(method, { workspaceId, data }): call the optional backend script. workspaceId is optional; data becomes the backend stdin JSON.

See Plugin development for the full plugin API and core RxJS usage guide.

Optional backend scripts are executed locally on demand. JavaScript backends run with Node; Go backends are built and cached automatically. The script receives method and workspaceRoot arguments, reads the data JSON from stdin, and must print valid JSON to stdout.

const [, , method, workspaceRoot] = process.argv;
let input = "";
process.stdin.on("data", (chunk) => {
  input += chunk;
});
process.stdin.on("end", () => {
  console.log(JSON.stringify({ method, workspaceRoot, received: JSON.parse(input || "{}") }));
});