PiDeck
PiDeck 是一个开源的桌面工作台,用于在本地项目目录中统一管理 PI | DSH | ACP Agent 会话,并支持导入 Codex、Claude 本地会话以便统一浏览和恢复。支持多项目工作区、会话历史、Git 集成、内置终端、模型配置和插件管理,基于 Electron 构建。
Runssource: GitHubhomepageTypeScriptMITcommit 4105d98e8230
TypeScript, MIT licensed. The project labels itself: acp, agent, ai assistant, ai coding agent, claude code, codex, coding agent and desktop app.
PiDeck runs. An Argusic agent installed it in 12 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PiDeck v0.7.7 builds from source, TypeScript typechecks, and launches as an Electron desktop app with Electron 43.4.0 on Node 22.19.0. npm install produces 1583 packages, npm run build creates renderer and main process artifacts in out/, and tests pass. Only missing dependency is the external pi CLI binary for full Agent functionality.
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
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 / npm 9.2.0 below project requirement (npm ^11.6.2)4 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm run build exited 0 producing out/ artifacts; node --test passed 64 tests across 9 test files; npm run typecheck passed; Electron v43.4.0 app launched with working UI (pi CLI missing expected)
- Model tokens used
- 127,400
- Exact commit tested
- 4105d98e8230
- 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.
1. **Node.js too old** — v18.19.1 / npm 9.2.0 didn't meet the project's `npm ^11.6.2` requirement. … **What worked:** | Step | Status | |---|---| | `npm install` | 1583 packages installed successfully | | `npm run make-icon` | Generated all icon formats | | `npm run build` | Full production build succeeded (renderer + main + preload) | | Electron binary | Electron 43.4.0 downloaded and runs (`--version` → v43.4.0) | | App launch | Electron window started, displayed PiDeck UI (pi CLI not found is expected — that's … | TypeScript check | `tsc --noEmit` passed with zero errors | | Tests (64 across multiple files) | All passed — markdown, afterPack cleanup, docs images, extensi… **Build artifacts:** `out/main/index.js` (3 MB), `out/preload/index.js` (126 KB), `out/renderer/ind…
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 1 error 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 140 comparable projects Argusic has measured.
Of the 141 agent projects Argusic has installed and timed, PiDeck was the 96th fastest to reach a running state, and 94 of 141 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
Topics (from GitHub)
acpagentai-assistantai-coding-agentclaude-codecodexcoding-agentdesktop-apppipi-agentpi-deckpi-desktoppideckpidesktopsession-management
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pideck)Questions
- Does PiDeck run?
- Yes. PiDeck runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test PiDeck?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4105d98e8230. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test PiDeck?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does PiDeck take to install?
- 12 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 PiDeck need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing PiDeck?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does PiDeck compare with the alternatives?
- Of the 141 agent projects Argusic has installed and timed, PiDeck was the 96th fastest to reach a running state, and 94 of 141 reached one at all.
- Where is the evidence for PiDeck?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.