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

This is the beginning of the README. Read the rest at the original. Read the full README ↗