dzhng / jevgrep
git clone https://github.com/dzhng/jevgrep.git
v0.8.0 · 19d ago
Find code by asking what it does. A CLI for coding agents that uses Jev to discover relevant files and source context.
—
stars, 24h
—
stars, 7 days
+2.8k
stars, 30 days · #120
2.8k
★ total
211
forks · 7 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguageTypeScript
LicenseMIT
Created2026-09-26 (24d ago)
Last pushtoday
Watchers5
OwnerUser
GitHub topics
ai-sdkclaude-codeclicode-searchcodexcoding-agentscontext-retrievaldeveloper-toolsjevsemantic-searchtypescriptvercel-ai-gateway
Links
- GitHub: github.com/dzhng/jevgrep
- Releases · Issues · Hacker News mentions
README excerpt
# jevgrep **Same intelligence. ~30% lower cost.** Find code by asking what it does. In our ten-task SWE-bench comparison, Jevgrep successfully completed the same 8 of 10 tasks as the baseline, at lower cost. Coding agents spend part of every unfamiliar task finding the right files. Jevgrep gives them a place to start: ask a repository question, and `jg` returns relevant files, reading leads, and verbatim source excerpts in one stdout response. It uses Jev to judge relevance across folders, files, and declarations. Your coding agent then implements and tests the change. [code] 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**. No separate Python, Bun, or ripgrep installation is required to use `jg`. ## Install the agent skill — required for agent setup Installing the CLI alone does not teach your coding agent to use it. **Install the skill as well**, from the project where your agent works: [code] The installer detects your coding agents (Claude Code, Codex, OpenCode and others) and asks where to install. Add `--global` for a user-wide install, or `--yes` for unattended installation. The skill explains installation, invocation and the meaning of returned context. It leaves research and implementation decisions to the calling agent. The current repository skill checks for `jg` and installs the CLI if it is missing; authentication still needs your selected provider’s key. The skill installer itself does not configure credentials. `jg skill` installs the `jevgrep` skill from the repository's `main` branch using a pinned skills CLI, with npm lifecycle scripts disabled. Skill installation needs Node 22.20+ and npm/npx plus network access for the installer. Rerun `jg skill` to get the current skill without waiting for a new npm release. ### Upgrade There is currently no `jg upgrade` command. Upgrade the CLI with npm: [code] After updating the CLI, refresh the installed skill by rerunning `jg skill`. Updating the npm package does not overwrite skill files in your projects. The installer records the GitHub source and skill path in `skills-lock.json`; rerun `jg skill` on another machine or after changing your Node installation. See the package guide for authentication details. ## Start with a question, leave with source Use `jg` when you know the behavior you need to understand but not where it lives: [code] Jevgrep explores the repository hierarchy and follows qualifying branches. It selects files using content previews, then identifies useful source units and surrounding context. It keeps qualifying file locations even when it cannot confidently return an excerpt; it does not force every search into a fixed top-two list. The summary and compact file list come first, followed by selected source with line references, then detailed declaration and call locations. Python, TypeScript/JavaScript, Go and Rust support declaration parsin