zvec-grep

Local-first search across your workspace, built for humans and AI agents.

Runssource: GitHubRustApache-2.0commit 4c5b1a00402f

Rust, Apache-2.0 licensed. The project labels itself: ai agents, bm25, cli, code search, full text search, local first, mcp and ripgrep.

zvec-grep runs. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

zvec-grep (zg) builds and installs from source. All test suites pass except 2 IPv6-only tests that fail because the container lacks IPv6 loopback. The CLI binary is functional and responds to --help, --version, --rg search, and --status commands.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
2
last tested
stars
4,338
forks
268
open issues
95
watchers
14
size
77 MB
created
last push

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.

  • 2 tests fail on IPv6 EADDRNOTAVAIL for ::1 in container without IPv6 loopback (shutdown-origin.test.mjs)
Install time
2 minutes
Cold machine to finish
21 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm run build exits 0; node --test --test-concurrency=1 test/*.test.mjs: 373/375 pass; node --test --test-concurrency=1 test/unit/*.test.mjs: 276/276 pass; node --test --test-concurrency=1 test/integration/*.test.mjs: 39/39 pass; node --test --test-concurrency=1 test/e2e/*.test.mjs: 9/9 pass; node dist/cli/index.js --version returns 0.2.1; node dist/cli/index.js --rg -F zg README.md returns results
Model tokens used
187,858
Exact commit tested
4c5b1a00402f
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 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

  - Integration tests: 39 subtests, **39 pass**, 0 fail
  - E2E tests: 9 subtests, **9 pass**, 0 fail
  - Package tests: 1 subtest, **1 pass**, 0 fail
- **CLI verification**: `zg --version` returns `0.2.1`; `zg --rg -F "zg" README.md` returns search …
- **Only 2 failures**: Both in `test/shutdown-origin.test.mjs` — they try to bind to `::1` (IPv6 lo…
- **No real credentials needed**: Tests that reference API keys (Qwen, etc.) use proper mocking and…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [{"msg": "2 t…
tokens used
187,858

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 minutes, faster than the median of the 121 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 122 ai-agents projects Argusic has installed and timed, zvec-grep was the 30th fastest to reach a running state, and 94 of 122 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 2 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.09
Argusic Runner1/3Runs100.000.23

Topics (from GitHub)

ai-agentsbm25clicode-searchfull-text-searchlocal-firstmcpripgrepsemantic-searchvector-search

Embed the badge

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

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

Questions

Does zvec-grep run?
Yes. zvec-grep runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test zvec-grep?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4c5b1a00402f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test zvec-grep?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does zvec-grep take to install?
2 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 zvec-grep need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing zvec-grep?
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 zvec-grep compare with the alternatives?
Of the 122 ai-agents projects Argusic has installed and timed, zvec-grep was the 30th fastest to reach a running state, and 94 of 122 reached one at all.
Where is the evidence for zvec-grep?
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.

Discussion