gitui
Blazing 💥 fast terminal-ui for git written in rust 🦀
Runssource: GitHubRustMITcommit 2fa693cb6ed4
Rust, MIT licensed. The project labels itself: async, bash, command line interface, command line tool, git, hacktoberfest, rust and terminal.
gitui runs. An Argusic agent installed it in 2.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
GitUI 0.28.1 builds from source, its full test suite passes (314 tests), and the binary launches as a terminal UI displaying real git repositories on the configured virtual display.
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 97.8 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.
- Rust toolchain not installed0.5 minutes
- python not found in PATH (hooks test pre_commit_py fails)0.1 minutes
- gpg, ssh-keygen, gpgsm not available (3 signing e2e tests skippable, not core)
- Install time
- 3 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test --workspace (skipping 3 sign tests) exited 0: 174+31+30+79=314 passed, 0 failed; release binary ./target/release/gitui --version returned 'gitui 0.28.1-nightly 2026-09-22 (2fa693c)'; --bugreport succeeded; gitui launched as TUI in script PTY showing ratatui output
- Model tokens used
- 39,827
- Exact commit tested
- 2fa693cb6ed4
- 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.
succeeded in 0ms: /usr/bin/script 0 ptmx exec /bin/sh -lc '. "$HOME/.cargo/env" && export PATH="$HOME/.local/bin:$PATH" && cd /tmp/testrepo && ti… succeeded in 6852ms: Session terminated, killing shell... ...killed. The app launched successfully in a PTY (via `script`). The TUI rendered ANSI output before the time… tokens used 39,827 The app launched successfully in a PTY (via `script`). The TUI rendered ANSI output before the time…
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 2.5 minutes.
- Recovered from all 3 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.
- Measured 3 times, so the result is not a one-off.
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 2.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
Topics (from GitHub)
asyncbashcommand-line-interfacecommand-line-toolgithacktoberfestrustterminaltui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gitui)Questions
- Does gitui run?
- Yes. gitui runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test gitui?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2fa693cb6ed4. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test gitui?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gitui take to install?
- 2.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 gitui need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gitui?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for gitui?
- 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.