I built Crux after watching coding agents waste context navigating large repos

I kept seeing the same problem when using coding agents on larger codebases:

• They grep through the repository repeatedly
• Open far more files than necessary
• Lose track of definitions and references
• Burn context before doing the actual work

So I built Crux, a code-intelligence tool designed for coding agents.

It provides on-demand access to:

• Symbol and definition search
• References
• Caller/callee graphs
• Fast navigation across large repositories

One question I’ve already received is: Does it run on every request and burn more tokens?

No. The coding agent decides when Crux is useful and calls it as needed. There’s a small baseline cost from exposing the tool definitions, but indexing and search results are only used when invoked. Simple tasks can stay simple; larger investigations and refactors can use Crux.

I’m now looking for developers willing to test it on real codebases.

I’d especially like feedback on:

• Which coding agent you use
• Your main language and repository size
• Where your agent struggles most with codebase navigation

Crux: https://github.com/pedr0v/crux

Happy to answer technical questions or hear brutally honest feedback.