DeepSeek-Bot
A team of long-lived bots for DeepSeek Harness, with main bots, bot-to-bot messages and group chats.
Runs with mockssource: GitHubJavaScriptApache-2.0commit 1bebe826f74e
JavaScript, Apache-2.0 licensed. The project labels itself: bot, deepseek harness, dsh plugin and multi agent.
DeepSeek-Bot runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3.4 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The ds-bot plugin's npm install and client build succeed. All 932 ds-bot unit tests and 111 app unit tests pass with Node 22. The client build, lint, and client.js consistency check all pass. The desktop Electron app answers version 44.7.0 with --no-sandbox.
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- oxlint native binding @oxlint/binding-linux-x64-gnu not installed by `npm run harness` on Node 180.5 minutes
- Smoke test requires `../deepseek-harness` checkout and pnpm, neither available in container0.5 minutes
- Node.js v18 is too old; project requires Node 22+ for `registerHooks` from `node:module`0.4 minutes
- Desktop app (Electron) prints DBus errors in container without system bus
- Install time
- 3 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm test with Node 22: 932 passed, 0 failed, 2 skipped on ds-bot; 111 passed, 0 failed, 1 cancelled, 1 skipped on app. npm run build --check: client.js matches source. npm run lint with Node 22: passes with warnings only. Desktop app `npx electron --no-sandbox --version` returned v44.7.0.
- Model tokens used
- 84,450
- Exact commit tested
- 1bebe826f74e
- 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.
# pass 111 # fail 0 # cancelled 1 # skipped 1 # todo 0 # duration_ms 1337.508282 The cancelled test is `session-check.test.mjs` — it was cancelled because its parent suite hit a br… Here's the final report: tokens used 84,450 The cancelled test is `session-check.test.mjs` — it was cancelled because its parent suite hit a br… Here's the final report:
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
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, 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.
- Took 3.4 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 bot projects Argusic has installed and timed, DeepSeek-Bot was the 3rd fastest to reach a running state, and 1 of 4 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.06 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/deepseek-bot)Questions
- Does DeepSeek-Bot run?
- DeepSeek-Bot runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test DeepSeek-Bot?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1bebe826f74e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test DeepSeek-Bot?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does DeepSeek-Bot take to install?
- 3.4 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 DeepSeek-Bot need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing DeepSeek-Bot?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does DeepSeek-Bot compare with the alternatives?
- Of the 4 bot projects Argusic has installed and timed, DeepSeek-Bot was the 3rd fastest to reach a running state, and 1 of 4 reached one at all.
- Where is the evidence for DeepSeek-Bot?
- 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.