pi-app

Desktop app for the pi coding agent: streaming timeline, Git review with hunk staging, session tree, native UI for pi extensions. Windows · macOS · Linux. pi 编程 Agent 桌面客户端

Runssource: GitHubTypeScriptMITcommit c26373f70cdd

TypeScript, MIT licensed. The project labels itself: agentic coding, ai agent, ai coding, ai coding assistant, claude, code review, coding agent and desktop app.

pi-app runs. An Argusic agent installed it in 3 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 Desktop 0.6.0 builds from source, all 1384 unit tests pass, all 275 contract tests pass, typecheck passes, and the Electron app launches on the virtual display.

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.03 (measured)
recorded runs
1
last tested
stars
409
forks
45
open issues
4
watchers
3
size
37 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . 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-app, 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.

  • Node.js 18.19.1 was too old (requires >=22.19.0)1 minute
  • Electron sandbox not usable inside container (chrome-sandbox not owned by root with setuid)1 minute
Install time
3 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm run test:unit: 1384 passed, npm run test:scripts: 275 passed, npm run typecheck passed, electron-vite preview launched successfully on Xvfb display :99 with all IPC handlers and update check logged
Model tokens used
28,141
Exact commit tested
c26373f70cdd
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 run test:scripts` — 275 contract tests passed, 0 fail
- `npm run typecheck` — no errors
**Launch**: `electron-vite preview` started and initialized cleanly on the Xvfb display (`:99`). Th…
tokens used
28,141
All errors were resolved. Here's the final summary:
**Install**: `npm install` succeeded. Required Node.js >= 22.19.0 (env had v18.19.1) → fixed by ins…
**Tests**: All passed.
- `npm run test:unit` — 286 files passed, 1384 tests passed, 6 skipped
- `npm run test:scripts` — 275 contract tests passed, 0 fail
- `npm run typecheck` — no errors
**Launch**: `electron-vite preview` started and initialized cleanly on the Xvfb display (`:99`). Th…

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 3 minutes to install, slower than the median of the 29 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 30 agentic-coding projects Argusic has installed and timed, pi-app was the 18th fastest to reach a running state, and 23 of 30 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.
  • A quick evaluation: it was running 3 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

agentic-codingai-agentai-codingai-coding-assistantclaudecode-reviewcoding-agentdesktop-appdeveloper-toolselectronelectron-appgitguillmpipi-agentpi-coding-agentreacttypescriptwsl

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-app.svg)](https://argusic.com/subject/pi-app)

Questions

Does pi-app run?
Yes. pi-app runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test pi-app?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c26373f70cdd. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test pi-app?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pi-app take to install?
3 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-app need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pi-app?
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-app compare with the alternatives?
Of the 30 agentic-coding projects Argusic has installed and timed, pi-app was the 18th fastest to reach a running state, and 23 of 30 reached one at all.
Where is the evidence for pi-app?
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.

Discussion