whiteboard
Lightweight collaborative Whiteboard / Sketchboard
Runssource: GitHubJavaScriptMITcommit cb4f34d3fcfc
JavaScript, MIT licensed. The project labels itself: collaborative, nodejs, sketchboard and whiteboard.
whiteboard runs. An Argusic agent installed it in 8.5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The collaborative whiteboard Node.js app installs without errors, builds successfully via webpack, passes all 12 tests across 3 test suites, and serves on port 8080 with a working REST API (health, loadWhiteboard, getReadOnlyWid all returning 200) and bundled frontend.
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 18 does not support JSON imports with 'with { type: "json" }' syntax2 minutes
- @babel/core@8 is ESM-only and babel-jest tries to require() it2 minutes
- uuid@14 references bare 'crypto' global as a bare identifier in ESM dist, which fails in Jest VM context1.5 minutes
- jsdom@30 requires Node >=22, not available with Node 181 minute
- copy-webpack-plugin@14 uses Array.toSorted() requiring Node 20+1 minute
- webpack-cli@7 requires Node 20+0.5 minutes
- Install time
- 9 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- npm test: 3 suites, 12 tests, all passed. npm run start: server started on :8080, curl /api/health returned 200, /api/loadwhiteboard?wid=test returned [], /api/getReadOnlyWid returned a UUID, frontend index.html served with correct webpack bundles, apidoc returned 200. webpack build compiled successfully.
- Model tokens used
- 68,669
- Exact commit tested
- cb4f34d3fcfc
- 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.
./src/js/index.js + 60 modules 2.44 MiB [built] [code generated]
./node_modules/css-loader/dist/cjs.js!./src/css/main.css 4.64 KiB [built] [code generated]
webpack 5.110.3 compiled successfully in 15273 ms
Let me now compile all my findings into the final result. Let me calculate the elapsed time and gat…
exec
/bin/sh -lc 'cd /work/repo && date +%s' in /work/repo
succeeded in 0ms:
1795288846
I started around 1795288734 (19:16:14) and now at 1795288846 (19:20:46). So about 8.5 minutes total.
tokens used
68,669
I started around 1795288734 (19:16:14) and now at 1795288846 (19:20:46). So about 8.5 minutes total.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 8.5 minutes.
- Recovered from all 6 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 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.5 minutes after the clone.
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/whiteboard)Questions
- Does whiteboard run?
- Yes. whiteboard runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test whiteboard?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cb4f34d3fcfc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test whiteboard?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does whiteboard take to install?
- 8.5 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 whiteboard need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing whiteboard?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for whiteboard?
- 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.