OpenDots
Your always-on AI coworkers that move between text, calls, and Slack.
Runssource: GitHubhomepageTypeScriptMITcommit 565bf781d654
TypeScript, MIT licensed.
OpenDots runs. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenDots template installs, builds, starts, and serves its React UI at http://127.0.0.1:4310 with all 254 tests passing on Node.js 24.
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 96 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.
- Container has Node.js v18.19.1 but the project requires >=24 (engine constraint in package.json).
- Install time
- 2 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test: 43 test files, 254 tests passed; curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:4310 returned 200; app serves the OpenDots React UI
- Model tokens used
- 90,362
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# One final clean run to confirm
DO_NOT_TRACK=1 npx vitest run --testTimeout=30000 2>&1 | grep -E '"'(Test Files|Tests|Start|Duratio…
succeeded in 20788ms:
Test Files 43 passed (43)
Tests 254 passed (254)
Start at 18:11:44
Duration 20.14s (transform 1.13s, setup 0ms, import 20.16s, tests 30.04s, environment 6ms)
All 254 tests pass, the app starts and serves on port 4310, and all development checks (typecheck, …
2026-11-06T18:12:09.904952Z ERROR codex_core::session: failed to record rollout items: thread 01a1b…
tokens used
90,362
All 254 tests pass, the app starts and serves on port 4310, and all development checks (typecheck, …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, faster than the median of the 36 comparable projects Argusic has measured.
- Recovered from all 1 error 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.
Of the 37 TypeScript projects Argusic has installed and timed, OpenDots was the 8th fastest to reach a running state, and 31 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.
- A quick evaluation: it was running 2 minutes after the clone.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.12 | |
| 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?
- Yes. OpenDots runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error 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. 2 attempts are 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.12: 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?
- 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 OpenDots need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenDots?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does OpenDots compare with the alternatives?
- Of the 37 TypeScript projects Argusic has installed and timed, OpenDots was the 8th fastest to reach a running state, and 31 of 37 reached one at all.
- Where is the evidence for OpenDots?
- 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.