Arbor

Code context for people and agents. Find a function’s callers. Trace the path through your code. Know what breaks before you break it.

Simulated replay — the arbor commands and their output are real (tokio @ 178k LOC). Methodology: BENCHMARKS.md

v3.0.5 · Tests in TypeScript and JavaScript count: calls inside describe/it/test callbacks now belong to the test, so arbor callers, diff and check see Jest, Vitest and Mocha tests. MCP tool output uses project-relative paths. Release notes

---

Why Arbor

Most AI coding tools treat code as text. Arbor builds a semantic dependency graph — functions, classes, and modules as nodes; calls, imports, and inheritance as edges — then answers execution-aware questions with deterministic precision:

Question	Arbor answer
If I change this symbol, what breaks?	Blast radius with depth, confidence, and risk level
Who calls this — directly and transitively?	Caller/callee traversal on the call graph
What's the shortest path between A and B?	A* path through real dependencies
Is this PR too risky to merge?	CI gate on blast-radius thresholds

No keyword guessing. No embedding hallucinations. One graph, every interface.

Where the graph is unsure, it says so — edges carry a confidence, and ambiguous resolutions are labelled rather than hidden. An honest unknown beats a confident wrong answer.

---

What's new in v3.0.5

A fix release: tests written in TypeScript and JavaScript now count.

Fix	What was wrong
Jest, Vitest and Mocha tests are callers	Calls inside describe/it/test callbacks belonged to no symbol, so arbor callers missed every test and diff/check reported that nothing tested a change. Each test and hook is now a function named after it, such as it: accepts two, that owns the calls in its callback. On the repro in #235, arbor callers decide went from 2 callers to 4.
Project-relative MCP paths	Tool output could include absolute paths from your machine. Every file path is now relative to the project, and the namespaced io.modelcontextprotocol/protocolVersion request key is read first.

Cached graphs rebuild once on first use (extract-4). See the 3.0.4 release notes for the previous release.

v3.0.3 (Rust calls through paths and macros, per-symbol diff, --base)

A fix release. Every item below was a wrong answer, not a missing feature, and each ships with a regression test.