Your codebase, understood.
CodeGraph transforms your entire codebase into a semantically searchable knowledge graph that AI agents can actually reason aboutβnot just grep through.
Ready to get started? Jump to the Installation Guide for step-by-step setup instructions.
Already set up? See the Usage Guide for tips on getting the most out of CodeGraph with your AI assistant.
AI coding assistants are powerful, but they're flying blind. They see files one at a time, grep for patterns, and burn tokens trying to understand your architecture. Every conversation starts from zero.
What if your AI assistant already knew your codebase?
Most semantic search tools create embeddings and call it a day. CodeGraph builds a real knowledge graph:
Your Code β AST + FastML β Graph Construction β Vector Embeddings
β β β
Functions Dependencies Semantic Search
Classes Call chains Similarity
Modules Data flow Context
When you search, you don't just get "similar code"βyou get code with its relationships intact. The function that matches your query, plus what calls it, what it depends on, and where it fits in the architecture.
CodeGraph doesn't return a list of files and wish you luck. It ships 8 agentic tools that do the thinking:
| Tool | What It Actually Does |
|---|---|
agentic_code_search |
Multi-step semantic search with AI-synthesized answers |
agentic_dependency_analysis |
Maps impact before you touch anything |
agentic_call_chain_analysis |
Traces execution paths through your system |
agentic_architecture_analysis |
Gives you the 10,000-foot view |
agentic_api_surface_analysis |
Understands your public interfaces |
agentic_context_builder |
Gathers everything needed for a feature |
agentic_semantic_question |
Answers complex questions about your code |
agentic_complexity_analysis |
Identifies high-risk code hotspots for refactoring |
Each tool runs a reasoning agent that plans, searches, analyzes graph relationships, and synthesizes an answer. Not a search resultβan answer.
View Agent Context Gathering Flow - Interactive diagram showing how agents use graph tools to gather context.
CodeGraph supports three agent backends selectable at runtime via CODEGRAPH_AGENT_ARCHITECTURE:
| Architecture | Description | Best For | Model Type |
|---|---|---|---|
rig |
Rig framework native orchestration | Fastest performance, deep analysis | Thinking/reasoning models (gpt-5.1, Claude 4.5 family, Grok 4.1 Fast Reasoning) |
react (default) |
ReAct-style single-pass reasoning | Quick queries, simple lookups | Basic Instruction following models |
lats |
Language Agent Tree Search | Complex problems requiring exploration | Works well with both |
Performance notes:
- Rig delivers the best performance with modern thinking/reasoning models. These models excel at multi-step tool orchestration and produce superior results for complex code analysis.
- ReAct remains the default for backward compatibility and works well with traditional instruction-following models.
- LATS uses tree search exploration, making it suitable for complex problems regardless of model type.
Agents can start with lightweight project context so their first tool calls are not blind. Enable via env:
CODEGRAPH_ARCH_BOOTSTRAP=trueβ includes a brief directory/structure bootstrap + contents of README.md and CLAUDE.md+AGENTS.md or GEMINI.md (if present) in the agentβs initial context.CODEGRAPH_ARCH_PRIMER="<primer text>"β optional custom primer injected into startup instructions (e.g., areas to focus on).
Why? Faster, more relevant early steps, fewer wasted graph/semantic queries, and better architecture answers on large repos.
Notes:
- Bootstrap is small (top directories summary), not a replacement for graph queries.
- Uses the same project selection as indexing (
CODEGRAPH_PROJECT_IDor current working directory).
# Use Rig for best performance with thinking and reasoning models (recommended)
CODEGRAPH_AGENT_ARCHITECTURE=rig ./codegraph start stdio
# Use default ReAct for traditional instruction models
./codegraph start stdio
# Use LATS for complex analysis
CODEGRAPH_AGENT_ARCHITECTURE=lats ./codegraph start stdioAll architectures use the same 8 graph analysis tools and tier-aware promptingβonly the reasoning strategy differs.
Here's something clever: CodeGraph automatically adjusts its behavior based on the LLM's context window that you configured for the codegraph agent.
Running a small local model? Get focused, efficient queries.
Using GPT-5.1 or Claude with 200K context? Get comprehensive, exploratory analysis.
Using grok-4-1-fast-reasoning with 2M context? Get incredibly comprehensive up-to 40 turns spanning in-depth analyses.
The Agent only uses the amount of steps that it requires to produce the answer so tool execution times vary based on the query and amount of data indexed in the database.
During development the agent used 3-10 steps on average to produce answers for test scenarios.
The Agent is stateless it only has conversational memory for the span of tool execution it does not accumulate context/memory over multiple chained tool calls this is already handled by your client of choice, it accumulates that context so codegraph needs to just provide answers.
| Your Model | CodeGraph's Behavior |
|---|---|
| < 50K tokens | Terse prompts, max 5 steps |
| 50K-150K | Balanced analysis, max 10 steps |
| 150K-500K | Detailed exploration, max 15 steps |
| > 500K (Grok, etc.) | Full monty, max 20 steps |
Same tool, automatically optimized for your setup.
We don't pick sides in the "embeddings vs keywords" debate. CodeGraph combines:
- 70% vector similarity (semantic understanding)
- 30% lexical search (exact matches matter)
- Graph traversal (relationships and context)
- Optional reranking (cross-encoder precision)
The result? You find handleUserAuth when you search for "login logic"βbut also when you search for "handleUserAuth".
When you connect CodeGraph to Claude Code, Cursor, or any MCP-compatible agent:
Before: Your AI reads files one by one, grepping around, burning tokens on context-gathering.
After: Your AI calls agentic_dependency_analysis("UserService") and instantly knows what breaks if you refactor it.
This isn't incremental improvement. It's the difference between an AI that searches your code and one that understands it.
# Clone and build with all features
git clone https://github.com/yourorg/codegraph-rust
cd codegraph-rust
./install-codegraph-full-features.sh# Local persistent storage
surreal start --bind 0.0.0.0:3004 --user root --pass root file://$HOME/.codegraph/surreal.dbcd schema && ./apply-schema.shcodegraph index /path/to/project -r -l rust,typescript,pythonπ Security Note: Indexing automatically respects
.gitignoreand filters out common secrets patterns (.env,credentials.json,*.pem, API keys, etc.). Your secrets won't be embedded or exposed to the agent.
Add to your MCP config:
{
"mcpServers": {
"codegraph": {
"command": "/full/path/to/codegraph",
"args": ["start", "stdio", "--watch"]
}
}
}That's it. Your AI now understands your codebase.
View Interactive Architecture Diagram - Explore the full workspace structure with clickable components and layer filtering.
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Claude Code / MCP Client β
βββββββββββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββ
β MCP Protocol
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β CodeGraph MCP Server β
β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β Agentic Tools Layer β β
β β βββββββββββ βββββββββββ βββββββββββ βββββββββββββββββββ β β
β β β ReAct β β LATS β β Tier β β Tool Execution β β β
β β β Agent β β Agent β β Selectorβ β Pipeline β β β
β β ββββββ¬βββββ ββββββ¬βββββ ββββββ¬βββββ ββββββββββ¬βββββββββ β β
β βββββββββΌββββββββββββΌββββββββββββΌββββββββββββββββΌββββββββββββ β
β βββββββββββββ΄ββββββββββββ΄ββββββββββββββββ β
β β β
β βββββββββββββββββββββββββββββΌββββββββββββββββββββββββββββββββ β
β β Inner Graph Tools β β
β β ββββββββββββββββ ββββββββββββββββ ββββββββββββββββββββ β β
β β β Transitive β β Call β β Coupling β β β
β β β Dependencies β β Chains β β Metrics β β β
β β ββββββββββββββββ ββββββββββββββββ ββββββββββββββββββββ β β
β β ββββββββββββββββ ββββββββββββββββ ββββββββββββββββββββ β β
β β β Reverse β β Cycle β β Hub β β β
β β β Deps β β Detection β β Nodes β β β
β β ββββββββββββββββ ββββββββββββββββ ββββββββββββββββββββ β β
β βββββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββ β
ββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββ
β
ββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββ
β SurrealDB β
β βββββββββββββββ βββββββββββββββ βββββββββββββββββββββββββββ β
β β Nodes β β Edges β β Chunks + Embeddings β β
β β (AST + β β (calls, β β (HNSW vector index) β β
β β FastML) β β imports) β β β β
β βββββββββββββββ βββββββββββββββ βββββββββββββββββββββββββββ β
β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β SurrealQL Graph Functions β β
β β fn::semantic_search_chunks_with_context β β
β β fn::get_transitive_dependencies β β
β β fn::trace_call_chain β β
β β fn::calculate_coupling_metrics β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Key insight: The agentic tools don't just call one function. They reason about which graph operations to perform, chain them together, and synthesize results. A single agentic_dependency_analysis call might:
- Search for the target component semantically
- Get its direct dependencies
- Trace transitive dependencies
- Check for circular dependencies
- Calculate coupling metrics
- Identify hub nodes that might be affected
- Synthesize all findings into an actionable answer
CodeGraph uses tree-sitter for initial parsing and enhances results with FastML algorithms and supports:
Rust β’ Python β’ TypeScript β’ JavaScript β’ Go β’ Java β’ C++ β’ C β’ Swift β’ Kotlin β’ C# β’ Ruby β’ PHP β’ Dart
Use any model with dimensions 384-4096:
- Local: Ollama, LM Studio, ONNX Runtime
- Cloud: OpenAI, Jina AI
- Local: Ollama, LM Studio
- Cloud: Anthropic Claude, OpenAI, xAI Grok, OpenAI Compliant
- SurrealDB with HNSW vector index (2-5ms queries)
- Free cloud tier available at surrealdb.com/cloud
Global config in ~/.codegraph/config.toml:
[embedding]
provider = "ollama"
model = "qwen3-embedding:0.6b"
dimension = 1024
[llm]
provider = "anthropic"
model = "claude-sonnet-4"
[database.surrealdb]
connection = "ws://localhost:3004"
namespace = "ouroboros"
database = "codegraph"See INSTALLATION_GUIDE.md for complete configuration options.
Keep your index fresh automatically:
# With MCP server (recommended)
codegraph start stdio --watch
# Standalone daemon
codegraph daemon start /path/to/project --languages rust,typescriptChanges are detected, debounced, and re-indexed in the background.
- More language support
- Cross-repository analysis
- Custom graph schemas
- Plugin system for custom analyzers
CodeGraph exists because we believe AI coding assistants should be augmented, not replaced. The best AI-human collaboration happens when the AI has deep context about what you're working with.
We're not trying to replace your IDE, your type checker, or your tests. We're giving your AI the context it needs to actually help.
Your codebase is a graph. Let your AI see it that way.
MIT
- Installation Guide
- SurrealDB Cloud (free tier)
- Jina AI (free API tokens)
- Ollama (local models)

