jevgrep: CLI for Coding Agents to Find Relevant Code
jevgrep is a Node.js CLI that helps coding agents locate relevant files and source excerpts in a repository using Jev, reducing agent cost by about 30%. 2,054 GitHub stars in 7 days since dzhng/jevgrep was created (309.6/day). 1 source across 1 channel. Automatically detected; not yet reviewed.
49Fact cited ·Analysis our interpretation ·Estimate forward-looking · [n] links to the source
7 claims drafted by openai/gpt-oss-20b were kept because each quote was found verbatim in its source; 0 unverifiable claims were discarded. Statements marked AI await human review.
What happened
- Fact jevgrep is a CLI for coding agents that uses Jev to discover relevant files and source context[1]AI
A CLI for coding agents that uses Jev to discover relevant files and source context
- Fact It reduces coding-agent cost by roughly 30%[1]AI
Same intelligence. ~30% lower cost.
- Fact In a ten-task SWE-bench comparison, Jevgrep completed 8 of 10 tasks at lower cost[1]AI
In our ten-task SWE-bench comparison, Jevgrep successfully completed the same 8 of 10 tasks as the baseline, at lower cost.
- Fact It outputs a summary, file list, source excerpts, and declaration/call locations[1]AI
The summary and compact file list come first, followed by selected source with line references, then detailed declaration and call locations.
- Fact It supports declaration parsing for Python, TypeScript/JavaScript, Go, and Rust[1]AI
Python, TypeScript/JavaScript, Go and Rust support declaration parsing; other text uses a fallback.
- Fact The GitHub repository dzhng/jevgrep was created on 26 Sept 2026 and had 2,054 stars on 2 Oct 2026.[1]
- Fact Its description reads: “Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.”[1]
- Fact That is 2,054 stars in 7 days, an average of 309.6 per day.[1]
Why it matters
- Analysis Install the CLI via npm, add the agent skill to their project, and use jg to query repositories for relevant code snippetsAI
- Analysis Automatically detected from public activity data. Not yet reviewed by an analyst.
Should I care?
What changed?
Who is affected?
- Analysis Software developers using coding agents to navigate and modify codebasesAI
What can developers do with it?
- Analysis Install the CLI via npm, add the agent skill to their project, and use jg to query repositories for relevant code snippetsAI
Is it production-ready?
Insufficient evidence
Analysis Not assessed.
What would make it important?
Not yet assessed.
What could prevent adoption?
Not yet assessed.
Technical change
- Fact jevgrep is a CLI for coding agents that uses Jev to discover relevant files and source context[1]AI
A CLI for coding agents that uses Jev to discover relevant files and source context
- Fact It reduces coding-agent cost by roughly 30%[1]AI
Same intelligence. ~30% lower cost.
- Fact In a ten-task SWE-bench comparison, Jevgrep completed 8 of 10 tasks at lower cost[1]AI
In our ten-task SWE-bench comparison, Jevgrep successfully completed the same 8 of 10 tasks as the baseline, at lower cost.
- Fact It outputs a summary, file list, source excerpts, and declaration/call locations[1]AI
The summary and compact file list come first, followed by selected source with line references, then detailed declaration and call locations.
- Fact It supports declaration parsing for Python, TypeScript/JavaScript, Go, and Rust[1]AI
Python, TypeScript/JavaScript, Go and Rust support declaration parsing; other text uses a fallback.
Architecture
No architecture has been documented for this signal.
Developer impact
Developer implications have not been assessed yet.
Difficulty has not been estimated yet.
Adoption & momentum
No adoption indicators recorded.
Timeline
First seen by the Astrava pipeline[1]
Limitations & risks
- Fact Requires Node.js 22+ and a key for a supported AI provider[1]AI
Requires Node.js 22+, macOS, Linux, or Windows, and a key for Vercel AI Gateway, TypeSafe, OpenRouter, OpenCode Zen, or a custom TypeSafe-compatible endpoint.
- Fact No separate Python, Bun, or ripgrep installation is required, but the CLI must be installed[1]AI
No separate Python, Bun, or ripgrep installation is required to use jg.
- Analysis Generated from activity metrics only; verify the linked sources before acting on it.
Competing approaches
No competing approaches documented yet.
Who is building on it
No independent projects or organisations are documented as building on this yet.
Evidence & sources
Primary source (1)
Published by the people who built it: release notes, repositories, papers, official docs.
- [1]dzhng/jevgrep repository(opens in a new tab)
Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.
Secondary source (0)
Independent reporting, third-party benchmarks, integrations by other projects.
None recorded.
Community signal (0)
Discussion threads and social posts. Evidence of attention, not of correctness.
None recorded.
How the score of 49 was calculated
| Factor | Share of maximum | Points |
|---|---|---|
| NoveltyRubric level 2/4 (Moderate). Heuristic (automated): first published 7 days ago. | 7.5/15 | |
| Technical significanceRubric level 3/4 (High). AI-assisted (openai/gpt-oss-20b), pending human review: Provides a structured, AI-assisted repository search that integrates with coding agents, reducing cost and effort Evidence: “It uses Jev to judge relevance across folders, files, and declarations.” | 11.3/15 | |
| Developer relevanceRubric level 3/4 (High). AI-assisted (openai/gpt-oss-20b), pending human review: Directly enhances coding agent workflows by providing relevant code context, lowering development cost Evidence: “Use jg when you know the behavior you need to understand but not where it lives: Jevgrep explores the repository hierarchy and follows qualifying branches.” | 11.3/15 | |
| Adoption velocityIndependent integrations: unknown (0 pts). GitHub stars: 309.6 per day since creation; full marks at 1000/day, log-scaled (4.2/5). | 4.2/10 | |
| Community momentumFewer than three periods of activity data, or no baseline activity to compare against. | 0/10 | |
| Source credibilityPrimary source present; mean source-tier weight 1.00 (primary 1.0, secondary 0.7, community 0.35). | 10/10 | |
| Cross-source confirmationNo independent publisher has confirmed this yet. | 0/10 | |
| Evidence strengthMet 2/4: primary source ✓, runnable artifact (code, weights or package) ✓, reproducible or independent benchmark ?, technical documentation or paper ✗. 1 unknown (scored 0). | 5/10 | |
| Time to impactNo time-to-impact estimate yet. | 0/5 | |
| Hype penaltyNo hype indicators detected. | 0 | |
| Breakout Score | 49 |
Low confidence (0.48) — 60% of measured factors have data. 0 independent non-community publishers. At least one primary source. Evidence strength 5/10. Capped at Low: no independent, non-community source yet.
An analytical ranking derived from observable signals using model breakout-v1.2. It is not a prediction and not a measure of quality. How it works