vibesdk
An open-source vibe coding platform that helps you build your own vibe-coding platform, built entirely on Cloudflare stack
Runssource: GitHubhomepageTypeScriptMITcommit 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 13 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Typecheck, lint, test suite (474 passing, 1 skipped), production build, SDK package, SpaceDO typecheck all pass; dev server starts and serves HTML at localhost:5173 returning HTTP 200.
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.
- Bun binary not found and unzip not available for the install script2 minutes
- Cloudflare Vite plugin tried to establish a remote proxy session, failing with 'You must be logged in'2 minutes
- SDK package build failed because dts-bundle-generator was not found2 minutes
- Node.js v18.19.1 is below the >=22 requirement, causing rolldown/Vite to fail with 'styleText' SyntaxError1 minute
- Wrangler tried to build container images from Dockerfile, but Docker is not available1 minute
- Worker FATAL error on startup because CUSTOM_DOMAIN was empty1 minute
- Install time
- 13 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- bun --bun run test exited 0, 474 passed 1 skipped across 40 test files; DEV_MODE=true bun --bun run vite started and curl http://localhost:5173/ returned HTTP 200 with valid HTML; bun --bun run build produced dist/client/ assets; bun --bun run typecheck passed; bun --bun run --cwd sdk package completed successfully; bun --bun run --cwd space typecheck passed
- Model tokens used
- 141,950
- 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 , the attempt that decided the verdict above. 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.
dist/client/assets/editor.api-83yhKdFj.js 2,655.55 kB │ gzip: 682.32 kB [INEFFECTIVE_DYNAMIC_IMPORT] src/utils/sentry.ts is dynamically imported by src/hooks/useSentryUser… [plugin builtin:vite-reporter] (!) Some chunks are larger than 500 kB after minification. Consider: - Using dynamic import() to code-split the application - Use build.rolldownOptions.output.codeSplitting to improve chunking: https://rolldown.rs/reference… - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit. ✓ built in 4.04s All checks pass. Let me compile the final report. tokens used 141,950 All checks pass. Let me compile 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 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 did not, or is not known
- Took 13 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, vibesdk was the 30th fastest to reach a running state, and 30 of 37 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
Topics (from GitHub)
aicloudflare-workerscoding-agentdurable-objectstext-to-appvibe-coding
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vibesdk)Questions
- Does vibesdk run?
- Yes. vibesdk runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 6 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. 2 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.08: 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?
- 13 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?
- 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.
- How does vibesdk compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, vibesdk was the 30th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for vibesdk?
- 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.