codegraph vs gitnexus
Local code knowledge graphs for AI-assisted exploration
codegraph and gitnexus index code into knowledge graphs that help developers and AI agents explore relationships, trace calls, and assess changes. codegraph emphasizes a locally maintained SQLite index and MCP or CLI access, while gitnexus also offers browser-based exploration and repository grouping.
codegraph: Give Coding Agents a Local Code Knowledge Graph
CodeGraph builds and maintains a local graph of code structure so AI coding agents can retrieve relevant source, call paths, and change impact without exploring files one by one. It connects to multiple agents through MCP and supports many languages.
gitnexus: Map Codebases for AI Agents with Knowledge Graphs
GitNexus builds a codebase knowledge graph with LadybugDB and Tree-sitter, then exposes it through MCP tools for AI coding agents. Use its local CLI for ongoing development or its browser UI for quick repository exploration.
| codegraph | gitnexus | |
|---|---|---|
| Language | C | TypeScript |
| License | MIT | — |
| Stars | 73.1k | 175 |
| Forks | 4.7k | 16 |
| Last analyzed | Oct 3, 2026 | Oct 22, 2026 |
Key differences
- codegraph stores its index locally in SQLite and watches files for incremental updates; gitnexus offers local CLI indexing and a browser UI, with browser capacity limited by available memory unless using backend mode.
- codegraph lists C as its project language and has an MIT license; gitnexus lists TypeScript and reports `NOASSERTION` metadata, while its README displays a PolyForm Noncommercial license badge.
- codegraph supports MCP and CLI queries for source, call paths, impact, and affected tests; gitnexus adds visual graph exploration, repository chat, and generated agent skills and context files.
- gitnexus supports repository groups for cross-repository contract and impact analysis; codegraph describes indexing and querying a project’s code structure.
- The provided project facts list 73.1k stars and 4.7k forks for codegraph, compared with 173 stars and 16 forks for gitnexus.
Choose codegraph if you…
- want a local SQLite graph that stays current through file watching and incremental sync.
- need CLI commands for tracing callers and callees, checking impact, or finding affected tests.
- prefer an MIT-licensed project and are prepared to initialize each project you want indexed.
Choose gitnexus if you…
- want a browser UI for visual graph exploration and repository chat.
- need repository grouping to inspect cross-repository contracts and impact.
- want generated agent skills and context files, and can verify the licensing terms for your use.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.