CoWork-OS

Rent the model. Own everything else. Free, open-source AI app for real work.

Runssource: GitHubhomepageTypeScriptMITcommit eff5d1262b8f

TypeScript, MIT licensed. The project labels itself: ai assistants, ai automation, claude, desktop app, discord bot, electron, gemini and guardrails.

CoWork-OS runs. An Argusic agent installed it in 2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Cowork OS repo installs and builds on Node 24, the full vitest suite passes (855 files, 8918 tests), and the cowork CLI answers with version 0.5.54.

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

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.37 (measured)
recorded runs
2
last tested
stars
554
forks
102
open issues
17
watchers
3
size
135 MB
created
last push

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.

Time lost to each failure while testing CoWork-OS, 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.

  • sqlite3 CLI binary missing, breaking local-control-plane-discovery and qa-eval-runner tests (spawnSync sqlite3 ENOENT)25 minutes
  • Numbat runtime manifest missing so NumbatBinaryResolver/integration tests failed (Go toolchain unavailable)15 minutes
  • env-migration test failed because container had OPENROUTER_API_KEY set, flipping provider selection from deepseek to openrouter10 minutes
  • npm install failed on Node 18 with 'Invalid comparator: npm:[email protected]'3 minutes
  • executor-step-failures test failed cleaning a directory symlink: ERR_FS_EISDIR3 minutes
Install time
2 minutes
Cold machine to finish
71 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
npx vitest run --reporter=verbose exited 0: 855 test files passed, 8918 tests passed, 2 todo; node bin/cowork-cli.js version printed 'CoWork OS 0.5.54 Node 24.21.0 Electron 44.4.3 linux x64'
Model tokens used
2,229,524
Exact commit tested
eff5d1262b8f
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.

**Setup performed**
- Installed Node 24.4.0 (matching `.nvmrc`; container had Node 18, which breaks `npm install` with …
- `npm install` (1370 packages) → `npm run setup` (Electron 44.4.3 + native rebuild of `better-sqli…
**Bugs found & fixed**
1. Node 18 couldn't parse the alias `"node-fetch": "npm:[email protected]"` in dependencies —…
2. Container env `OPENROUTER_API_KEY` leaked into `env-migration.test.ts`, flipping provider select…
3. `sqlite3` CLI was missing; `local-control-plane-discovery.test.ts` helper and `src/cli/local-con…
4. `executor-step-failures.test.ts` failed to clean up a directory symlink (`ERR_FS_EISDIR`) — adde…
5. Numbat runtime manifest/binary absent (Go not available, no compiler) — stood up a schema-correc…
**Final verification**
- `npx vitest run --reporter=verbose` exited 0: `855 passed (855)` files, `8918 passed | 2 todo` te…
- `node bin/cowork-cli.js version` printed: `CoWork OS 0.5.54 / Node 24.21.0 / Electron 44.4.3 / li…

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.
  • Installed in 2 minutes.
  • 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 MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

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 2 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.37
Argusic Runner1/3Did not run20.000.08

Topics (from GitHub)

ai-assistantsai-automationclaudedesktop-appdiscord-botelectrongeminiguardrailsllmlocal-firstmacosmcpmodel-context-protocolopenaipersonal-aisecurityself-hostedslack-bottelegramwhatsapp-bot

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/CoWork-OS.svg)](https://argusic.com/subject/cowork-os)

Questions

Does CoWork-OS run?
Yes. CoWork-OS runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test CoWork-OS?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit eff5d1262b8f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test CoWork-OS?
The run that produced this verdict cost $0.37: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does CoWork-OS take to install?
2 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 CoWork-OS need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing CoWork-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.
Where is the evidence for CoWork-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.

Discussion