ui-builder
A React component that provides a no-code, visual way to create UIs, compatible with shadcn/ui and custom components.
Runssource: GitHubhomepageTypeScriptMITcommit bc1ceda30693
TypeScript, MIT licensed. The project labels itself: no code, reactjs, shadcn ui, tailwindcss, ui builder and visual editor.
ui-builder runs. An Argusic agent installed it in 0.4 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm test passed (53 suites, 1374 tests), dev server serves HTTP 200 on port 3000, production build compiles all routes, lint and typecheck pass clean, registry build produces 82 files.
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.js is v18.19.1 but Next.js 16 requires >=20.9.0. npm install warned on engine but succeeded. next dev and next build would fail under Node 18.1 minute
- Install time
- under a minute
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 1374 passed; curl localhost:3000 returned HTTP 200; next build compiled 20 routes.
- Model tokens used
- 124,992
- Exact commit tested
- bc1ceda30693
- 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.
2026-10-15T17:09:53.680207Z ERROR codex_core::session: failed to record rollout items: thread 01a14… 2026-10-15T17:09:53.680303Z ERROR codex_core::session: failed to record rollout items: thread 01a14… tokens used 124,992 Everything works. Here's the final verification report: **npm install** completed with only engine warnings (Node 18, expected). **npm test** passed: 53 suites, 1374 tests, full coverage. **npx eslint** passed with 0 warnings. **npx tsc --noEmit** passed with 0 errors. **npm run build-registry** built 82 files successfully. **next build** compiled all pages with Node 20. **next dev** served HTTP 200 on localhost:3000.
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.
- Installed in 0.4 minutes.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 0.4 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/ui-builder)Questions
- Does ui-builder run?
- Yes. ui-builder runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test ui-builder?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bc1ceda30693. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ui-builder?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ui-builder take to install?
- 0.4 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 ui-builder need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ui-builder?
- 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.
- Where is the evidence for ui-builder?
- 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.