puck
The visual editor for React.
Runssource: GitHubhomepageTypeScriptMITcommit 449f42df3abd
TypeScript, MIT licensed. The project labels itself: ai, builder, drag and drop, draganddrop, no code, nocode, page builder and pagebuilder.
puck runs. An Argusic agent installed it in 8 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Puck monorepo builds and tests successfully with Node 24 and pnpm 11, demo server responds HTTP 200, and all 292 unit tests plus 4 e2e smoke tests pass.
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 — project requires >=242 minutes
- pnpm not found in PATH1 minute
- npm install -g pnpm failed EACCES on /usr/local/lib1 minute
- Puppeteer: No usable sandbox in container1 minute
- Smoke test process.stdout.moveCursor not a function (non-TTY terminal)
- Install time
- 8 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pnpm test exited 0 (54 suites, 292 passed); demo server curl http://localhost:3000 returned 200; smoke tests 4/4 passed with puppeteer headless chrome
- Model tokens used
- 65,890
- Exact commit tested
- 449f42df3abd
- 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.
Now let me clean up the server and compile the final answer. exec /bin/sh -lc 'pkill -f "next start" 2>/dev/null; echo "done"' in /work/repo exited 143 in 0ms: Here's the complete report. **Install** — Needed to install pnpm (`npm_config_prefix=$HOME/.npm-global npm install -g pnpm`) an… **Tests** — `pnpm test` ran 54 suites, 292 tests — all passed. The demo app built with Next.js. The… tokens used 65,890 Here's the complete report. **Install** — Needed to install pnpm (`npm_config_prefix=$HOME/.npm-global npm install -g pnpm`) an… **Tests** — `pnpm test` ran 54 suites, 292 tests — all passed. The demo app built with Next.js. The…
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 5 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, puck was the 150th fastest to reach a running state, and 166 of 235 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)
aibuilderdrag-and-dropdraganddropno-codenocodepage-builderpagebuilderreactvisual-editor
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/puck)Questions
- Does puck run?
- Yes. puck runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test puck?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 449f42df3abd. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test puck?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does puck 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 puck need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing puck?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does puck compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, puck was the 150th fastest to reach a running state, and 166 of 235 reached one at all.
- Where is the evidence for puck?
- 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.