navi
An interactive cheatsheet tool for the command-line
Runssource: GitHubRustApache-2.0commit f7330b9ad5bd
Rust, Apache-2.0 licensed. The project labels itself: bash, cheatsheets, cli, command line, rust, shell, snippet and snippets.
navi runs. An Argusic agent installed it in 60 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
navi builds from source, passes all 26 Rust unit tests, and its core cheatsheet query, info, widget generation, tldr integration, and cheatsh integration produce correct output when run with a controlling terminal.
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 92.2 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.
- No Rust toolchain available10 minutes
- tmux missing — required by integration test5 minutes
- Interactive 3rd-party tests fail without a PTY (failed to open /dev/tty)5 minutes
- fzf missing — navi requires it for interactive selection3 minutes
- tealdeer missing — required for tldr integration2 minutes
- wget missing — required for cheat.sh integration2 minutes
- Install time
- 60 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cargo test: 26 passed, 0 failed; bash test suite inside tmux: 27 tests passed; navi --print --best-match on cheats, tldr, and cheatsh all return correct output
- Model tokens used
- 571,940
- Exact commit tested
- f7330b9ad5bd
- 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.
| 1 | No Rust toolchain in container | Installed via `rustup` (curl sh.rustup.rs) | 10 | | 2 | fzf not installed — required by navi at runtime | Cloned junegunn/fzf, installed binary to `~… | 3 | tmux not installed — required by integration test | Downloaded tmux + libevent/libutempter `.… | 4 | tealdeer missing — required for tldr integration | `cargo install tealdeer --version 1.7.3 --… | 5 | wget missing — required for cheat.sh integration | Extracted from `apt-get download wget` | 2… | 6 | Interactive tests (3rd-party tldr, cheatsh, integration) need a PTY — fail with "failed to op… **test_depth**: `tier1_real` - `cargo test` output: `test result: ok. 25 passed; 0 failed`, `test result: ok. 1 passed; 0 failed` - Bash integration suite run inside tmux PTY: 27 tests pass (19 cases + 1 info + 5 widget + 2 third… - Direct CLI verification: `navi --query 'trivial case' --best-match --print` prints `echo "foo"`, … **verified_how**: `cargo test` exited 0 with 26 passed; bash test suite inside tmux PTY exited 0 wi… **final_state**: navi builds from source, passes all 26 Rust unit tests, and its core cheatsheet qu…
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.
- Recovered from all 6 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 Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 60 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
Of the 5 bash projects Argusic has installed and timed, navi was the 5th fastest to reach a running state, and 4 of 5 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.
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 with mocks | 88.67 | 0.09 | |
| Argusic Runner | 2/3 | Runs | 100.00 | 0.19 | |
| Argusic Runner | 1/3 | Runs with mocks | 88.00 | 0.15 |
Topics (from GitHub)
bashcheatsheetsclicommand-linerustshellsnippetsnippetsterminal
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/navi)Questions
- Does navi run?
- Yes. navi runs. Argusic installed and launched it on a clean machine in 60 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test navi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f7330b9ad5bd. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test navi?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does navi take to install?
- 60 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 navi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing navi?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does navi compare with the alternatives?
- Of the 5 bash projects Argusic has installed and timed, navi was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for navi?
- 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.