Jev.nvim

It finds things a regex cannot, because it judges each function as text instead of matching a pattern. The demo's own point is that grep is shaped like the language: one idea appeared as five syntaxes across twelve files and the regex caught five hits and none of the rest. The cost is scope, since it judges one function at a time and a question about how two functions interact returns the wrong list.

No, and the repo says so. The clip renders against the plugin's test fake so it runs from a clean clone, which makes the numbers fixtures rather than measurements, and demo/README.md lists exactly what is staged for the camera and what is not. The accuracy table in the README is deliberately blank, and opts.threshold is described as a starting point rather than a result.

Input is $0.042 per MTok and output is free, and the plugin prints its estimate before sending anything: the 48-function fixture corpus is about 13,000 tokens and $0.0005. Above confirm_above functions, 200 by default, a glob asks first. That number is arithmetic over the estimator's own token count rather than a measurement, so it holds whatever endpoint you point at.

Both. An optional second argument is a glob with vim.fn.glob() semantics, a visual range narrows the run to the functions the range overlaps, and :Jev! skips the confirmation on a wide glob. Glob files are read with readfile rather than loaded into a second buffer, each function payload is trimmed to 3,450 characters, and a session cache keyed on a hash of the question plus unit source means re-asking an edited buffer pays only for what changed.

Seven today: lua, python, rust, go, javascript, typescript and tsx, and anything else gets one message and no request. You need Neovim 0.10+, curl, a Treesitter parser for the language you are asking about, and TYPESAFE_API_KEY. The model defaults to jev-1.13.0 because the threshold was measured against it.

Every error path fails open: no key, no curl, no parser, a timeout or a 500 prints one message and leaves you where you were. A request rejected as over budget is bisected and both halves requeued, and a single unit too big for one request has its source halved once and then gives up rather than looping.

Phrase it positively. The README says negated questions read badly and that noul(X) plus noul(not X) is not guaranteed to be 1, so ask for functions that swallow an exception rather than functions that do not handle errors. Rust and Go have no exceptions, so an exception-shaped question asks those two something slightly different from what it asks Python.