dashi-taskboard
现代化可灵活嵌入的任务面板，支持 Codex、DeepSeek Harness
Runssource: GitHubJavaScriptApache-2.0commit 723c400eec86
JavaScript, Apache-2.0 licensed. The project labels itself: claude code, cli, codex, codex app, codex desktop, codex plugin, dsh and dsh plugin.
dashi-taskboard runs. An Argusic agent installed it in 45 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Codex Taskboard server starts and answers HTTP 200 on port 47823, all 30 server tests and 9 component tests pass, the web UI builds via Vite, and the taskctl CLI prints its help. The server and build scripts need --experimental-sqlite passed to node, which is not in the current package.json scripts.
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 100 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- System Node.js 18.19.1 does not meet >=22.5 requirement3 minutes
- Rollup native binding @rolldown/binding-linux-x64-gnu not installed as optional dependency2 minutes
- node:sqlite built-in requires --experimental-sqlite flag2 minutes
- Install time
- 45 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- node --experimental-sqlite --test test/server.test.mjs → 30 passed, 0 failed; npx vitest run web/src/components/MarkdownDocument.test.tsx → 1 file passed 9 tests; curl http://127.0.0.1:47823/ → HTTP 200; GET /api/projects → valid JSON
- Model tokens used
- 138,119
- Exact commit tested
- 723c400eec86
- 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.
1. **Node.js upgrade** – repo requires `>=22.5`; system had v18.19.1. Installed v22.5.0 via `n`, th…
2. **Missing native binding** – The Vite/Rolldown build failed because `@rolldown/binding-linux-x64…
3. **`node:sqlite` flag** – The server and tests use `import { DatabaseSync } from "node:sqlite"`, …
**Verification:**
- **Server** launched and answered `HTTP 200` on `http://127.0.0.1:47823/`
- **API** returns projects (`GET /api/projects` → valid JSON with default `local` project)
- **Server test suite**: `node --experimental-sqlite --test test/server.test.mjs` → **30 passed, 0 …
- **Component tests**: `npx vitest run web/src/components/MarkdownDocument.test.tsx` → **1 file pas…
- **TypeScript check**: `npm run typecheck` → exit 0
- **CLI**: `node cli/taskctl.mjs --help` prints all subcommands
- **Web build**: `npm run build:web` succeeds (the full `npm run build` fails at the post-build inj…
**Remaining gap:** `npm run build` and `npm start` need the `--experimental-sqlite` flag. The `npm …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.
- Recovered from all 3 errors 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 45 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 claude-code projects Argusic has installed and timed, dashi-taskboard was the 8th fastest to reach a running state, and 7 of 8 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.
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
Topics (from GitHub)
claude-codeclicodexcodex-appcodex-desktopcodex-plugindshdsh-pluginskills
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dashi-taskboard)Questions
- Does dashi-taskboard run?
- Yes. dashi-taskboard runs. Argusic installed and launched it on a clean machine in 45 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test dashi-taskboard?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 723c400eec86. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test dashi-taskboard?
- 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 dashi-taskboard take to install?
- 45 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 dashi-taskboard need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dashi-taskboard?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does dashi-taskboard compare with the alternatives?
- Of the 8 claude-code projects Argusic has installed and timed, dashi-taskboard was the 8th fastest to reach a running state, and 7 of 8 reached one at all.
- Where is the evidence for dashi-taskboard?
- 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.