beads-ui
Local UI for Beads, Collaborate on issues with your coding agent.
Runssource: GitHubJavaScriptMITcommit b1d519a1bb7c
JavaScript, MIT licensed. The project labels itself: agent, ai tools, issue tracker and local first.
beads-ui runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Full dev environment working: Node 22 installed, all deps resolved, type checker and linter pass, 384 tests pass, server starts and serves the Beads UI over HTTP
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.
- System Node 18 insufficient (requires >=22)3 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0 (384 passed, 74 files); curl -s -o /dev/null -w %{http_code} http://127.0.0.1:3000 returned 200
- Model tokens used
- 31,508
- Exact commit tested
- b1d519a1bb7c
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**`npm start`:** Works (debug logging note: a file-watcher EMFILE error appears for `.beads` dir wh… No mocks were needed — the server serves real content from the repo's own `.beads` database. tokens used 31,508 All systems green. Here's the full record: **Install:** `npm install` added 414 packages. Node 22 was installed via nvm (system had Node 18 wh… **Build & type-check:** `tsc --noEmit` passed; `npm run build` produced the frontend bundle. **Tests:** 74 test files, 384 tests — all passed. **Lint & formatting:** `eslint` and `prettier --check` both clean. **Server launch:** `node server/index.js` printed `listening on http://127.0.0.1:3000`. Curling the… **`npm start`:** Works (debug logging note: a file-watcher EMFILE error appears for `.beads` dir wh… No mocks were needed — the server serves real content from the repo's own `.beads` database.
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.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 137 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 138 agent projects Argusic has installed and timed, beads-ui was the 71st fastest to reach a running state, and 92 of 138 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 8 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/beads-ui)Questions
- Does beads-ui run?
- Yes. beads-ui runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test beads-ui?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b1d519a1bb7c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test beads-ui?
- 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 beads-ui take to install?
- 8 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 beads-ui need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing beads-ui?
- 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 beads-ui compare with the alternatives?
- Of the 138 agent projects Argusic has installed and timed, beads-ui was the 71st fastest to reach a running state, and 92 of 138 reached one at all.
- Where is the evidence for beads-ui?
- 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.