jevgrep

Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.

Runssource: GitHubTypeScriptMITcommit baf2d1c4c719

TypeScript, MIT licensed. The project labels itself: ai sdk, claude code, cli, code search, codex, coding agents, context retrieval and developer tools.

jevgrep runs. An Argusic agent installed it in 25 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Project installs, builds, lints, type-checks, and all test suites pass cleanly. The jg CLI help screen and version command work. Provider-dependent tests skip gracefully without credentials.

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
3,251
forks
249
open issues
8
watchers
6
size
12 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.

Time lost to each failure while testing jevgrep, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • System Node.js 18.19.1 does not meet the >=22 requirement3 minutes
  • node --experimental-strip-types not supported in v22.0.02 minutes
  • bun not pre-installed in the container1 minute
Install time
25 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
bash scripts/test-suite.sh completed with 0 failures: bun test (42/42 pass, 28 skipped by design), bun test apps/cli/test (16/16 pass), bun test packages/core/test (30/30 pass), node --test provider-protocol.mjs (18/18 pass), node --experimental-strip-types --test parser tests (22/22 pass), node --test release.test.mjs (4/4 pass), python3 unittest swebench (27/27 pass). Built CLI binary reports version 0.4.2
Model tokens used
55,469
Exact commit tested
baf2d1c4c719
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.

- **Bun install**: `bun install --frozen-lockfile` completed with 40 packages.
- **Build**: `bun run build` produced the CLI binary; version `0.4.2`.
- **Lint**: 0 warnings, 0 errors across all packages.
- **Type checks**: Passed for both `@repo/core` and `@dzhng/jevgrep`.
- **Full test suite**: All 126+ tests pass (bun tests, node native tests, parser tests, release tes…
- **No mocks needed**: The project handles missing provider credentials gracefully via test skippin…
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": 25, "errors": [{"msg": "Sy…
tokens used
55,469

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 25 minutes.
  • Recovered from all 3 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.07
Argusic Runner1/3Runs with mocks92.000.08

Topics (from GitHub)

ai-sdkclaude-codeclicode-searchcodexcoding-agentscontext-retrievaldeveloper-toolsjevsemantic-searchtypescriptvercel-ai-gateway

Embed the badge

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

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

Questions

Does jevgrep run?
Yes. jevgrep runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test jevgrep?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit baf2d1c4c719. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test jevgrep?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jevgrep take to install?
25 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 jevgrep need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jevgrep?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for jevgrep?
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