kanban-tui
Task Manager with a TUI written in Python and usable by agents
Runssource: GitHubPythonMITcommit 1f96443e3ba6
Python, MIT licensed. The project labels itself: claude skills, jira, kanban, python, task manager, terminal, textual and tui.
kanban-tui runs. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Installed and built; full test suite passes 318/318; both CLI entrypoints run and print version 0.21.2; CLI task/board/column commands respond.
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.
- 14 test failures + 2 collection errors: ModuleNotFoundError atlassian (jira extra not in dev group), skills/mcp command test failures (pycli-mcp missing), test_config.py import errors5 minutes
- uv not installed in container; system pip blocked by PEP 668 externally-managed-environment4 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- `.venv/bin/python -m pytest` exited 0: 318 passed, 77% coverage; `.venv/bin/ktui --version` printed 'kanban-tui, version 0.21.2'; `.venv/bin/ktui --help`, `.venv/bin/ktui task --help`, `.venv/bin/ktui board list --json` all returned 0
- Model tokens used
- 93,554
- Exact commit tested
- 1f96443e3ba6
- 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.
All 318 tests pass, the CLI works, and the app reports version 0.21.2. Let me compile the final res… exec /bin/sh -lc 'cd /work/repo && .venv/bin/python -m pytest --co -q 2>&1 | tail -5' in /work/repo succeeded in 998ms: src/kanban_tui/widgets/task_card.py 192 136 29% 68-69, 73, 79-81, 85,… src/kanban_tui/widgets/task_column.py 123 95 23% 25-29, 32-33, 36-37, … TOTAL 5530 3798 31% ========================= 318 tests collected in 0.56s ========================= Done. The repository installs cleanly via `uv sync` and the full test suite (318 tests) passes once… tokens used 93,554 Done. The repository installs cleanly via `uv sync` and the full test suite (318 tests) passes once…
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 2 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.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kanban-tui)Questions
- Does kanban-tui run?
- Yes. kanban-tui runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test kanban-tui?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1f96443e3ba6. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test kanban-tui?
- 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 kanban-tui 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 kanban-tui need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kanban-tui?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for kanban-tui?
- 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.