paint-board
🎨 A powerful multi-end drawing board that brings together a lot of creative brushes to experience a whole new range of drawing effects!
Runssource: GitHubhomepageTypeScriptMITcommit 57265d7458fc
TypeScript, MIT licensed. The project labels itself: canvas, canvas game, drawing, drawing board, drawingboard, javascript, sketch and whiteboard.
paint-board runs. An Argusic agent installed it in 29 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
paint-board v2.0.0 (paint-board) builds and serves correctly via Vite. The dev server (pnpm dev) starts and returns HTTP 200 on /paint-board/. All application JS/CSS assets compile cleanly.
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 60 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.
- vite-plugin-pwa 0.20.5 failed during build: Dynamic require of workbox-build not supported (and even after updating to 1.3.0, workbox-build 7.4.1 crashed with 'crypto is not defined')8 minutes
- Native canvas module (node-canvas v2.11.2) failed to compile — missing pixman-1 dev headers (libpixman-1-0 runtime is installed but no .pc or headers)4 minutes
- pnpm not available in container2 minutes
- pnpm blocked build scripts (canvas, esbuild, onnxruntime-node, protobufjs, sharp) due to supply-chain security policy1 minute
- Install time
- 29 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npx vite build exited 0: ✓ built in 42s, 2166 modules transformed, dist/ produced; dev server at localhost:5183 answered HTTP 200 on GET /paint-board/
- Model tokens used
- 110,010
- Exact commit tested
- 57265d7458fc
- 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.
+++ b/vite.config.ts
@@ -2,24 +2,11 @@ import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import viteEslint from 'vite-plugin-eslint'
import svgr from 'vite-plugin-svgr'
-import { VitePWA } from 'vite-plugin-pwa'
import { resolve } from 'path'
Now compiling the final report.
2026-10-03T01:40:18.184815Z ERROR codex_core::session: failed to record rollout items: thread 01a0f…
tokens used
110,010
Now compiling the final report.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 4 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 29 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
Of the 9 canvas projects Argusic has installed and timed, paint-board was the 9th fastest to reach a running state, and 6 of 9 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.
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 | 2/3 | Did not run | 20.00 | 0.02 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.10 |
Topics (from GitHub)
canvascanvas-gamedrawingdrawing-boarddrawingboardjavascriptsketchwhiteboard
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/paint-board)Questions
- Does paint-board run?
- Yes. paint-board runs. Argusic installed and launched it on a clean machine in 29 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test paint-board?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 57265d7458fc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test paint-board?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does paint-board take to install?
- 29 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 paint-board need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing paint-board?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does paint-board compare with the alternatives?
- Of the 9 canvas projects Argusic has installed and timed, paint-board was the 9th fastest to reach a running state, and 6 of 9 reached one at all.
- Where is the evidence for paint-board?
- 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.