How to use Claude to reduce code lookup tokens
Indexio indexes a codebase and serves Claude Code lookups through MCP, falling back to regex when needed. Its authors report reduced token use but identify symbol-heavy workflows as a limitation.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
For [repository], evaluate Indexio as an MCP lookup tool for Claude Code. Index [scope], favor indexed discovery, and retain regex fallback. Compare [representative tasks] with built-in lookups, recording token usage and testing symbol-heavy queries separately.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- iohotspot
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The authors report about 50–60% lower token usage and near-instant lookups in their testing, while noting that symbol lookups can be weaker than regex.
- Human involvement
- The authors describe real-world comparative testing and a symbol-lookup limitation; they do not describe code review.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Observed Claude Code tool calls spending time on regex code searches.
- Investigated codebase indexing and built an internal database with MCP lookups.
- Added tool-call logic to favor indexed lookups, retaining regex fallback.
Indexio began with its authors watching Claude Code's built-in tool calls. They noticed substantial time going into regex searches for lines of code and investigated codebase indexing as an alternative. Their concern was that repeated regex results brought unnecessary data into the context window while the underlying files were mostly static.
They built Indexio to index a codebase into an internal database and return requested information through MCP. Getting sessions to use the indexed lookup required additional tool-call logic that attempts to override built-in lookup tools. When information is absent from the index, the system falls back to regex searches. The implementation is a single Rust binary.
The authors reported roughly 50–60% lower token usage in their real-world testing compared with built-in tools, alongside near-instant lookups rather than multiple seconds for each regex lookup. Those are the authors' results; the post supplies no detailed measurement procedure. They also identified a weakness: symbol lookups can work less well than regex, limiting the fit for symbol-heavy workflows. Who it's for: developers evaluating indexed code discovery for agents working repeatedly in an established codebase.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · iohotspot
Frequently asked questions
How does Indexio handle missing information?
The author says Indexio falls back to regex lookups when something is not in its index.
What token savings were reported?
The authors report about 50–60% lower token usage in their real-world testing against built-in tools. The post does not provide a detailed measurement procedure and notes weaker symbol lookups.
More details
Remaining steps
- Compared token usage and lookup behavior with built-in tools.
About this account
Claude Code performs code discovery through an MCP index when the tool-routing logic directs it there, with regex available as a fallback.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=50047627. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: iohotspot on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Indexio · MCP · Rust
Code search · MCP · Token usage
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.