Most AI coding agents navigate a repo by grepping text or fuzzy-matching embeddings — which is exactly why they miss dependencies, break call chains, and confidently ship edits that ripple somewhere they never looked. GitNexus swaps that guesswork for a real graph: it parses your codebase with Tree-sitter and records every dependency, call chain, cluster, and execution flow as explicit, queryable relationships an agent can traverse.
What Sets It Apart
- Structure, not descriptions. Where tools like DeepWiki summarize what code does, the graph tracks how every symbol actually connects — so an agent can answer "what breaks if I change this?" instead of paraphrasing a file.
- Built for the agent, not just the human. The CLI indexes locally and exposes the graph over MCP to Cursor, Claude Code, Codex, Windsurf and more; Claude Code even gets hooks that inject graph context into searches and flag a stale index after commits.
- Levels the model playing field. Feeding smaller models full architectural context lets them reason about a codebase closer to how frontier models do — the leverage is in the retrieved structure, not raw parameter count.
- Two front doors. A globally installed CLI for daily development, or a zero-install browser app (Tree-sitter + LadybugDB compiled to WASM) that runs entirely client-side for quick exploration and demos.
Who It's For
Great fit if you drive an AI agent through a large or unfamiliar codebase every day and are tired of it losing the thread across files — the CLI + MCP path is where the payoff lives. Look elsewhere if you just want prose documentation (DeepWiki-style) rather than a queryable graph, or if browser mode is your only plan: it caps around ~5k files on browser memory unless you run the local backend. Note the OSS license is PolyForm Noncommercial, so commercial use needs the enterprise offering from Akon Labs.
