Tasks.md

A self-hosted, Markdown file based task management board

Runssource: GitHubhomepageJavaScriptMITcommit 8f43374183fb

JavaScript, MIT licensed. The project labels itself: agile, kanban, markdown, project management, self hosted and task management.

Tasks.md runs. An Argusic agent installed it in 12 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 Tasks.md backend (Koa API on port 8080) and frontend (Vite-built SolidJS app served as static files) are both installed and running. The backend REST API correctly handles title, resource (lane/task CRUD), tags, sort, and image endpoints. The frontend build compiles and serves the PWA index.html, JS, and CSS assets.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
2
last tested
stars
2,219
forks
114
open issues
21
watchers
10
size
8 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 Tasks.md, 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.

  • stacks-editor file dependency had no dist/ — npm install copied the submodule before it was built3 minutes
  • Frontend npm install failed: missing git submodule Stacks-Editor (file: frontend/src/components/Stacks-Editor/package.json)2 minutes
  • Express Koa body-parser bug: The POST to /_api/resource/Backlog (existing directory) threw 500 Internal Server Error (mkdir on existing dir)1 minute
Install time
12 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
Started backend with `node server.js` on port 8080, then `curl -s http://localhost:8080/_api/title` returned 200, `curl -s http://localhost:8080/_api/resource/` returned task tree JSON, `curl -s -X POST "http://localhost:8080/_api/resource/Backlog/Test%20task.md" -H "Content-Type: application/json" -d '{"isFile":true,"content":"# Test"}'` returned 201, `curl -s http://localhost:8080/_api/resource/` returned the created task. Frontend homepage served 200 with full HTML.
Model tokens used
63,405
Exact commit tested
8f43374183fb
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Now for the JSON:
- install_succeeded: true - both backend and frontend npm install succeeded
- launch_succeeded: true - server started and responded on port 8080
- install_minutes: around 10 (including building Stacks-Editor and frontend)
- errors: I should list the errors encountered and fixed
- test_depth: tier1_real - I exercised the actual API endpoints
- verified_how: I'll list the curl commands and results
- final_state: a summary sentenceNow let me compile the final report.
**Time calculation:**
- Start: ~22:16 UTC
- Now: ~22:22 UTC
- About 6 minutes elapsed for actual interactive work, but the install steps (npm install, builds) …

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 12 minutes.
  • 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 MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 5 agile projects Argusic has installed and timed, Tasks.md was the 3rd fastest to reach a running state, and 4 of 5 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.05
Argusic Runner1/3Runs100.000.13

Topics (from GitHub)

agilekanbanmarkdownproject-managementself-hostedtask-management

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Tasks.md.svg)](https://argusic.com/subject/tasks-md)

Questions

Does Tasks.md run?
Yes. Tasks.md runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test Tasks.md?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8f43374183fb. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Tasks.md?
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 Tasks.md take to install?
12 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 Tasks.md need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Tasks.md?
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 Tasks.md compare with the alternatives?
Of the 5 agile projects Argusic has installed and timed, Tasks.md was the 3rd fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for Tasks.md?
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.

Discussion