dots
Open-source dots for the web: an AI agent with its own browser, one that does not get blocked.
Runs with mockssource: GitHubPythonMITcommit 2ff9848c1c8a
Python, MIT licensed. The project labels itself: ai agent, ai agents, ai browser, anti detect browser, browser agent, browser automation, chatgpt and dotfiles.
dots runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.7 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
All 4 pytest tests pass, the CLI help displays correctly, and the app launches a server on port 9876 with the stealth Firefox engine downloaded and ready.
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, 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.
- Install time
- under a minute
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest tests/ exited 0, 4 passed; dots --help displayed full usage with all options; dots --openrouter-key sk-or-fake launched server on port 9876, socket confirmed listening
- Model tokens used
- 117,762
- Exact commit tested
- 2ff9848c1c8a
- 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.
succeeded in 614ms: === Installed package versions === Name: invisible-playwright-mcp Version: 0.70.2 Name: dots Version: 0.1.0 === Browser engine === /home/runner/.cache/invisible-playwright/firefox-35_151.0_20261002195313/firefox-bin === Server verified on 9876 === done tokens used 117,762
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 0.7 minutes, faster than the median of the 20 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 21 ai-agent projects Argusic has installed and timed, dots was the 6th fastest to reach a running state, and 14 of 21 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
ai-agentai-agentsai-browseranti-detect-browserbrowser-agentbrowser-automationchatgptdotfilesdotsfirefoxllm-agentmcpopen-source-alternativeopenaiopenai-dotsopenrouterplaywrightstealth-browserweb-agentweb-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dots)Questions
- Does dots run?
- dots 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 dots?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2ff9848c1c8a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test dots?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does dots take to install?
- 0.7 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 dots need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dots?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does dots compare with the alternatives?
- Of the 21 ai-agent projects Argusic has installed and timed, dots was the 6th fastest to reach a running state, and 14 of 21 reached one at all.
- Where is the evidence for dots?
- 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.