jevgrep
Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.
Runs with mockssource: 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, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Repository builds, types check, lints clean. All 4 test suites pass (70 pass, 0 fail). End-to-end CLI search works against a mock provider: auth saves credentials, doctor verifies access, search returns file locations and source excerpts.
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
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 third-party provider API key for Jev (Vercel/TypeSafe/OpenRouter/OpenCode)2 minutes
- Node.js version too old (v18, requires 22+)1 minute
- No bun binary in PATH (npm-installed bun is musl-linked, incompatible with glibc Ubuntu)1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- bun test: 34 pass, 54 skip, 0 fail (88 tests, 14 files); node --test parser tests: 22 pass, 0 fail; node --test provider-protocol: 18 pass, 0 fail; node --test release: 4 pass, 0 fail; jg doctor (against mock): 'Jev connection verified through Vercel AI Gateway'; jg 'find functions' /tmp/jg-test returned 1 relevant file with source excerpt
- Model tokens used
- 94,390
- 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
- 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.
succeeded in 0ms: start_epoch=1791088181 now_epoch=1791088537 Total wall minutes: 5 exec /bin/sh -lc '# Ensure mock is killed pkill -f "python3 /tmp/mock-provider.py" 2>/dev/null || true' in /work/repo exited 143 in 0ms: The mock should be cleanly stopped now. Here's the ARGUSIC result. tokens used 94,390 The mock should be cleanly stopped now. Here's the ARGUSIC 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 6 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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.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.
[](https://argusic.com/subject/jevgrep)Questions
- Does jevgrep run?
- jevgrep runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 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. One attempt is 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.08: 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?
- 6 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?
- 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.