PiBot
Open-source, local-first AI agent team for your desktop: multi-agent group chats, computer use, browser, MCP, routines and approvals. macOS, Windows, Linux + Android. Built on pi.
Runs with mockssource: GitHubTypeScriptApache-2.0commit c923b02d8f74
TypeScript, Apache-2.0 licensed. The project labels itself: agent, ai agent, ai agents, ai assistant, android, automation, chatgpt and coding agent.
PiBot runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, project builds (electron-vite), all 3311 unit tests pass, Electron desktop app launches and reaches renderer-connected state, type-check passes for all project references, CLI entry point works.
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 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- unzip system binary not available — zip test failed with ENOENT3 minutes
- Node.js version mismatch — system has v18.19.1 but project requires v26.11.11 minute
- pnpm 12 not installed — system npm lacks pnpm0.5 minutes
- Install time
- 18 minutes
- Cold machine to finish
- 47 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm test: 3311 tests passed (25 files); pnpm --filter @pibot/desktop build: electron-vite build succeeded; electron app launched: full startup lifecycle observed; node apps/cli/bin/pibot.mjs --help: CLI usage shown
- Model tokens used
- 325,442
- Exact commit tested
- c923b02d8f74
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
],
'test_depth': 'tier2_mock',
'notes': 'All 3311 Vitest tests pass (25 test files). Electron app builds and launches successf…
'verified_how': 'pnpm test: 3311 tests passed (25 files); pnpm --filter @pibot/desktop build: e…
'final_state': 'Dependencies installed, project builds (electron-vite), all 3311 unit tests pas…
}
print(json.dumps(result))
\" 2>&1" in /work/repo
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 18.0, "errors": [{"msg": "…
tokens used
325,442Replay 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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 18 minutes to install, slower than the median of the 140 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 141 agent projects Argusic has installed and timed, PiBot was the 120th fastest to reach a running state, and 94 of 141 reached one at all.
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 with mocks | 92.00 | 0.18 |
Topics (from GitHub)
agentai-agentai-agentsai-assistantandroidautomationchatgptcoding-agentcomputer-usedesktop-appelectronllmlocal-firstmcpmulti-agentollamaopenaiprivacyself-hostedtypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pibot)Questions
- Does PiBot run?
- PiBot runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test PiBot?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c923b02d8f74. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test PiBot?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does PiBot take to install?
- 18 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 PiBot need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing PiBot?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does PiBot compare with the alternatives?
- Of the 141 agent projects Argusic has installed and timed, PiBot was the 120th fastest to reach a running state, and 94 of 141 reached one at all.
- Where is the evidence for PiBot?
- 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.