v0.29.0Built on Pi Durable →

Pi, on your phone.
And any browser.

Pi Pocket is a self-hosted web app for the Pi coding agent. Start a run from anywhere, share it with the people you work with, and let it keep going when the server restarts.

$ npm install -g pi-pocket
Self-hosted Uses Pi's sign-ins No build step Runs on Android MIT license
The session list on an Android phone. One session is working, one waits for approval, and one is done.
Pi Pocket on an iPhone. Pi has fixed a sign-in redirect loop that Alex asked about. Riley asked it to push the branch, and Lancet Guard waits for someone to allow or deny git push. The line under the message box shows 3 people here and guard on.

Made for phones

What you use most is a thumb's reach away, and back closes what opened last. Push notifications, dictation, and an icon on your home screen.

Built to share

Invite people, or open a session on all your devices. Everyone sees the run as it happens, and can steer it or talk beside it.

Survives restarts

Every step is stored before it shows. Restart the server mid-run, and the work picks up where it stopped.

Multiplayer

Share a session.

Everyone sees the run as it happens, and each message shows who sent it.

  • Presence. See who is here, and who is about to write to Pi.
  • Side chat. Talk beside the run, where Pi does not see it. @mention people, quote a reply, or pass a message on to Pi.
  • Take turns. One person drives; the others ask to. Anyone who can steer can still stop a run.
  • Invites. A link, a QR code, or a short code. Let people steer or only view, in one session or all of them.
The People sheet on an iPhone, over the session. Alex, Sam, and Riley are in the session. In the chat, Alex mentions Riley about the cookie fix, Sam asks whether iOS has the same problem, and Alex answers.
PiP

An assistant for your other sessions.

PiP opens over whatever you are looking at. Ask in plain words, and it hands the work to a session with the tools to do it.

  • Starts work. In a folder, a git worktree, or a GitHub repository, now or on a schedule.
  • Reports back. It follows a run to the end and sums it up in a line, as a push notification when you are away.
  • Watches GitHub. "When CI fails on main, fix it and tell me."
  • Stays in its lane. It changes no files and runs no commands, never allows a call that waits for approval, and never picks a model.

Press Alt+A, tap the orb, or type /pip. Only the owner can open PiP.

PiP open over a session on an Android phone. Riley asked it to start a session in shop-web that adds a regression test, in a worktree. PiP started the session, followed it, and after the report says all 4 tests pass in its worktree and nothing needs Riley there.
Wide screens

Room for everything.

Your sessions, the conversation with each of Pi's edits, and peek tiles that show your other sessions at work. Answer an approval right from its tile.

Pi Pocket on a wide screen. On the left, the list of sessions. In the middle, a session where Pi added a test: its edit is open in the timeline with the diff, followed by npm test with 4 passed. On the right, peek tiles of other sessions: one waits for approval of git push, with Deny and Allow on the tile; another is still working.
Foundation

Built on Pi Durable.

Pi Durable is Earendil's harness for long-running agents. It keeps conversations, model calls, tool calls, and app state together, and commits each step before anything is shown. Pi Pocket keeps all of it in one SQLite file.

  • Runs survive restarts. A tool call that was cut off runs again only if that is safe; otherwise Pi is told it was interrupted.
  • Same view everywhere. Browsers get only committed state, so a device that joins late sees what everyone else sees.
  • Steer or queue. A message sent mid-run joins it or waits for the next one, across restarts too.
Features

All of Pi, and then some.

Pi's tools, models, skills, and prompt templates, with what a browser and a team add.

Ask Pi to change Pi Pocket

There is no build step. Web files reload every open browser, extensions reinstall while the server runs, and running work resumes after a restart. Pi knows where the docs are.

Files and changes

Browse the folder, review every change, and switch branches.

Peek tiles

Other sessions' latest steps, beside the one you are in.

A built-in browser

Pi drives a real Chromium. You watch and click the same page.

Artifacts

HTML, Markdown, and SVG in a sandbox, with every version kept.

Subagents

Helpers in conversations of their own, on one board.

Memory

Lessons Pi keeps across sessions, once the owner approves them.

Plan mode

Pi reads and proposes. Edits wait for someone's yes.

Forks and worktrees

Fork from any reply, retry with another model, work on a branch.

Models you choose

Pi Pocket uses Pi's providers and sign-ins. Pick the model and thinking level for each session. Pi never picks a model for you. See what Pi spent per person and per session, and set limits for either.

Themes

Pocket, Lantern, every Omarchy theme, or your own.

Skills and prompts

Pi's skills and saved prompts, as slash commands.

Extensions

Pi Pocket's own features are extensions. Drop in your own, or find reviewed ones in the hub. Each one starts off until the owner turns it on.

Steer or queue, file mentions, shell commands, dictation, find in session, export, codemode, and more are in the feature tour.

While you are away

Work that starts without you.

A clock, GitHub, or another service can send Pi a message. Each one counts as the work of the person who set it up, with their access and spend limit.

/schedule

Scheduled messages

Later or on repeat. A restart keeps them waiting; none is sent twice.

/until npm test

Done when

Pi keeps going while the check fails, for five checks at most.

/watch

Pull requests

Failed checks, conflicts, and reviews reach Pi until it is merged.

PiP

Repository watches

New issues, failing CI, releases, and @pi mentions start work.

POST /hook/…

Webhooks

Each post becomes a message. GitHub's must carry its signature.

push

Notifications

When Pi finishes or needs you. Deny a call from the notification.

Security

You decide who can make Pi act.

Pi runs commands on your machine as you. Pi Pocket controls who can ask it to, and which calls wait for a person.

  • Lancet Guard. Once you turn it on, it checks every bash, write, and edit call. Risky ones wait for someone to allow or deny them, and the answer survives restarts.
  • Roles. Viewers can read, react, and chat, but cannot send to Pi, approve, or upload.
  • Text from outside is data. Webhooks, GitHub events, and what PiP reads reach Pi marked as data, not instructions.
  • Sandboxes. Artifacts and the built-in browser cannot reach the app or its cookies.
!

Steering means shell access. Invite only people you trust with that. SECURITY.md says what is protected and what is not.

Access

Five ways to connect.

The launcher asks how your devices connect, then shows a sign-in link and a QR code for your phone.

local

This device

127.0.0.1, behind a tunnel of your own.

lan

Local network

Any device on the same network, over plain http.

tailscale

Tailscale

Only devices on your tailnet, encrypted by Tailscale.

tailscale-serve

Tailscale Serve

https on your own tailnet name, with a certificate Tailscale holds and nothing public.

Push notifications and dictation need https, from Cloudflare Tunnel or Tailscale Serve. Pi Pocket also runs on Android: install it in Termux and keep everything on the phone.

Get started

Run it yourself.

  1. Sign in with PiRun pi and use /login, or sign in later from the app.
  2. Start the launcherChoose how your devices connect. Your choice is remembered.
  3. Scan the QR codeYour phone stays signed in for a year. Add it to your home screen.
  4. Pick a modelTap the model chip in the message box, and make it the default.
# Requires Node.js 22.19 or newer
$ npm install -g pi-pocket
$ pi-pocket
# Or try it once: npx pi-pocket
# To change its code: git clone, npm install, npm start
While the launcher runs: q quits, r restarts the server, a changes access, o opens a browser, and s shows the QR code. More in the README.