cloudflare-os
Agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with your company’s context and systems.
Runssource: GitHubhomepageTypeScriptApache-2.0commit 004ab773fad6
TypeScript, Apache-2.0 licensed.
cloudflare-os runs. An Argusic agent installed it in 6 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Cloudflare OS installs, builds, and runs locally with Node.js v26.13.0, pnpm 11.17.0, and 5 missing native bindings added manually; 316 script tests and all vitest suites pass except workerd-dependent ones that time out under 7.5 GiB memory cgroup.
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.js v18 cannot run .ts files or import node:util styleText2 minutes
- Missing native bindings (vite-plus, tailwindcss/oxide, yuku-codegen, yuku-parser linux-x64-gnu)2 minutes
- pnpm not found in environment1 minute
- Workerd-based test suites timeout under memory cgroup limit1 minute
- .npmrc corrupted by npm config set prefix0.5 minutes
- Install time
- 6 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pnpm build exited 0 (76/76 packages, 43% cache hits); pnpm test showed 316/316 script tests pass, vitest suites pass across all gatekeeper/test packages except 3 workerd suites that OOM; curl http://localhost:3001/cdn-cgi/local/explorer/ confirms wrangler dev server started and served Requests
- Model tokens used
- 115,747
- Exact commit tested
- 004ab773fad6
- 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.
tokens used 115,747 Build succeeded completely — 76 packages built with 43% cache hits, no failures. Now let me compile… Here's the summary of what happened and what was observed: **Errors Encountered & Fixes:** 1. **`pnpm: not found`** — Node.js v18 came without pnpm. Fixed by installing pnpm 11.17.0 via `npm… 2. **`ERR_UNKNOWN_FILE_EXTENSION` for .ts files** — Node.js v18 cannot natively run TypeScript file… 3. **`Cannot find native binding` for vite-plus** — The `@voidzero-dev/vite-plus-linux-x64-gnu` opt… 4. **`Cannot find native binding` for @tailwindcss/oxide** — Same issue with Tailwind's native bind… 5. **`Cannot find native binding` for yuku-codegen/yuku-parser** — Same pattern. Fixed by adding th… 6. **`.npmrc` modified by npm config** — Earlier `npm config set prefix` appended to `.npmrc`. Fixe… 7. **workerd-based test suites timeout** — The `gatekeeper-kit` workerd conformance tests and `work…
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 5 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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 35 comparable projects Argusic has measured.
Of the 36 TypeScript projects Argusic has installed and timed, cloudflare-os was the 25th fastest to reach a running state, and 30 of 36 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.
- A quick evaluation: it was running 6 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cloudflare-os)Questions
- Does cloudflare-os run?
- Yes. cloudflare-os runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test cloudflare-os?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 004ab773fad6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test cloudflare-os?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cloudflare-os take to install?
- 6 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 cloudflare-os need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cloudflare-os?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does cloudflare-os compare with the alternatives?
- Of the 36 TypeScript projects Argusic has installed and timed, cloudflare-os was the 25th fastest to reach a running state, and 30 of 36 reached one at all.
- Where is the evidence for cloudflare-os?
- 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.