BeatDesign runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 27 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test BeatDesign?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit d2ef27017442. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test BeatDesign?

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 BeatDesign take to install?

27 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 BeatDesign need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing BeatDesign?

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.

Where is the evidence for BeatDesign?

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.

BeatDesign

Local-first AI canvas and timeline. Any MCP agent. Open-source alternative to Higgsfield.

Runs with mockssource: GitHub homepageTypeScriptApache-2.0commit d2ef27017442

TypeScript, Apache-2.0 licensed. The project labels itself: ai canvas, ai image generation, ai video generation, beatapi, canvas, generative ai, image generation and local first.

BeatDesign runs, with stand-ins for the services it depends on. An Argusic agent installed it in 27 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

pnpm install, db:push, dev server, production build and production server all succeed; 417 unit tests pass; the dev server at 127.0.0.1:3020 answers HTTP 200 on /api/ping with {"message":"pong"}; the production server at port 3000 returns the same.
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 92 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.10 (measured)
recorded runs: 1
last tested: 2026-10-27
stars: 267
forks: 36
open issues: 3
watchers: 4
size: 17 MB
created: 2026-08-20
last push: 2026-10-21

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-27. 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.

Time lost to each failure while testing BeatDesign, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Node 18.19.1 shipped in container (requires >=22); pnpm not available5 minutes
Vite 8 required Node >=22.12 but downloaded Node 22.0.03 minutes
paraglide-js compilation failed on Node 18 (crypto.subtle undefined in tsx)2 minutes
TypeScript typecheck errors (routeTree.gen.ts not found at typecheck time, createFileRoute generic mismatch)

Install time: 27 minutes
Cold machine to finish: 6 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: pnpm test exited 0, 417 passed; curl http://127.0.0.1:3020/api/ping returned {"message":"pong"} with HTTP 200; node .output/server/index.mjs started and returned HTTP 200 on /api/ping
Model tokens used: 67,003
Exact commit tested: d2ef27017442
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

All systems verified. Here's the final summary:
- `pnpm test` — **417 passed, 0 failed**
- `pnpm build` — succeeds, production server built
- `curl http://127.0.0.1:3020/api/ping` — returns `{"message":"pong"}` (HTTP 200)
- `node .output/server/index.mjs` — production server starts on port 3000, responds 200
tokens used
67,003
All systems verified. Here's the final summary:
- `pnpm test` — **417 passed, 0 failed**
- `pnpm build` — succeeds, production server built
- `curl http://127.0.0.1:3020/api/ping` — returns `{"message":"pong"}` (HTTP 200)
- `node .output/server/index.mjs` — production server starts on port 3000, responds 200

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

Installed in 27 minutes.
Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed Apache-2.0, as reported by its host.

What did not, or is not known

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

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	1/3	Runs with mocks	92.00	0.10	2026-10-27 08:46 UTC

Topics (from GitHub)

ai-canvas ai-image-generation ai-video-generation beatapi canvas generative-ai image-generation local-first mcp mcp-server open-source react video-editor video-generation

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/BeatDesign.svg)](https://argusic.com/subject/beatdesign)

Questions

Does BeatDesign run?: BeatDesign runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 27 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test BeatDesign?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit d2ef27017442. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test BeatDesign?: 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 BeatDesign take to install?: 27 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 BeatDesign need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing BeatDesign?: 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.
Where is the evidence for BeatDesign?: 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.