jevgrep vs zvec-grep
Find code by asking what it does: `jg` uses the Jev decision model to judge folders, files and declarations, returning relevant files plus verbatim excerpts for coding agents. CLI + skill. — versus — zg: ripgrep, BM25 and vector search behind one local-first CLI for humans and agents — index a workspace once, search code, docs and data by meaning, then verify with exact text or regex.
Both are grep-shaped CLIs that search a codebase by meaning; zvec-grep is local BM25 + vectors after an index pass, jevgrep a hosted decision model walking the tree per question.
| jevgrep | zvec-grep | |
|---|---|---|
| Stars | 2.6k | 4.0k |
| Forks | 189 | 234 |
| Language | TypeScript | TypeScript |
| License | MIT | Apache-2.0 |
| Last activity | 9 days ago | 3 days ago |
| Topics | code-intel, coding | code-intel, rag, local |
| Curated connections | 3 | 6 |
jevgrep — the curator's take
Use it when your agent lands in an unfamiliar repo and burns turns grepping for where a behavior lives — no index to build, and measured ~26% lower total cost at the same solve rate on its own 10-task SWE-bench run. Skip it when you already know the symbol or path (plain `rg` wins), or when you want zero per-query spend: every search is a paid Jev call through Vercel AI Gateway, TypeSafe, OpenRouter or a compatible endpoint. Install the skill too, or agents won't call it.
zvec-grep — the curator's take
Give it to a coding agent that wastes tool calls grepping: `zg index` builds a local index (embeddings can stay local — potion-retrieval-32m is the default), then `zg query` returns ranked, source-linked results across code, Markdown and structured files, and the agent drops to exact/regex only to confirm. Fewer calls, fewer tokens, nothing leaves the machine unless you allow a remote embedder. Built on Alibaba's zvec engine; direct and server modes. NOT a symbol-aware tool — it doesn't know what a function is, only what text means — and NOT a graph: for call edges and blast radius use a code-intelligence server.