Yes. gitlogue runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test gitlogue?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 73750f745249. 3 attempts are recorded, and the full method is on the methodology page.

What did it cost to test gitlogue?

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 gitlogue take to install?

3.3 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 gitlogue need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing gitlogue?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for gitlogue?

All 3 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.

gitlogue

A cinematic Git commit replay tool for the terminal, turning your Git history into a living, animated story.

Runssource: GitHubRustISCcommit 73750f745249

Rust, ISC licensed. The project labels itself: cli, cli tool, code animation, commit history, developer tools, git, git history and git visualization.

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

The gitlogue binary builds from source, all 228 unit/integration tests pass, and the CLI responds with correct help text and version 0.11.0.
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: 3
last tested: 2026-09-24
stars: 5,260
forks: 123
open issues: 9
watchers: 9
size: 80 MB
created: 2025-11-08
last push: 2026-11-05

Subject data from GitHub, linked at the top of this page, refreshed 2026-11-07. 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: 3 minutes
Cold machine to finish: 4 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: cargo test exited 0, 228 tests passed (55+163+10); cargo run -- --version returned 'gitlogue 0.11.0'; cargo run -- --help printed full usage
Model tokens used: 43,954
Exact commit tested: 73750f745249
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.

running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
All 228 tests passed and the binary runs correctly. Let me do a final quick version check:
exec
/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && cargo run -- --version 2>&1 && git log --onel…
 succeeded in 168ms:
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.24s
     Running `target/debug/gitlogue --version`
gitlogue 0.11.0
73750f7 Merge pull request #235 from unhappychoice/dependabot/cargo/chrono-english-0.2.1
tokens used
43,954

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 ISC, as reported by its host.
Measured 3 times, so the result is not a one-off.

What did not, or is not known

Took 3.3 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.

Of the 124 cli projects Argusic has installed and timed, gitlogue was the 63rd fastest to reach a running state, and 111 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 3.3 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	3/3	Runs	100.00	0.01	2026-09-24 22:21 UTC
Argusic Runner	2/3	Runs	100.00	0.02	2026-09-17 04:21 UTC
Argusic Runner	1/3	Runs	100.00	0.13	2026-09-03 14:38 UTC

Embed the badge

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

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

Questions

Does gitlogue run?: Yes. gitlogue runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test gitlogue?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 73750f745249. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test gitlogue?: 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 gitlogue take to install?: 3.3 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 gitlogue need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gitlogue?: Nothing did, in the recorded run: zero errors between clone and running.
How does gitlogue compare with the alternatives?: Of the 124 cli projects Argusic has installed and timed, gitlogue was the 63rd fastest to reach a running state, and 111 of 124 reached one at all.
Where is the evidence for gitlogue?: All 3 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.