dooit

An awesome TUI todo manager

Runssource: GitHubhomepagePythonMITcommit ba2a7efdbb56

Python, MIT licensed. The project labels itself: cli, python3, rich, terminal based, textual, todo app, todolist and tui.

dooit runs. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Dooit 3.3.4 is installed in a virtual environment, all 81 tests pass, and the CLI commands (--version, --help, config-loc) function correctly.

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.02 (measured)
recorded runs
2
last tested
stars
2,968
forks
134
open issues
27
watchers
19
size
10 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.

Install time
1 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pytest tests/ -v returned 81 passed, 0 failed; dooit --version returned 'dooit - 3.3.4'
Model tokens used
15,460
Exact commit tested
ba2a7efdbb56
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.

**Install**: `pip install -e .` inside a venv succeeded — all dependencies resolved and the package…
**Tests**: Ran `pytest tests/ -v` — **81 passed, 0 failed** in ~28s. The test suite covers model op…
**App launch**: `dooit --version` printed `dooit - 3.3.4`, `dooit --help` printed usage with all su…
No errors were encountered — everything worked out of the box.
tokens used
15,460
Now let me compile the results.
Here's the report:
**Install**: `pip install -e .` inside a venv succeeded — all dependencies resolved and the package…
**Tests**: Ran `pytest tests/ -v` — **81 passed, 0 failed** in ~28s. The test suite covers model op…
**App launch**: `dooit --version` printed `dooit - 3.3.4`, `dooit --help` printed usage with all su…
No errors were encountered — everything worked out of the box.

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 1 minute, faster than the median of the 123 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • 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 124 cli projects Argusic has installed and timed, dooit was the 18th fastest to reach a running state, and 112 of 124 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.
  • A quick evaluation: it was running 1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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.02
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

clipython3richterminal-basedtextualtodo-apptodolisttuiunixporn

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/dooit.svg)](https://argusic.com/subject/dooit)

Questions

Does dooit run?
Yes. dooit runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test dooit?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ba2a7efdbb56. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test dooit?
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 dooit take to install?
1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does dooit need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing dooit?
Nothing did, in the recorded run: zero errors between clone and running.
How does dooit compare with the alternatives?
Of the 124 cli projects Argusic has installed and timed, dooit was the 18th fastest to reach a running state, and 112 of 124 reached one at all.
Where is the evidence for dooit?
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