Cartograph context engine

Full context.
Before the agent answers.

Cartograph indexes repositories into a local knowledge graph of files, symbols, imports, calls, inheritance, communities, and execution flows.

Built for codebase exploration and security research: fast local indexing, ranked flow discovery, precise symbol context, plugin-fed datasets, and permissive MIT licensing.

Latest GitHub release
curl -sSfL https://onixhdz.github.io/cartograph/install.sh | sh
206
Languages detected
13
Tier 1 languages
Flows
Ranked relevance
Plugins
External graph data
01 · WHY

Agents need system context, not isolated file reads.

Cartograph gives the agent a graph it can traverse: structure, dependencies, call paths, communities, processes, and search results grounded in the indexed repository. It ranks what matters so investigations start from relevant flows and important symbols, not a flat list of text matches.

WITHOUT GRAPH CONTEXT
  • Read files one at a time
  • Grep for symbol names without relationships or ranking
  • Guess which calls, imports, and files are actually important
  • Miss execution flows, communities, and relevance signals
WITH CARTOGRAPH
  • Files, symbols, imports, calls, and inheritance in one graph
  • Hybrid BM25 + vector search when embeddings are enabled
  • Ranked flows, communities, and impact context for focused answers
  • Communities, process traces, file trees, and symbol impact connected in one local graph
02 · WHAT'S IN THE BOX

What Cartograph connects.

01 GRAPH

KNOWLEDGE GRAPH

Maps folders, files, symbols, imports, calls, inheritance, communities, and execution processes.

02 PARSE

206 LANGUAGES

Tree-sitter detection across 206 languages, with full extraction for 13 Tier 1 languages and inferred extraction for 56+ Tier 2 languages.

03 SEARCH

HYBRID RETRIEVAL

BM25 full-text plus optional vector search via reciprocal rank fusion for better semantic recall.

04 FLOWS

FLOW DETECTION

Discovers execution processes from entry points through call chains, then surfaces ranked flows instead of isolated matches.

05 AGENT

SKILLS + MCP

Install Cartograph skills for AI coding agents, then expose the warm graph through MCP for Claude Code, Cursor, OpenCode, and other tools.

06 PLUGINS

PLUGIN DATASETS

Embedded Go plugins can register external datasets directly through the public API and query them as local graph-backed datasets.

03 · WHY CARTOGRAPH

Purpose-built for exploration and security research.

Many code-intelligence tools stop at visualization, chat, or oversized tool catalogs. Cartograph focuses on the investigation loop that matters: index the repo, retrieve the right symbols, follow execution flows, understand impact, and keep the agent grounded in real code relationships.

01 EXPLORE

Find where behavior lives with semantic query, file-tree views, and symbol context.

02 TRACE

Follow ranked execution flows, callers, callees, processes, and related files to understand how behavior moves through the codebase.

03 RESEARCH

Use plugins and graph context to widen investigations with external datasets, references, and domain-specific signals.

04 SPEED PATH

Keep graphs hot through the background service so multi-query research sessions avoid repeated startup and reload costs.

04 · ARCHITECTURE

Index. Resolve. Query. Context.

Cartograph builds the graph in stages: walk the repository, parse symbols with tree-sitter, resolve imports, calls, inheritance, and references, cluster related symbols, trace execution processes, build BM25 plus optional vector search indexes, and serve the result to CLI and MCP clients.

cartograph
  │
  ├─ structure ──► repositories, folders, files, ignore rules
  ├─ parse     ──► tree-sitter symbols, imports, calls, heritage
  ├─ resolve   ──► cross-file calls, imports, inheritance, references
  ├─ cluster   ──► communities of related symbols (Leiden)
  ├─ processes ──► execution flows from entry points through call chains
  ├─ search    ──► BM25 + optional vector retrieval with RRF
  ├─ plugins   ──► external nodes, edges, and agent references
  └─ serve/mcp ──► warm graph cache, HTTP API, editor tools
05 · QUICKSTART

Install it, then ask your agent.

Cartograph is meant to sit in the agent loop. Install the binary, install the skills, then ask your coding agent to index, inspect, and reason through the graph.

01 · INSTALL
$ brew install onixhdz/tap/cartograph
# or
$ curl -sSfL https://onixhdz.github.io/cartograph/install.sh | sh

Homebrew is recommended on macOS. The shell installer supports Linux and macOS, or check out the latest Releases .

02 · INSTALL SKILLS
$ cartograph skills install
# targeted install
$ cartograph skills install --agent claude,opencode

Adds Cartograph routing, prompts, and workflows to AI coding agents so they know when to use the graph.

03 · ASK YOUR AGENT
"Use Cartograph to index this repo,
then map the auth flow and impact
for validateUser."

The installed skill guides the agent to start the service when useful, index first, and use graph-aware commands like context, impact, and query.

Teach your agent how the codebase works.

Cartograph maps repository context into one local graph so agents and researchers can explore code structure, trace behavior, and investigate risk.