abhigyanpatwari / GitNexus

GitNexus ⚠️ Important Notice:** GitNexus has NO official cryptocurrency, token, or coin. Any token/coin using the GitNexus name on Pump.fun or any other platform is **not affiliated with, endorsed by, or created by** this project or its maintainers. Do not purchase any cryptocurrency claiming association with GitNexus. Join the official Discord to discuss ideas, issues etc! **Building nervous system for agent context.** Indexes any codebase into a knowledge graph — every dependency, call chain, cluster, and execution flow — then exposes it through smart tools so AI agents never miss code. https://github.com/user-attachments/assets/172685ba-8e54-4ea7-9ad1-e31a3398da72 > *Like DeepWiki, but deeper.* DeepWiki helps you *understand* code. GitNexus lets you *analyze* it — because a knowledge graph tracks every relationship, not just descriptions. **TL;DR:** The **Web UI** is a quick way to chat with any repo. The **CLI + MCP** is how you make your AI agent actually reliable — it gives Cursor, Claude Code, and friends a deep architectural view of your codebase so they stop missing dependencies, breaking call chains, and shipping blind edits. Even smaller models get full architectural clarity, making it compete with goliath models. --- Star History Two Ways to Use GitNexus | | **CLI + MCP** | **Web UI** | | ----------------- | -------------------------------------------------------------- | ------------------------------------------------------------ | | **What** | Index repos locally, connect AI agents via MCP | Visual graph explorer + AI chat in browser | | **For** | Daily development with Cursor, Claude Code, Windsurf, OpenCode, Codex | Quick exploration, demos, one-off analysis | | **Scale** | Full repos, any size | Limited by browser memory (~5k files), or unlimited via backend mode | | **Install** | | No install —gitnexus.vercel.app | | **Storage** | LadybugDB native (fast, persistent) | LadybugDB WASM (in-memory, per session) | | **Parsing** | Tree-sitter native bindings | Tree-sitter WASM | | **Privacy** | Everything local, no network | Everything in-browser, no server | > **Bridge mode:** connects the two — the web UI auto-detects the local server and can browse all your CLI-indexed repos without re-uploading or re-indexing. --- CLI + MCP (recommended) The CLI indexes your repository and runs an MCP server that gives AI agents deep codebase awareness. Quick Start That's it. This indexes the codebase, installs agent skills, registers Claude Code hooks, and creates / context files — all in one command. To configure MCP for your editor, run once — or set it up manually below. MCP Setup auto-detects your editors and writes the correct global MCP config. You only need to run it once. Editor Support | Editor | MCP | Skills | Hooks (auto-augment) | Support | | --------------------- | --- | ------ | -------------------- | -------------- | | **Claude Code** | Yes | Yes | Yes (PreToolUse + PostToolUse) | **Full** | | **Cursor** | Yes | Yes | — | MCP + Skills | | **Windsurf** | Yes | — | — | MCP | | **OpenCode** | Yes | Yes | — | MCP + Skills | | **Codex** | Yes | — | — | MCP | > **Claude Code** gets the deepest integration: MCP tools + agent skills + PreToolUse hooks that enrich searches with graph context + PostToolUse hooks that auto-reindex after commits. Community Integrations | Agent | Install | Source | |-------|---------|--------| | pi | | pi-gitnexus | If you prefer manual configuration: **Claude Code** (full support — MCP + skills + hooks): **Cursor** ( — global, works for all projects): **OpenCode** ( ): **Codex** ( for system scope, or for project scope): CLI Commands What Your AI Agent Gets **7 tools** exposed via MCP: | Tool | What It Does | Param | | ------------------ | ----------------------------------------------------------------- | -------------- | | | Discover all indexed repositories | — | | | Process-grouped hybrid search (BM25 + semantic + RRF) | Optional | | | 360-degree symbol view — categorized refs, process participation | Optional | | | Blast radius analysis with depth grouping and confidence | Optional | | | Git-diff impact — maps changed lines to affected processes | Optional | | | Multi-file coordinated rename with graph + text search | Optional | | | Raw Cypher graph queries | Optional | > When only one repo is indexed, the parameter is optional. With multiple repos, specify which one: . **Resources** for instant context: | Resource | Purpose | | ----------------------------------------- | ---------------------------------------------------- | | | List all indexed repositories (read this first) | | | Codebase stats, staleness check, and available tools | | | All functional clusters with cohesion scores | | | Cluster members and details | | | All execution flows | | | Full process trace with steps | | | Graph schema for Cypher queries | **2 MCP prompts** for guided workflows: | Prompt | What It Does | | ----------------- | ------------------------------------------------------------------------- | | | Pre-commit change analysis — scope, affected processes, risk level | | | Architecture documentation from the knowledge graph with mermaid diagrams | **4 agent skills** installed to automatically: • **Exploring** — Navigate unfamiliar code using the knowledge graph • **Debugging** — Trace bugs through call chains • **Impact Analysis** — Analyze blast radius before changes • **Refactoring** — Plan safe refactors using dependency mapping **Repo-specific skills** generated with : When you run , GitNexus detects the functional areas of your codebase (via Leiden community detection) and generates a file for each one under . Each skill describes a module's key files, entry points, execution flows, and cross-area connections — so your AI agent gets targeted context for the exact area of code you're working in. Skills are regenerated on each run to stay current with the codebase. --- Multi-Repo MCP Architecture GitNexus uses a **g…