dorabot

macOS app for 24/7 AI agents in an IDE with memory, scheduled tasks, browser use + access to Whatsapp, Telegram, Slack.

Runs with mockssource: GitHubhomepageTypeScriptMITcommit ed7226ef32b0

TypeScript, MIT licensed. The project labels itself: ai agent, ai assistant, browser automation, claude, claude agent sdk, electron, macos and open source.

dorabot runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.2 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

The dorabot backend compiles from source, its WebSocket gateway serves HTTP health at 200 on a Unix socket and handles RPC methods for auth, sessions, skills, agents, calendar RRULE scheduling, goals CRUD, projects/tasks, and provider detection against a real SQLite (WAL) database; the interactive CLI lists skills and agents; 8 backend test scripts pass;

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 78.7 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
78.7 / 100
cost of the verifying run
$0.40 (measured)
recorded runs
1
last tested
stars
249
forks
35
open issues
25
watchers
5
size
43 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 dorabot, 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.

  • Dorabot single-message ( -m ) path hangs because the Claude SDK CLI binary validates models locally and the default config model is not in its embedded catalog; no real credentials are available to satisfy the auth chain14 minutes
  • Node.js v18 (pre-installed) does not meet project requirement of >=223 minutes
  • Three package.json test scripts (test-model-catalog.mjs, test-codex-auth-state.mjs, test-gateway-auth-state.mjs) are referenced but never committed to git
Install time
1 minutes
Cold machine to finish
29 minutes
Errors hit and fixed
3 hit, 1 fixed with no human help
How the result was proved
Gateway health endpoint (curl --unix-socket ~/.dorabot/gateway.sock http://localhost/health) returned HTTP 200. WebSocket RPC over Unix socket authenticated and exercised 15+ methods (ping, status, skills.list, sessions.list, calendar.list, channels.status, agents.list, config.get, goals.add/update/delete, calendar.add/list, projects.add/tasks.add/delete, provider.get, provider.detect). Backend test suite ran 8/8 scripts all passing: test-fs-ops 33/33, test-scheduler-run-item ok, test-event-log ok, test-fs-watch-events ok, test-reconnect-replay ok, test-load-7x4 recovered 8400/8400 events, test-question-lifecycle ok, test-oauth-refresh ok. Desktop electron-vite build completed with 106 output files. Interactive CLI listed 5 eligible skills and 8 agents. tsc typecheck completed with 0 errors.
Model tokens used
860,075
Exact commit tested
ed7226ef32b0
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.

Desktop out/ files: 106
exec
/bin/sh -lc "# Clean up any remaining test procs
ps aux | grep -v grep | grep -E \"mock-anthropic|mock-final|mock6\" | awk '{print "'$2}'"' | xargs …
 succeeded in 0ms:
cleanup done
Here is my final assessment:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":1.2,"errors…
tokens used
860,075
Here is my final assessment:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":1.2,"errors…

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.2 minutes, faster than the median of the 83 comparable projects Argusic has measured.
  • 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.
  • Hit 3 errors during setup, 2 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 84 ai-agent projects Argusic has installed and timed, dorabot was the 23rd fastest to reach a running state, and 58 of 84 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks78.670.40

Topics (from GitHub)

ai-agentai-assistantbrowser-automationclaudeclaude-agent-sdkelectronmacosopen-sourceopenaipersonal-aislack-bottelegram-bottypescriptwhatsapp-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/dorabot.svg)](https://argusic.com/subject/dorabot)

Questions

Does dorabot run?
dorabot runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test dorabot?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed7226ef32b0. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test dorabot?
The run that produced this verdict cost $0.40: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does dorabot take to install?
1.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 dorabot need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing dorabot?
3 things 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 dorabot compare with the alternatives?
Of the 84 ai-agent projects Argusic has installed and timed, dorabot was the 23rd fastest to reach a running state, and 58 of 84 reached one at all.
Where is the evidence for dorabot?
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.

Discussion