gnvim
GUI for neovim, without any web bloat
Runssource: GitHubRustMITcommit 38b1037d90c9
Rust, MIT licensed. The project labels itself: gtk, gui, neovim, neovim guis, nvim, rust, text editor and ui.
gnvim runs. An Argusic agent installed it in 12.5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
GNvim builds from source, passes all 10 tests (2 UI + 8 nvim-rs), and launches successfully against nvim v0.13.0-dev nightly; the GTK4 window connects to Neovim via --embed RPC. The app is functional but lacks X11 DRI3 acceleration and D-Bus session bus in the headless container environment (cosmetic warnings only).
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.
- No Rust toolchain, GTK4/libadwaita dev packages, or Neovim available in the container8 minutes
- nvim binary (0.9.5 from apt) too old — README requires 0.10+, API not compatible1.5 minutes
- cargo build failed: glib-build-tools build script could not find glib-compile-resources1 minute
- libappstream.so.5 and libxmlb.so.2 missing from dev dir at runtime1 minute
- libyaml-0.so.2 missing at runtime0.5 minutes
- GSettings schema 'com.github.vhakulinen.gnvim.Devel' not installed0.5 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- Tests: 'cargo test -p gnvim' passed 2/2, 'cargo test -p nvim-rs' passed 8/8; launch: '/work/repo/target/debug/gnvim --version' printed 'gnvim 0.3.2-dev'; runtime test: timeout 15 gnvim --new --nvim /home/runner/gtk-devdeps/bin/nvim ran without panicking, exited cleanly on SIGTERM
- Model tokens used
- 502,293
- Exact commit tested
- 38b1037d90c9
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
nvim version:
NVIM v0.13.0-dev-2081+g5a53f3bb9e
Build type: RelWithDebInfo
LuaJIT 2.1.1793383622
Run "nvim -V1 -v" for more info
Now let me compile the final ARGUSIC_RESULT:
Here's the full report:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":12.5,"error…
tokens used
502,293
Here's the full report:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":12.5,"error…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 12.5 minutes.
- 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 MIT, as reported by its host.
- Measured 2 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.
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/gnvim)Questions
- Does gnvim run?
- Yes. gnvim runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test gnvim?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 38b1037d90c9. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test gnvim?
- The run that produced this verdict cost $0.37: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gnvim take to install?
- 12.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 gnvim need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gnvim?
- 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.
- Where is the evidence for gnvim?
- All 2 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.