taskwarrior
Taskwarrior - Command line Task Management
Runssource: GitHubhomepageC++MITcommit 9956cdfc674e
C++, MIT licensed. The project labels itself: gtd, task manager, taskwarrior, to do list and todo.
taskwarrior runs. An Argusic agent installed it in 19 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Taskwarrior 3.5.0 is fully built and installed with all 179 tests passing, the binary answers '3.5.0' on --version, supports add/list/done workflows against a local task database, and the C++ unit tests, Python integration tests, and shell script tests all succeed.
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, 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.
- default.theme not found at compile-time TASK_RCDIR path (/usr/local/share/doc/task/rc) during test execution3 minutes
- Rust toolchain not found2 minutes
- libuuid-dev headers not found (only libuuid1 runtime library present)1 minute
- Install time
- 19 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- ctest --test-dir build returned '100% tests passed, 0 tests failed out of 179'; ./build/src/task --version returned '3.5.0'; ./build/src/task add/list/done worked with correct output
- Model tokens used
- 86,934
- Exact commit tested
- 9956cdfc674e
- 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 - Test task 0 1 task Recently upgraded to 3.5.0. Please run 'task news' to read highlights about the new release. Completed task 1 'Test task'. Completed 1 task. No matches. Recently upgraded to 3.5.0. Please run 'task news' to read highlights about the new release. All 179 tests pass (100%), and the CLI works end-to-end. Here's the summary: tokens used 86,934 All 179 tests pass (100%), and the CLI works end-to-end. Here's the summary:
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 19 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/taskwarrior)Questions
- Does taskwarrior run?
- Yes. taskwarrior runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test taskwarrior?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9956cdfc674e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test taskwarrior?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does taskwarrior take to install?
- 19 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 taskwarrior need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing taskwarrior?
- 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.
- Where is the evidence for taskwarrior?
- 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.