Yes. vibesdk runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test vibesdk?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 89c5f3a84c65. 3 attempts are recorded, and the full method is on the methodology page.

What did it cost to test vibesdk?

The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does vibesdk take to install?

12 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 vibesdk need a GPU?

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

What goes wrong when installing vibesdk?

3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for vibesdk?

All 3 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.

vibesdk

An open-source vibe coding platform that helps you build your own vibe-coding platform, built entirely on Cloudflare stack

Runssource: GitHub homepageTypeScriptMITcommit 89c5f3a84c65

TypeScript, MIT licensed. The project labels itself: ai, cloudflare workers, coding agent, durable objects, text to app and vibe coding.

vibesdk runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The VibeSDK project installs, builds, typechecks, and passes all 514 unit tests (root vitest + SDK bun tests) using Bun 1.4.2 and Node.js 20.18.0 inside the container.
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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.06 (measured)
recorded runs: 3
last tested: 2026-09-24
stars: 5,462
forks: 1,282
open issues: 22
watchers: 34
size: 7 MB
created: 2025-08-25
last push: 2026-10-22

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

bun not found in container2 minutes
Node.js v18.19.1 lacks node:util.styleText used by Vitest v32 minutes
cannot install packages via apt-get (no root) or npm -g (permission denied)1 minute

Install time: 12 minutes
Cold machine to finish: 11 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: bun run test exited 0, 474 passed, 1 skipped across 40 files; bun run --cwd sdk test exited 0, 40 passed; bun run build exited 0; bun run typecheck exited 0
Model tokens used: 51,742
Exact commit tested: 89c5f3a84c65
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run 2026-09-16. The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

exec
/bin/sh -lc 'echo "Start time estimation: install deps started at ~19:26"
echo "Finished at ~19:38"
echo "Total: ~12 minutes"' in /work/repo
 succeeded in 0ms:
Start time estimation: install deps started at ~19:26
Finished at ~19:38
Total: ~12 minutes
All verification passed. Here's the final report:
tokens used
51,742
All verification passed. Here's 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 3 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 3 times, so the result is not a one-off.

What did not, or is not known

Took 12 minutes to install, slower than the median of the 231 comparable projects Argusic has measured.

Of the 232 ai projects Argusic has installed and timed, vibesdk was the 165th fastest to reach a running state, and 153 of 232 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	3/3	Runs	100.00	0.06	2026-09-24 19:36 UTC
Argusic Runner	2/3	Runs	100.00	0.08	2026-09-16 22:30 UTC
Argusic Runner	1/3	Runs	100.00	0.04	2026-09-05 00:57 UTC

Topics (from GitHub)

ai cloudflare-workers coding-agent durable-objects text-to-app vibe-coding

Embed the badge

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

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

Questions

Does vibesdk run?: Yes. vibesdk runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test vibesdk?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 89c5f3a84c65. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test vibesdk?: The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does vibesdk take to install?: 12 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 vibesdk need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing vibesdk?: 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does vibesdk compare with the alternatives?: Of the 232 ai projects Argusic has installed and timed, vibesdk was the 165th fastest to reach a running state, and 153 of 232 reached one at all.
Where is the evidence for vibesdk?: All 3 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.