geek-life

The Todo List / Task Manager for Geeks in command line

Runssource: GitHubGoMITcommit 7e1e10ff3a58

Go, MIT licensed. The project labels itself: cli app, command line, command line tool, geeks, golang, task manager, terminal ui and todoapp.

geek-life runs. An Argusic agent installed it in 5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Geek-life TUI app builds cleanly and launches under a PTY, rendering the full terminal UI with Projects, Tasks, Dynamic Lists, title bar, and status bar.

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.01 (measured)
recorded runs
1
last tested
stars
563
forks
32
open issues
27
watchers
16
size
2 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 geek-life, 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.

  • Go binary not found in PATH (no go compiler)2 minutes
  • util/util.go line 78: log.Printf does not support error-wrapping directive %w1 minute
  • App panics with 'open /dev/tty: no such device or address' when run directly in headless shell1 minute
  • DB_FILE env var or --db-file flag is needed to avoid ~/.geek-life/default.db path which may not exist
Install time
5 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
/tmp/geek-life built with 'go build -o /tmp/geek-life ./app' succeeded. 'go test ./...' passed all packages. Binary launched under 'script -q -c' with DB_FILE=/tmp/test.db; ESC/host control sequences rendered confirming full TUI startup. Process ran until 'timeout 2' killed it (exit 124). Media validated via 'ffmpeg -v error -i FILE -f null -' (exit 0).
Model tokens used
81,786
Exact commit tested
7e1e10ff3a58
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.

No third-party credentials required — the app uses a local BoltDB database.
tokens used
81,786
All media files decode cleanly (exit 0 for all three). Let me now compile the final result.
**Summary of work done:**
1. **Go not installed** — downloaded `go1.22.5.linux-amd64.tar.gz`, extracted to `/tmp/go`
2. **Build error** — `util/util.go` used `%w` in `log.Printf` (only `%v` is valid there); fixed to …
3. **Build succeeded** — `go build -o /tmp/geek-life ./app` produced an 8.1MB binary with no errors
4. **Tests** — `go test ./...` passes all packages (no test files exist, no build failures)
5. **App launched** — ran under `script` (PTY) with `TERM=xterm-256color`, the full TUI rendered: t…
6. **Media verified** — `ffmpeg -v error -i <file> -f null -` returned exit 0 for all 3 media files…
No third-party credentials required — the app uses a local BoltDB database.

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 4 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

  • Took 5 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 cli-app projects Argusic has installed and timed, geek-life was the 3rd fastest to reach a running state, and 3 of 4 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 5 minutes after the clone.

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 Runner1/3Runs100.000.01

Topics (from GitHub)

cli-appcommand-linecommand-line-toolgeeksgolangtask-managerterminal-uitodoapptodolisttui

Embed the badge

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

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

Questions

Does geek-life run?
Yes. geek-life runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test geek-life?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7e1e10ff3a58. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test geek-life?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does geek-life take to install?
5 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 geek-life need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing geek-life?
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 geek-life compare with the alternatives?
Of the 4 cli-app projects Argusic has installed and timed, geek-life was the 3rd fastest to reach a running state, and 3 of 4 reached one at all.
Where is the evidence for geek-life?
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.

Discussion