repomap

repomap

A map of your codebase for AI agents: code graph, search, call paths and change impact. No API key.

Code graph · hybrid search · call paths · change impact · an interactive graph UI.

One Rust binary. Local. No API key. MIT.

npx -y @sylphx/repomap setup

Live demo · Docs · Quickstart · Tools · Graph UI · Benchmarks · Compare

The real UI on excalidraw (687 files, indexed in under half a second): search, a symbol's code and callers, then the blast radius of a change. Try it in your browser , no install needed.

See it work

Run it on any repository. This is the real output on repomap's own source (v1.5.0, trimmed): ask what breaks if pagerank changes.

$ npx -y @sylphx/repomap impact pagerank

Impact (MEDIUM risk)

Changing: function pagerank (crates/repomap-core/src/graph.rs:639) 2 direct callers, 4 symbols affected in total across 6 files and 3 modules; 5 files importing the changed files; 1 test file to run.

Direct callers (will break if the contract changes)

• method DbSchema.graph_json — crates/repomap-core/src/db.rs:1981
• function link — crates/repomap-core/src/graph.rs:122

Indirect (depth 2)

• function assemble — crates/repomap-core/src/index.rs:700

One local call, no API key, and an answer your agent can cite as file:line.

Quickstart

npx -y @sylphx/repomap setup     # add repomap to Claude Code, Codex, Cursor, VS Code, Claude Desktop, Windsurf, Gemini CLI

npx -y @sylphx/repomap serve # open the graph UI for the current repo

Prefer to wire one client by hand? claude mcp add repomap -- npx -y @sylphx/repomap mcp for Claude Code; the Cursor, VS Code, Codex and Docker snippets follow.

That's it. Add --claude-hooks to also enrich Claude Code's Grep and Glob. setup detects the clients you have, writes their MCP config, and prints every change it made. Run it again and nothing changes. Then ask your agent: *"Use repomap to map this repo."*

Cursor and VS Code, one click

· Install in VS Code

Requires Node 18+. Confirm the install in your editor, open your project, and enable the server. Both links run npx -y @sylphx/repomap mcp locally; no API key is needed.

For VS Code from a terminal:

code --add-mcp '{"name":"repomap","command":"npx","args":["-y","@sylphx/repomap","mcp"]}'

Or add the server to .cursor/mcp.json:

{

"mcpServers": { "repomap": { "command": "npx", "args": [ "-y", "@sylphx/repomap", "mcp" ] } } }

For .vscode/mcp.json, use the VS Code servers format:

{

"servers": { "repomap": { "type": "stdio", "command": "npx", "args": [ "-y", "@sylphx/repomap", "mcp" ] } } }

<!-- editor-install:end -->

Manual MCP config

{

"mcpServers": { "repomap": { "command": "npx", "args": ["-y", "@sylphx/repomap", "mcp"] } } }

Claude Code: claude mcp add repomap -- npx -y @sylphx/repomap mcp Claude Desktop, one click: download repomap- .mcpb from the latest release, open it, and pick your project folder. Claude Code plugin: /plugin marketplace add SylphxAI/repomap, then /plugin install repomap@repomap Codex (~/.codex/config.toml):

[mcp_servers.repomap]

command = "npx" args = ["-y", "@sylphx/repomap", "mcp"]

Docker (stdio, amd64/arm64):

{ "mcpServers": { "repomap": { "command": "docker", "args": ["run", "-i", "--rm", "-v", "/path/to/repo:/workspace:ro", "ghcr.io/sylphxai/repomap"] } } }

The server indexes the client's workspace root (or its working directory, or REPOMAP_ROOT). Every tool also takes root.

Proof: file localization on SWE-bench Verified

One issue-text search finds every fix file in the top 10 for 83.0% of SWE-bench Verified issues (semble: 71.0%). File retrieval, not issue resolution.

Chart values and evaluation protocol SWE-bench Verified: every gold fix file in the top k files Method Acc@1 Acc@5 Acc@10 repomap 48.8% 74.8% 83.0% semble 34.0% 61.6% 71.0% BM25 20.8% 45.4% 55.8% Defaults selected on 300 disjoint SWE-bench test instances, excluding every Verified ID, then frozen before one evaluation on all 500 Verified instances. One search per issue, at its base commit; gold files are used only for scoring. All three methods scored 500/500, with zero errors. Split definitions, pinned revisions and full results · Committed chart data

Trade-off: on semble's public code-search set, NDCG@10 is 0.845 versus semble's 0.851 ; semble wins there. This is not a claim of better search on every task. Measured search quality and limitations .

Why

Agents burn most of their context on grep, ls and reading whole files just to work out where things are. repomap gives them the map up front:

• Where is it? Hybrid search that matches symbol names, the words inside functions *and* what the code means, with the lines that matched. Ask "where are failed requests retried" or parseConfig.
• What is this? One call returns a symbol's code, callers with call-site lines, callees, subtypes and the tests that reach it.
• How does A reach B? The shortest call path, each hop cited file:line.
• What breaks if I change this? Direct and indirect callers, importing files, modules touched, tests to run, and a risk level. Point it at your git diff before you commit.
• What does this repo look like? Modules found from real dependencies (not just folders), the most central files, the most used symbols, and entry points.

All of it comes from a local index: tree-sitter parsing, a resolved import and call graph, PageRank, Louvain communities, BM25 over AST chunks, and a small static code embedding model (33 MB, downloaded once from Hugging Face, then offline). Nothing leaves your machine, and no API is called; the model download is the only network request (set REPOMAP_EMBED=0 to skip it).

What your agent gets

Six tools, each with an obvious job:

Answers are compact text that cites file:line, so they cost few tokens. Pass format: "json" for structured output.

> impact target=decode

Impact (LOW risk)

Changing: function decode (src/auth/token.ts:14) 1 direct caller, 3 symbols affected in total across 3 files and 2 modules; 1 file importing the changed files; no tests reach this.

Direct callers (will break if the contract changes)

• function verifyToken — src/auth/token.ts:8

Indirect (depth 2)

• method SessionStore.refresh — src/auth/session.ts:5

Indirect (depth 3)

• function handleRefresh — src/api/router.ts:6

Importing files

• src/auth/session.ts

The same commands work in your terminal: repomap map, repomap search "…", repomap context X, repomap trace A B, repomap impact --changed, repomap db.

The graph UI

npx -y @sylphx/repomap serve            # live, with code preview

npx -y @sylphx/repomap export # repomap.html: one self-contained file you can publish

Impact. Select a file and press i : everything that depends on it lights up by depth, with a list you can click through. Code. Click a symbol to see its source, callers and callees. Open ↗ jumps to y