Yes. pi-pocket runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 2 errors on the way, and recorded the session.

How did Argusic test pi-pocket?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed50991eb9c9. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test pi-pocket?

The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does pi-pocket take to install?

13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does pi-pocket need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing pi-pocket?

2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for pi-pocket?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

pi-pocket

A durable, multiplayer, mobile-first web app for Pi agents, built on Pi Durable

Runssource: GitHub homepageTypeScriptMITcommit ed50991eb9c9

TypeScript, MIT licensed. The project labels itself: ai agent, coding agent, mobile, multiplayer, omarchy, pi, pi durable and pwa.

pi-pocket runs. An Argusic agent installed it in 13 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Pi Pocket installs with Node 22.23.3, passes npm check/lint/format:check and the full test suite (412 passed, 0 failed), and serves on its launcher at 127.0.0.1:8899 with working sign-in (200 app root, 303 on login, 401 on bad token)
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.04 (measured)
recorded runs: 1
last tested: 2026-10-19
stars: 507
forks: 44
open issues: 9
watchers: 2
size: 7 MB
created: 2026-10-04
last push: 2026-10-19

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-19. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing pi-pocket, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Ship node is v18.19.1 but Pi Pocket requires >=22.19 and bin/pi-pocket.js exits on it3 minutes
Port 8787 was already occupied by the host gateway on 127.0.0.1, so the first launch attempt could not bind1 minute

Install time: 13 minutes
Cold machine to finish: 6 minutes
Errors hit and fixed: 2 hit, 2 fixed with no human help
How the result was proved: npm test exited 0, 412 passed / 527; launch: node bin/pi-pocket.js printed a sign-in link, curl http://127.0.0.1:8899/ returned 200, valid login token returned 303 then authed root 200 with title Pi Pocket, bad token returned 401
Model tokens used: 187,897
Exact commit tested: ed50991eb9c9
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- `npm install`: 244 packages, 0 vulnerabilities, no errors.
- `npm run check`, `npm run lint`, `npm run format:check`: all clean.
- `npm test`: 527 tests, 412 passed, 0 failed, 115 skipped (browser tests skip by design because no…
- Launched the real launcher: `node bin/pi-pocket.js --access local --port 8899` printed the sign-i…
- `curl http://127.0.0.1:8899/` → 200 with the Pi Pocket app; valid sign-in token → 303 → cookie → …
exec
/bin/sh -lc "printf 'ARGUSIC_RESULT: %s\\n' '{\"install_succeeded\":true,\"launch_succeeded\":true,…
 succeeded in 0ms:
**Result**
tokens used
187,897
**Result**

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Reached a running state on a clean machine, with the session recorded.
Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.

What did not, or is not known

Took 13 minutes to install, slower than the median of the 41 comparable projects Argusic has measured.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 42 ai-agent projects Argusic has installed and timed, pi-pocket was the 29th fastest to reach a running state, and 24 of 42 reached one at all.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.04	2026-10-19 16:21 UTC

Topics (from GitHub)

ai-agent coding-agent mobile multiplayer omarchy pi pi-durable pwa self-hosted

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/pi-pocket.svg)](https://argusic.com/subject/pi-pocket)

Questions

Does pi-pocket run?: Yes. pi-pocket runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test pi-pocket?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed50991eb9c9. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test pi-pocket?: The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pi-pocket take to install?: 13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does pi-pocket need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pi-pocket?: 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does pi-pocket compare with the alternatives?: Of the 42 ai-agent projects Argusic has installed and timed, pi-pocket was the 29th fastest to reach a running state, and 24 of 42 reached one at all.
Where is the evidence for pi-pocket?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.