lazygit
simple terminal UI for git commands
Runssource: GitHubGoMITcommit 3f6be3b3ee7b
Go, MIT licensed. The project labels itself: cli, git and terminal.
lazygit runs. An Argusic agent installed it in 3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
lazygit builds, all 32 unit-test packages pass, all integration tests pass headlessly, and the TUI binary launches and runs on the 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 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.
- style tests fail under NO_COLOR=1 because gookit/color disables ANSI output when Enable=false5 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test ./... -short -count=1: 32/32 ok. go test ./pkg/integration/clients/... -run TestIntegration -count=1: all 210+ tests PASS in 70s
- Model tokens used
- 70,764
- Exact commit tested
- 3f6be3b3ee7b
- 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.
```text ``` tokens used 70,764 Here is the full accounting: **Install**: Downloaded Go 1.25.0 binary (the `go.mod` requires it). `go build` succeeded silently.… **Error encountered**: `NO_COLOR=1` is set in the container environment. The `gookit/color` library… **Unit tests**: All 32 packages pass (`go test ./... -short -count=1`). No failures. **Integration tests**: Full headless suite runs and passes — 210+ subtests across all categories (b… **Launch**: The TUI binary runs successfully. `timeout 5 /tmp/lazygit` under `script` starts, draws… ```text ```
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 3 minutes, faster than the median of the 24 comparable projects Argusic has measured.
- Recovered from all 1 error 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.
Of the 25 cli projects Argusic has installed and timed, lazygit was the 12th fastest to reach a running state, and 23 of 25 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 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lazygit)Questions
- Does lazygit run?
- Yes. lazygit runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test lazygit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3f6be3b3ee7b. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test lazygit?
- 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 lazygit take to install?
- 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 lazygit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lazygit?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does lazygit compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, lazygit was the 12th fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for lazygit?
- 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.