nervx: CLI tool reduces Claude Code token usage by analyzing codebase structure

What nervx does
nervx is a CLI tool (pip installable) that addresses Claude Code's inefficient codebase navigation. The developer built it after observing Claude would perform excessive grep searches (60+ times for simple queries) and re-read files, consuming half the context window before starting real work.
How it works
The tool parses your entire repository with tree-sitter, builds a SQLite graph of every function, class, call chain, and import, then generates a NERVX.md file containing a structural map of your project. This map includes entry points, execution flows, hot files, and fragile code.
The key feature: running nervx build . automatically adds instructions to your CLAUDE.md file that teach Claude how to use nervx. Claude then runs nervx nav on its own before grepping, checks blast radius before refactoring, and generally navigates more efficiently without manual prompting.
Technical details
- No MCP server configuration required
- No API keys needed
- No LLM calls during build process
- Pure tree-sitter + git implementation
- Builds in under 5 seconds
- Zero LLM cost for the analysis
Performance results
Tested on a FastAPI repository with the same 3 questions:
- Tool calls: 93 → 56 (-40%)
- Output tokens: 15,694 → 8,196 (-48%)
- Grep searches: 63 → 22 (-65%)
Additional features
- Catches dead code
- Flags functions where callers disagree on error handling
- Detects patterns like factories and event buses from graph shape
- Includes visualization for the generated graph
- Supports Python, JS/TS, Java, Go, Rust, C/C++, C#, Ruby
Why it's different
The developer specifically avoided approaches that use LLMs to generate graphs or require MCP setup, focusing instead on pure static analysis to avoid adding more token usage to solve the token waste problem.
📖 Read the full source: r/ClaudeAI
👀 See Also

2-Prompt System to Carry Context Between Claude Chats Without Token Waste
A developer shares two prompts for compressing an entire Claude conversation into a structured context block and loading it into a fresh chat, preserving decisions, work, and next steps.

Why Your Claude Code UI Output Drifts and How a Structured Spec Fixes It
A developer explains that inconsistent UI output from Claude Code isn't a prompt problem — it's a format problem. Providing exact hex codes, font weights, spacing, screen states, and transitions eliminates drift. They also open-sourced an MCP server that converts screen recordings into structured specs.

Claude Code's Monitor tool pipes dev server logs into AI-driven auto-fixes
Claude Code's Monitor tool lets you run a dev server in background, tail logs with smart grep filters, and have Claude auto-detect errors, write fixes, and commit them — all while you test the UI.

Open Source Knowledge Base Server and Multi-Agent Orchestrator for Persistent AI Memory
A developer built a custom MCP server on a private VPS to give Claude, Codex, and Gemini persistent memory across sessions, with a knowledge base server that ingests Obsidian vaults and a multi-agent orchestrator called Daniel for failover.