GitNexus does something I didn't think was practical yet: it builds a full code knowledge graph in your browser. No server. No uploads. Your code never leaves your machine. And it uses Graph RAG to let you query that knowledge graph in natural language.
Let me explain why this matters more than it sounds.
Code understanding is one of the hardest problems in software engineering. Not writing code - understanding existing code. Every developer who's joined a new team or inherited a legacy codebase knows the pain. You spend weeks reading files, tracing call chains, building a mental model of how everything connects. It's slow, error-prone, and the mental model starts decaying the moment you build it.
Knowledge graphs are the right data structure for this problem. Code is fundamentally a graph - functions call other functions, modules import modules, types reference types, configurations affect behavior. A flat text search or even a vector database loses the relational structure that makes code comprehensible.
GitNexus builds this graph automatically. Point it at a repository and it parses the code, extracts entities (functions, classes, modules, APIs), identifies relationships (calls, imports, inherits, configures), and constructs a queryable knowledge graph. The Graph RAG layer lets you ask questions like "what happens when a user signs up?" and get answers that trace through the actual code paths, not just surface-level keyword matches.
The client-side part is what really got my attention. Most code analysis tools require you to upload your code to a server. That's a non-starter for a lot of teams. Enterprise code. Proprietary algorithms. Code under NDA. The security and compliance overhead of sending your source code to a third party kills adoption before it starts.
GitNexus avoids this entirely by running in the browser. WebAssembly handles the parsing. IndexedDB stores the graph. A local embedding model handles the semantic layer. Your code literally never leaves your machine. For security-conscious organizations, this is the difference between "we can use this" and "absolutely not."
The technical achievement here is real. Building and querying a knowledge graph with thousands of nodes and edges, running semantic search, and doing graph traversal - all in a browser tab. Five years ago this would have been impossible. WebAssembly performance, browser storage improvements, and efficient small models have converged to make it feasible.
I tested it on a mid-sized TypeScript project (about 200 files) and the experience was genuinely useful. The graph visualization alone - seeing how modules connect, where the complexity clusters, which files are central and which are peripheral - gave me insights that would have taken hours of manual exploration.
The Graph RAG queries are the killer feature though. Being able to ask "how does the payment flow work?" and get a traced answer that references specific files and functions, with the graph path visible - that's a step change in code comprehension tooling.
Some observations on where this is heading:
Onboarding. New team members could get up to speed on a codebase in hours instead of weeks. Point GitNexus at the repo, start asking questions.
Code review. Understanding the blast radius of a change is a graph problem. GitNexus could show you exactly what's affected by a modification.
Architecture documentation. The knowledge graph itself is a form of always-up-to-date documentation. No more stale architecture diagrams.
Refactoring. Understanding dependency chains is critical for safe refactoring. A knowledge graph makes implicit dependencies explicit.
The client-side constraint is both a limitation and a strength. You won't process million-line monorepos in a browser. But for the vast majority of repositories, it's more than sufficient, and the privacy benefit is worth the tradeoff.
GitNexus is pointing at a future where code understanding is augmented by default. Not as an optional add-on, but as a fundamental part of how we interact with codebases. That future can't come soon enough.