GitNexus

GitNexus indexes a codebase into a knowledge graph of symbols, calls, dependencies and execution flows. Use it through your coding agent's MCP tools, the CLI, or a web graph explorer.

Quick start · Documentation · Web UI · Discord

https://github.com/user-attachments/assets/172685ba-8e54-4ea7-9ad1-e31a3398da72

Quick start

Requires Node.js 22.18+ on 22.x, or 24.11+. See platform requirements for Linux and Windows native dependencies.

# Run from your repository root
npx gitnexus analyze

# Connect your editors once
npx gitnexus setup

analyze builds the index, installs agent skills, registers Claude Code hooks, and writes AGENTS.md / CLAUDE.md context files. setup configures MCP for your editors. Use gitnexus analyze --index-only to index without those repository integration files.

For repeated use, install globally with npm install -g gitnexus. If installation fails, see troubleshooting.

What you can do

Task	Tool
Find code and related execution flows	query
Inspect a symbol's callers and dependencies	context
Check what a change could affect	impact
Trace a path between two symbols	trace
Review the impact of a Git diff	detect_changes
Preview and apply a semantic rename	rename

Ask your agent questions such as “What calls this function?” or “What would this change affect?” Resolution depends on language support and available evidence; check reported ambiguity, index freshness and coverage limits.

Editor setup

gitnexus setup detects Claude Code, Cursor, Codex, Antigravity, Factory Droid, OpenCode, CodeBuddy and Qoder. Windsurf requires manual MCP configuration. To select editors:

gitnexus setup -c cursor,codex

See editor setup for the support matrix, manual MCP configuration, hooks and plugin installation.

Everyday commands

gitnexus analyze                 # Refresh the current repository's index
gitnexus analyze --watch         # Reindex as local files change
gitnexus query "authentication"  # Search the graph
gitnexus impact UserService --direction upstream
gitnexus status                  # Check index freshness
gitnexus list                    # List indexed repositories
gitnexus serve                   # Serve indexed repositories to the web UI

For multiple concurrent agents, use one gitnexus mcp --http --port 3111 server and connect clients to http://127.0.0.1:3111/mcp. See the shared-server instructions.

Web UI

Run gitnexus serve, then open gitnexus.vercel.app. The UI connects to the backend to browse indexed repositories and use AI chat. It uses the existing index; no re-upload or re-index is needed.

For Docker, hosted deployments, image verification, or a local frontend, see deployment.

Supported languages

C, C++, C#, COBOL, Dart, Go, Java, JavaScript, Kotlin, Objective-C, PHP, Python, Ruby, Rust, Swift, TypeScript, Vue and Zig have registered providers. Support varies by construct; see the language inventories for measured behavior, exclusions and remaining gaps.

Documentation

Read	For
CLI reference	Commands, indexing flags, watch mode, configuration and shared stores
Environment variables · vector tuning	Runtime settings and search tuning
MCP reference	All tools, resources, examples, policies and response budgets
Editor setup	Supported integrations and manual configuration
Deployment	Docker, Render, image signatures and local frontend setup
Wiki generation	Model configuration and generated repository documentation
Runbook	Index recovery, embeddings and operational troubleshooting
Architecture · type resolution	How the indexer and resolution layers work
Type-resolution roadmap	Planned work and acceptance criteria

Security and privacy

The CLI indexes code locally without an LLM. Optional remote embeddings, wiki generation and AI chat use the providers you configure. The web UI accesses the backend it connects to. Review security guidance and deployment authentication before exposing an index to other users.

Development

See CONTRIBUTING.md for setup and pull requests, TESTING.md for validation, and GUARDRAILS.md for repository rules.

Enterprise

GitNexus is available as an enterprise offering — fully managed SaaS or self-hosted deployment. Commercial use of the OSS version is also available with proper licensing.

Enterprise includes:

• PR Review — automated blast radius analysis on pull requests
• Auto-updating Code Wiki — always up-to-date documentation (Code Wiki is also available in OSS)
• Auto-reindexing — knowledge graph stays fresh automatically
• Multi-repo support — unified graph across repositories
• OCaml support — additional language coverage
• Priority feature/language support — request new languages or features

Upcoming: auto regression forensics · end-to-end test generation

👉 Learn more at akonlabs.com — for commercial licensing or enterprise inquiries, ping us on Discord or email founders@akonlabs.com

Community Integrations

Built by the community — not officially maintained, but worth checking out.

Project	Author	Description
pi-gitnexus	@tintinweb	GitNexus plugin for pi — pi install npm:pi-gitnexus
gitnexus-stable-ops	@ShunsukeHayashi	Stable ops & deployment workflows (Miyabi ecosystem)
KiloCode MCP workflow	@oktanishq	Guide to connect GitNexus MCP to Kilo Code and verify tools.

Have a project built on GitNexus? Open a PR to add it here!

License

PolyForm Noncommercial 1.0.0. Commercial licensing is available through akonlabs.com.

Acknowledgments

• Tree-sitter — AST parsing
• LadybugDB — embedded graph database with vector support (formerly KuzuDB)
• Sigma.js — WebGL graph rendering
• transformers.js — browser ML
• Graphology — graph data structures
• MCP — Model Context Protocol