Jev Code Finder

A Rust CLI that searches code by meaning with TypeSafe Jev. You describe a concept in plain English and it returns relevant files, line ranges, confidence scores and source snippets - so a query like 'where are permissions enforced?' can find middleware and guards without knowing their exact names.

It walks the repository respecting .gitignore, asks Jev to score each source path, opens only paths meeting --file-threshold (default 0.25), splits them into overlapping size-bounded windows, then sends those windows in bounded batches and prints matches over --threshold, default 0.55.

Homebrew: brew tap Peu77/tap followed by brew install --HEAD jev-code-finder. From source: clone the repository and run cargo install --path . Rust 1.88 or newer is required, and the included rust-toolchain.toml selects the correct version when using rustup.

A TypeSafe API key, network access to https://api.typesafe.ai, and Rust 1.88 or newer. The README says to export TYPESAFE_API_KEY in the environment and never commit it or pass it as a command-line argument; it publishes no usage-cost figures.

Transient network errors, HTTP 408 and 429 responses, server errors and invalid responses are retried up to three times with exponential backoff of 250 milliseconds, 500 milliseconds, then 1 second. Permanent client errors fail immediately, and --parallelism defaults to 10 concurrent scanning requests.

Yes: cargo run -- "how are failed payments retried?" --path . runs it from the repository. The README also offers an agent skill via npx skills add Peu77/JevFind --skill jev-code-finder for coding-agent workflows.

A colored file tree updating in place: symbols mark pending files, files being scored, paths below --file-threshold, scans with no match, files with matches and files not readable as UTF-8. Completed files show path-relevance percentages; matches also show the strongest window percentage.