Credentials. The provider key is stored globally for the OS user, so do not place it in a repository or in shared configuration files.
Who it is forA developer who has been asked to change a feature in a codebase they do not know and does not know the file or function names.
The problemKeyword search needs an exact identifier, and reading many files to guess where logic lives costs time and context.
The outcomeA ranked set of original source excerpts with paths and line numbers that point to the code handling the behavior.
What you need first
- Node.js 24
- npm
- An API key for TypeSafe AI, Vercel AI Gateway or OpenRouter
- Permission to send eligible source excerpts from the target repository to the chosen provider
Steps
- Run
npm install -g @nassim-arifette/jevgrep - Run
jevgrep init --global - Run
cd path/to/my-projectand thenjevgrep init, answeringyonly after you have reviewed the scope - Run
jevgrep inspectto confirm which files are eligible and what is excluded - Run
jevgrep search --query "Where is session expiry handled?"
Prompt for your agent
Using the JevGrep CLI in the repository at <repo path>, run `jevgrep search --query "<behavior question>"` and list each returned excerpt with its path and line range. Verify that the result reports complete coverage before treating an empty or short result as meaningful.
Caveat. Eligible source fragments are sent to the configured provider, and the search is not a substitute for exact tools such as rg when you already know the symbol.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for nassim-arifette/jevgrep and "Find where a behavior lives in an unfamiliar repo"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer