LayerMap

io.github.coffeecoprojectv0.1.4Updated Oct 5, 2026

Call graph for coding agents: callers up to HTTP routes, callees and usages for TS, Go, Python, Java

VerifiedSTDIODesktop onlyDeveloper ToolsKnowledge & Memory

Overview

AI-generated overview

LayerMap gives coding agents a read-only call graph of a repository, tracing callers up to HTTP routes and callees across TypeScript, JavaScript, Go, Python…

What it does
LayerMap builds a local map of a codebase and exposes three read-only tools: project_explore_map for a directory, file or declaration's callers and callees (direction INCOMING or OUTGOING, depth up to 8), project_search_map to find declarations by words in names, paths or documentation, and project_find_references for every usage of a declaration. Calls are resolved with each language's own compiler or type checker, so interface, base-class, template and decorator calls resolve as the compiler resolves them. The map is rebuilt incrementally on each call and cached outside the repository.
When to use it
Use it when an agent needs to answer impact questions in a repository, such as which HTTP routes or handlers a change affects, without many separate searches. It suits TypeScript, JavaScript, Go, Python and Java projects where compiler-accurate callers and callees matter.
Requirements
Runs locally over stdio via npx (npm package layermap). Needs Node.js 22.22 or later, macOS or Linux (x64 or arm64), and a Git repository; Java projects need JDK 21 or later. No accounts, API keys or environment variables are declared; an optional LAYERMAP_CACHE variable sets the cache location.
Before you install
The tools are read-only and the README states LayerMap runs entirely on the machine and sends nothing anywhere. Setup commands can register the server, allow its read-only tools to run without a prompt, and add a sentence to the agent's instructions file; use --scope project for a team and the remove command to undo. The first map of a large repository can take minutes.

Installation

In SourceWeft

  1. Open LayerMap in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[LayerMap]

LayerMap

English · 中文

[npm] [License]

[Claude Code asks which HTTP endpoints changing Storage.MarkFeedAsRead affects; one LayerMap call returns all four callers with their routes]

A real Claude Code session on Miniflux, replayed: one map call finds every endpoint, then the agent confirms them in source.

A layered map of your codebase for coding agents. LayerMap gives Claude Code, Codex, DeepSeek Harness and other MCP clients three read-only tools that answer, in one call, what an agent otherwise works out with dozens of searches:

  • What calls this, and what does changing it affect? Callers traced up to 8 levels, to the HTTP routes, handlers, jobs and commands they start from.
  • What does it call? Callees down to 8 levels.
  • What is here? Modules, each file's declarations, and every usage of a symbol.

It maps TypeScript, JavaScript, Go, Python and Java with each language's own compiler, so calls through interfaces, base classes, templates and decorators resolve as the compiler resolves them, including the ones text search misses.

Example

In Miniflux, one call on Storage.MarkFeedAsRead finds all four ways a request reaches it, each with its route:

DECLARATION internal/storage/entry.go: Storage.MarkFeedAsRead m656-680 exported  ← called by internal/api/feed.go: handler.markFeedAsRead m140-155 @149  ← called by internal/fever/handler.go: handler.handleWriteFeeds m492-519 @508  ← called by internal/googlereader/handler.go: handler.markAllAsReadHandler m1261-1338 @1311  ← called by internal/ui/feed_mark_as_read.go: handler.markFeedAsRead m14-30 @24[1] internal/api/feed.go: handler.markFeedAsRead m140-155  ← used as value by internal/api/api.go: Serve f25-84 @61 "/feeds/{feedID}/mark-all-as-read"[1] internal/googlereader/handler.go: handler.markAllAsReadHandler m1261-1338  ← used as value by internal/googlereader/handler.go: Serve f44-64 @62 "/mark-all-as-read"[1] internal/ui/feed_mark_as_read.go: handler.markFeedAsRead m14-30  ← used as value by internal/ui/ui.go: Serve f18-180 @77 "/feed/{feedID}/mark-all-as-read"… (the Fever API, then on down to main.go: main)

m and f mark methods and functions with their lines; @ is the line of the call, and the quoted path is the route it is registered under.

Results

Impact questions ("which HTTP endpoints does changing this affect?") on public Go, Python and Java projects, graded blind against truth sets cross-checked with each language's own toolchain:

With LayerMapWithout
Endpoints found, at most 15 requests (gpt-5.5, 6 tasks × 3 runs)97.9%58.8%
Used unprompted by Claude Code / Codex (plugin installed)6 of 6 / 6 of 6—
Endpoints found, no request limit (Claude Code / Codex)99.3% / 98.0%99.0% / 98.6%
Cost, no request limit (Claude Code in USD / Codex in input tokens)−32% / −55%
Time, no request limit+24% / +17%

With a tight budget, the map finds far more of the affected code, at about 24% more tokens. With no limit, both agents get there either way. The map makes the run cheaper, and the agents explore more widely, which takes longer. These are small samples on tasks written by LayerMap's authors. The report has the setup, the published tasks and the limitations.

How LayerMap differs

Other tools give agents part of this. LayerMap combines compiler accuracy with whole-chain traces in one local map:

Tree-sitter code graphs (codegraph, GitNexus, …)Language servers and IDEs (Claude Code's LSP tool, Serena, JetBrains)Embedding search (Claude Context, Augment)LayerMap
How calls are linkedMatched by names, imports and framework rules, often with confidence scoresThe compiler's own resolutionNot linked; similar code is retrievedResolved by each language's compiler or type checker
Callers traced to routes and handlersIn several tools, at varying depthOne level per request (JetBrains: 5 by default)—Up to 8 levels in one call
Kept as a mapYes, with file watchingNo, answered live by a running serverAn index of code chunksYes, brought up to date on every call
Runs on your machineYes; some send anonymous telemetryYesUsually with cloud embeddingsYes, and sends nothing

Another tool fits better if you need:

  • more languages, since tree-sitter graphs cover 30 or more;
  • Windows;
  • renaming and refactoring, from language servers;
  • search by meaning, from embedding search;
  • search across many repositories, with Sourcegraph.

Install

Claude Code

/plugin marketplace add coffeecoproject/layermap/plugin install layermap@layermap

Codex

codex plugin marketplace add coffeecoproject/layermapcodex plugin add layermap@layermap

DeepSeek Harness

npx layermap setup dsh

This adds LayerMap to every dsh profile. Each session maps the project dsh was started in, and npx layermap remove dsh undoes it.

In every agent, start a new session in a Git repository and ask as usual. LayerMap tells the agent when the map helps. On first launch, npx downloads the pinned layermap package from npm.

Claude Code asks once before each map tool runs in a project. Choose "don't ask again", or run npx layermap allow claude to allow the plugin's read-only tools everywhere.

Without plugins: run npx layermap setup claude or npx layermap setup codex. Setup does three things:

  • registers the server;
  • lets its read-only tools run without a prompt;
  • adds one marked sentence to the agent's instructions file.

Use --scope project to set it up for a whole team, and npx layermap remove … to undo it. For any other MCP client, run npx -y layermap mcp as a stdio server in the repository.

Requirements:

  • Node.js 22.22 or later.
  • macOS or Linux (x64 or arm64).
  • A Git repository.
  • For Java projects, a JDK 21 or later.

How it works

The first call in a repository builds its map: seconds for a small project, a few minutes for a large one. Later calls re-analyze only what changed, so the map always matches the working tree.

Maps stay in your user cache (~/Library/Caches/layermap, ~/.cache/layermap or LAYERMAP_CACHE), never in the repository. LayerMap runs entirely on your machine and sends nothing anywhere (privacy, security).

ToolUse
project_explore_mapA directory, a file, or a declaration's callers and callees (direction INCOMING or OUTGOING, depth up to 8).
project_search_mapFind declarations by words in their names, paths or documentation.
project_find_referencesEvery usage of a declaration, compiled from current source.

The same from the command line:

npx layermap explore src/api/users.ts --name createUser --direction INCOMING --depth 8npx layermap search "invoice total"npx layermap refs src/billing/tax.ts calculateTax

FAQ

How long does the first map take? On a recent Mac:

  • Miniflux (400 Go files): about 3 s.
  • Polar's server (1,900 Python files): about a minute.
  • Conductor (1,500 Java and 1,300 TypeScript files): under two minutes.

What can't it see? Calls the compiler cannot resolve statically: dependency injection, unknown framework routing, reflection and computed names. The tools say where a trace stops, and a missing relationship does not prove absence.

Windows? Not yet.

How do I remove it?

  • Claude Code: /plugin uninstall layermap@layermap.
  • Codex: codex plugin remove layermap@layermap.
  • Then delete the cache directory.

Development

You need pnpm, Go 1.24 and a JDK 21+. A missing toolchain leaves its language unanalyzed.

Run pnpm install. On the first install pnpm asks which dependencies may run build scripts; allow esbuild only, since the SQLite package ships prebuilt binaries:

pnpm approve-builds esbuild '!@photostructure/sqlite'

Then run pnpm test, pnpm typecheck or pnpm lint.

pnpm package builds the npm package.

License

Apache-2.0. See LICENSE and NOTICE.

Source: README.md at commit 82b8dcf

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.4LatestOct 5, 2026