A web dashboard for Pi — browse, manage, and chat with your Pi coding agent sessions from any browser.

• Session browser — view all Pi sessions grouped by project, with search, favorites, and active session indicators
• Live chat — send messages, steer the agent, and watch responses stream in real-time via SSE
• Branch navigation — explore conversation branches and switch between them
• Session lifecycle — create, resume, abort, and stop sessions directly from the UI
• Extension UI — handles Pi extension prompts (input, confirm, select) with modal dialogs
• Mobile-friendly — responsive layout with iOS keyboard handling
• Standalone binary — bundle into a single self-contained Bun executable

• SvelteKit + Svelte 5
• Bun runtime & adapter
• Tailwind CSS + DaisyUI
• Marked for markdown rendering

• Bun ≥ 1.0
• Pi installed and available on your PATH (or set PI_BIN)

# Install dependencies
bun install

# Start dev server
bun run dev

Open http://localhost:4020 in your browser.

See Agent Setup § Environment Configuration for the full env var reference.

When PI_AUTH_PASSWORD is set, all routes require authentication. Users are redirected to a login page where they enter the password. A session cookie is issued on success and lasts 30 days.

The password can be supplied as either:

• Plaintext — e.g. PI_AUTH_PASSWORD=my-secret
• Bcrypt hash — e.g. PI_AUTH_PASSWORD='$2b$10$...' (any string starting with $2 is treated as a bcrypt digest)

To generate a bcrypt hash:

bun -e "console.log(await Bun.password.hash('my-secret', { algorithm: 'bcrypt' }))"

Job completion callbacks (/api/jobs/:id/complete) are exempt — they use their own per-job token authentication.

Step-by-step instructions for an AI coding agent to set up the project from scratch.

Verify the following are available on PATH:

bun --version        # Bun ≥ 1.0
gh auth status       # GitHub CLI, authenticated
pi --version         # Pi coding agent (or claude --version for Claude Code)

bun install
bun run check        # typecheck
bun test src/        # unit tests

cp .env.example .env

Edit .env and set values as needed. All variables are optional and have sensible defaults:

Server (standalone/production only — dev server always uses port 4020):

Authentication:

Harness:

Sessions:

Jobs & Worktrees:

Job Skills:

PR Poller:

PR Analysis:

When OPEN_ROUTER_API_KEY is set, each review job runs a two-step analysis before dispatching the reviewer agent: (1) a fast classification of the PR's risk, area, and stack, then (2) generation of tailored review instructions guided by the Code Review Principles — covering SOLID, DRY, naming, error handling, scale, and more. If the analysis model call fails, a rules-based fallback produces instructions from the classification alone.

The analysis model is selected by PR risk level (override with PI_ANALYSIS_MODEL):

Symlink the job-callback extension into Pi's extensions directory:

bash scripts/setup-hooks.sh

This symlinks extensions/job-callback.ts into ~/.pi/agent/extensions/. The extension fires on agent_end to report job results (success/failure) back to pi-remote-web via its callback API.

# Development (port 4020)
bun run dev

# Production
bun run build && bun run preview

# Standalone binary
bun run package && ./dist/pi-dashboard

The PR poller watches GitHub repos for pull requests and automatically dispatches review jobs. Manage monitored repos via the API:

# List monitored repos
curl http://localhost:4020/api/monitored-repos

# Add a repo
curl -X POST http://localhost:4020/api/monitored-repos \
  -H 'Content-Type: application/json' \
  -d '{"owner": "org", "repo": "my-repo", "enabled": true, "assigned_only": false, "manual_only": false}'

Per-repo toggles:

• enabled — whether the poller watches this repo
• assigned_only — only poll PRs assigned to the authenticated GitHub user
• manual_only — skip automatic polling; only process PRs triggered manually

bun run check        # typecheck before committing
bun test src/        # run tests before committing

• Use conventional commits (e.g. feat:, fix:, chore:)
• Use Australian English in user-facing copy
• Work on feature branches; open PRs against main

Build a single portable executable that embeds all client assets:

bun run package
./dist/pi-dashboard

src/
├── lib/
│   ├── components/     # Svelte components (ChatBubble, MessageInput, etc.)
│   ├── server/         # Server-side logic (RPC manager, session scanner, SSE)
│   ├── types.ts        # Shared TypeScript types
│   └── utils.ts        # Utility functions
├── routes/
│   ├── +page.svelte    # Session browser (home)
│   ├── session/[id]/   # Individual session chat view
│   └── api/            # REST + SSE API endpoints
└── app.html            # HTML shell

MIT