CLI · MCP · Receipts · Code graph · Pull request checks
Arbor docs
Install the v3.0.5 CLI, trace callers, review a branch, connect your editor and get receipts for Claude Code turns. A Cloud guide covers pull request checks.
Build your first graph
Arbor indexes source into a graph of symbols and calls. Query it from your terminal, or let an MCP client use it. With Claude Code, it can also write a receipt after each turn.
Install Arbor, then run these commands in your project.
Open the quickstart Runs locally. No Cloud account required.cd your-project
arbor setup
arbor status
arbor mapsetup builds the index. map shows the repository outline.
Find your next step
From install to first query
Choose a release, verify it, and index a project.
Installation QuickstartCallers, branches and agent turns
Trace a symbol, compare a branch with main, connect an assistant, or see what a Claude Code turn changed.
CLI reference MCP integration ReceiptsCheck what the graph sees
Learn the model and work through missing relationships.
The code graph TroubleshootingSee a query through to the source
Open a recorded Python project. Pick a function, follow its callers, and inspect the source behind each relationship.
A captured investigation, with the engine version and analysis limits included.
Local engine, open source
These guides cover the v3.0.5 CLI, MCP bridge and receipts. Indexing, queries and receipts run on your machine, and the CLI has no telemetry or update check. For a check on GitHub pull requests in repositories with checks on, try Arbor Cloud. The pull request checks guide covers turning checks on, what the check lists and Team rules.
Read the v3.0.5 release notes