The OrchestratorOverviewHow It Connects
The StudioOverviewExtensionsHow It Works
ResourcesBlogFAQAbout
Get in touch
Early Access
Studio Extension

Code Intelligence

SCIP indexing, graph navigation, semantic search

Your agents don't need your entire codebase in the context window to understand it. Code Intelligence builds a structural index locally — symbols, references, call graphs — so agents query precise answers instead of scanning thousands of lines.

Code Intelligence overview
Code Intelligence overview
Structural pattern matching
Structural pattern matching
Package dependencies
Package dependencies
Risk analysis and hotspots
Risk analysis and hotspots
Change and symbol impact
Change and symbol impact

Full codebase structure at a glance — symbols, references, and relationships indexed locally.

Capabilities

What it does

SCIP Indexing

Parses your codebase into a structural index using SCIP (Source Code Intelligence Protocol). Symbols, definitions, references, and type relationships — all queryable without LLM inference.

Graph Navigation

Interactive graph explorer built on Graphology and Sigma.js. Visualise call chains, dependency trees, and symbol relationships. Drag, zoom, and click through your code's architecture.

Semantic Search

Vector embeddings stored in LanceDB with cross-encoder reranking. Search by meaning — 'where do we validate user input' — not just by symbol name. All inference runs locally.

20 Languages

TypeScript, Python, Go, Java, Rust, C/C++, C#, Ruby, Kotlin, Swift, Scala, PHP, and more. The indexer handles each language's semantics natively — generics, traits, interfaces, decorators — not just text matching.

AST-Grep Patterns

Structural pattern matching via ast-grep. Find code by shape — 'all functions that catch an error and don't log it' — across your codebase in milliseconds.

Cross-Repo Federation

Index multiple repositories and search across them. Your agents see dependencies, shared libraries, and API contracts across the whole project — not just the current repo.

How it works

From install to first use.

1
Index your codebaseThe SCIP indexer runs locally, parsing source files into a structured graph of symbols, references, and relationships. Stored in Kuzu (graph) and LanceDB (vectors).
2
Agents query, not scanInstead of pasting files into the context window, agents call structured tools — find_references, get_definition, search_symbols — and get precise, structured answers.
3
Explore visuallyOpen the graph workspace tab to navigate your codebase interactively. Click a symbol to see its callers, callees, and type hierarchy in real time.
4
Stay currentThe index updates incrementally as you edit. No manual rebuilds. Agents always see the latest structure.
Why local matters

Precision saves tokens.

A 'find all references' call returns exactly the lines that matter — not 50 files of context. Your agents spend tokens on reasoning, not on reading.

LocalAll indexing and search runs on your machine
~100×fewer tokens than dumping files into context
0lines of code sent to any cloud for indexing
<1ssymbol lookup vs seconds of LLM scanning

Code Intelligence ships with the Studio. No extra install, no extra cost.

Get early access All extensions