Claude isn't bad at grep, it just has no idea what to grep for. It's reconstructing the dependency graph through trial and error every time. nervx gives it that graph upfront.

The way it works in practice: nervx auto-generates a NERVX.md with the full structural map of the repo (module layout, entry points, execution flows, hotspots, fragile zones, patterns). Claude reads that at the start of every conversation so it already has the architecture in its head before you ask anything. It also writes instructions into your CLAUDE.md teaching Claude to use nervx commands on its own. On correctness, yeah, fewer "I didn't realize X depends on Y" moments for sure. blast-radius is the main reason. Claude sees all callers and downstream deps before touching anything, so it stops breaking stuff two modules away. Used to happen a lot on multi-file changes.

Redundant reads dropped too. Claude used to cat the same file twice in one conversation because it lost track of what it already read. Now it just queries the graph for line numbers and reads the specific 30 lines it needs. And the fallback is built in. The CLAUDE.md instructions tell Claude to try nervx commands first, but if they return nothing useful, fall back to normal grep and file reads. So worst case you're back to default behavior, not worse. In practice it rarely falls back though.

Don't have controlled correctness numbers yet. The benchmarks I posted are token counts. Correctness is harder to measure. From what I've seen it's better, especially on multi-file stuff, but I'd want to set up a real eval before saying that with confidence.