tiki

Terminal Markdown-based shapeless workflow builder

Runssource: GitHubhomepageGoApache-2.0commit 872cc5ff178a

Go, Apache-2.0 licensed. The project labels itself: cli, go, golang, hacktoberfest, issue management, kanban, kanban board and linux.

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

tiki binary builds from source, all 40 test packages pass with race detector, CLI subcommands (--version, --help, exec, demo, pipe input) work correctly in this container

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.09 (measured)
recorded runs
1
last tested
stars
225
forks
13
open issues
10
watchers
2
size
59 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
4 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
go test ./... -race exited 0 (40 test packages all ok); binary --version returns 'tiki version dev'; --help prints usage; 'tiki exec select *' over demo project returns data; pipe input creates correct frontmatter; tiki demo extracts project
Model tokens used
181,703
Exact commit tested
872cc5ff178a
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.

echo "---"
stat /work/repo/bin/tiki | grep Modify
echo "---"
date -u +%s' in /work/repo
 succeeded in 0ms:
Modify: 2026-10-30 03:51:09.297481989 +0000
Modify: 2026-10-30 03:52:43.645379927 +0000
1793332523
Start was ~03:51, now ~03:55 — about 4 minutes. Everything is done.
tokens used
181,703
Start was ~03:51, now ~03:55 — about 4 minutes. Everything is done.

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.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Took 4 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 128 cli projects Argusic has installed and timed, tiki was the 85th fastest to reach a running state, and 117 of 128 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 4 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 Runner1/3Runs100.000.09

Topics (from GitHub)

cligogolanghacktoberfestissue-managementkanbankanban-boardlinuxmacosmarkdownmarkdown-viewerproject-managementterminaltuiwindows

Embed the badge

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

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

Questions

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