Does vim-anywhere run?

vim-anywhere runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test vim-anywhere?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 724bcc4f8f84. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test vim-anywhere?

The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does vim-anywhere take to install?

1.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 vim-anywhere need a GPU?

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

What goes wrong when installing vim-anywhere?

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

Where is the evidence for vim-anywhere?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

vim-anywhere

Use Vim everywhere you've always wanted to

Runs with mockssource: GitHubShellMITcommit 724bcc4f8f84

Shell, MIT licensed. The project labels itself: keyboard shortcuts, osx, shell, text editor and vim.

vim-anywhere runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

All 18 BATS tests pass: 8 install tests (macOS mvim present/missing, Linux gvim/xclip missing, unsupported OS, requires git), 5 run tests (temp dir creation, .path/mvim failure, clipboard copy, custom vimrc), 5 uninstall tests (macOS path/workflow removal, missing path, Linux gsettings/gconftool).
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 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.12 (measured)
recorded runs: 1
last tested: 2026-09-30
stars: 3,769
forks: 145
open issues: 43
watchers: 39
size: 0 MB
created: 2013-12-29
last push: 2026-05-02

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-30. 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: 2 minutes
Cold machine to finish: 34 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: bats test/ exited 0, 18/18 tests passed
Model tokens used: 931,383
Exact commit tested: 724bcc4f8f84
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

ok 17 uninstall: removes gsettings binding on Linux
ok 18 uninstall: uses gconftool when available on Linux
=== Checking if bin/run would work on Linux ===
=== Checking script permissions ===
-rwxr-xr-x 1 runner runner 2042 Sep 30 19:15 bin/run
-rwxr-xr-x 1 runner runner 4028 Sep 30 19:15 install
-rwxr-xr-x 1 runner runner 1195 Sep 30 19:15 uninstall
-rwxr-xr-x 1 runner runner  974 Sep 30 19:15 update
The test suite passed on first run with no errors. Let me compile the final result.
tokens used
931,383
The test suite passed on first run with no errors. Let me compile the final result.

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

Installed in 1.5 minutes.
Nothing broke on the way: zero errors between clone and running.
Licensed MIT, as reported by its host.

What did not, or is not known

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

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	1/3	Runs with mocks	92.00	0.12	2026-09-30 19:49 UTC

Topics (from GitHub)

keyboard-shortcuts osx shell text-editor vim

Embed the badge

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

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

Questions

Does vim-anywhere run?: vim-anywhere runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test vim-anywhere?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 724bcc4f8f84. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test vim-anywhere?: The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does vim-anywhere take to install?: 1.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 vim-anywhere need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing vim-anywhere?: Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for vim-anywhere?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.