agentic_contextLABSCO SUMMARY
Four questions, four answers — not four result lists.
Consolidating into four tools is a deliberate trade: fewer tool definitions riding in the context on every turn, and each call does the planning and graph-walking that you would otherwise have to orchestrate yourself.
What it is
A code intelligence server that indexes a repository into a graph plus embeddings in SurrealDB, then puts reasoning agents in front of it. Each tool plans, searches, follows graph relationships and synthesizes an answer rather than returning a file list.
What you get
agentic_context— gathers what you need before editing: searches code, builds context, answers semantic questions. Focus values"search","builder"and"question", auto-selected from the queryagentic_impact— maps change impact through dependency chains and call flows, so you find out what breaks before you touch it. Focus values"dependencies"and"call_chain", both analysed by defaultagentic_architecture— system structure, API surfaces and architectural patterns, with focus values"structure"and"api_surface"agentic_quality— risk assessment across complexity hotspots, coupling metrics and refactoring priorities, with focus values"complexity","coupling"and"hotspots"- Agent architectures selectable at runtime: Rig is the default and maps each tool to the reasoning strategy that suits it — tree search for open-ended architecture and quality questions, linear reasoning for direct lookups, and a self-correcting fallback that analyses the failure and retries with a refined plan
- Bootstrap context so an agent's first tool call is not blind: a brief directory outline plus the contents of README.md and the agent instruction files, when enabled
- Context overflow protection, with per-tool and accumulation limits derived from the context window you declare
Requirements
Build from source with the full-features install script; on macOS, LLVM's lld is available for faster linking via the provided Makefile targets. A SurrealDB instance is required — the documented local start binds 0.0.0.0:3004 with file-backed storage — and the schema is applied from the schema directory before first use. Then index with codegraph index <YOUR_PATH_TO_PROJECT> -r -l rust,typescript,python, and register it with your client as codegraph start stdio --watch. Indexing respects .gitignore and filters common secret patterns such as .env, credentials.json and *.pem, so those are not embedded or exposed to the agent. Daemon mode is available for keeping the index warm.
Setup effort
Build from source — git clone https://github.com/Jakedismo/codegraph-rust
USE CASES
Briefing an agent before it edits
One call gathers the relevant code, the surrounding context and an answer to the semantic question, instead of a dozen searches that each return a file.
Finding out what a change will break
Dependency chains and call flows analysed together, so the blast radius is known before the edit rather than after the test run.
Getting oriented in an unfamiliar repository
System structure and API surface in one answer, with bootstrap context giving the agent a directory outline and the project's own instruction files to start from.
Deciding where refactoring pays off
Complexity hotspots and coupling metrics combined into a priority order, rather than a raw metrics dump you still have to interpret.
Keeping answers inside the model's context window
Declare the agent's context window and per-tool and accumulation limits are derived from it, so a large answer is bounded rather than truncated at the client.
4 tools
Listed in project docs. Your client may show a different list.
agentic_impactagentic_architectureagentic_qualityBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
git clone https://github.com/Jakedismo/codegraph-rust
cd codegraph-rust
./install-codegraph-full-features.sh
surreal start --bind 0.0.0.0:3004 --user root --pass root file://$HOME/.codegraph/surreal.db
cd schema && ./apply-schema.sh
codegraph index <YOUR_PATH_TO_PROJECT> -r -l rust,typescript,pythonMCP Clients
Claude Code
{
"mcpServers": {
"codegraph": {
"command": "<YOUR_PATH_TO_CODEGRAPH>",
"args": [
"start",
"stdio",
"--watch"
]
}
}
}