OpenDots
Your always-on AI coworkers that move between text, calls, and Slack.
Runs with mockssource: GitHubTypeScriptMITcommit 565bf781d654
TypeScript, MIT licensed.
OpenDots runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.
OpenDots builds, all 254 unit tests pass, the server starts on port 4310, serves the app HTML at GET / and returns valid JSON from the state and workspace APIs
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
Subject data from GitHub, linked at the top of this page. 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.
- Install time
- 1 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test exited 0, 254 passed across 43 files; npm start served http://127.0.0.1:4310/ returning HTTP 200 with HTML, /api/state returned JSON, /api/workspace returned JSON
- Model tokens used
- 35,314
- Exact commit tested
- 565bf781d654
- 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.
3. **`npm test`** — all **254 tests passed** across **43 test files**. 4. **`npm run build`** — built `dist/client` via Vite and `dist/server` via tsc. 5. **`npm start`** — the server started and served HTTP 200 on `/` with the OpenDots HTML page, and… tokens used 35,314 All steps completed successfully. Here's the summary: **What happened:** 1. **Node.js version mismatch** — the repo requires Node >= 24, but only Node 18 was available. I i… 2. **`npm ci`** — installed all 329 packages without error. 3. **`npm test`** — all **254 tests passed** across **43 test files**. 4. **`npm run build`** — built `dist/client` via Vite and `dist/server` via tsc. 5. **`npm start`** — the server started and served HTTP 200 on `/` with the OpenDots HTML page, and…
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 1 minute, faster than the median of the 30 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, 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.
Of the 31 TypeScript projects Argusic has installed and timed, OpenDots was the 4th fastest to reach a running state, and 22 of 31 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.02 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/opendots)Questions
- Does OpenDots run?
- OpenDots runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test OpenDots?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 565bf781d654. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test OpenDots?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenDots take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does OpenDots need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenDots?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does OpenDots compare with the alternatives?
- Of the 31 TypeScript projects Argusic has installed and timed, OpenDots was the 4th fastest to reach a running state, and 22 of 31 reached one at all.
- Where is the evidence for OpenDots?
- 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.