Install Arbor

Official release binaries#

Prebuilt binaries are the most direct way to get the GitHub release without a Rust toolchain. Download the archive for your operating system and processor from GitHub Releases, extract it, and place the executable in a directory on your PATH.

macOS · Apple silicon

arbor-macos-aarch64.tar.gz

macOS · Intel

arbor-macos-x86_64.tar.gz

Linux · ARM64

arbor-linux-aarch64.tar.gz

Linux · x86-64

arbor-linux-x86_64.tar.gz

Windows · x86-64

arbor-windows-x86_64.zip

Open a new terminal after changing PATH. On macOS and Linux, the extracted arbor file must have execute permission. The Windows executable is arbor.exe.

Package manager alternatives#

Cargo

If you already have a Rust toolchain and your platform's build tools, install the published crate. Cargo builds the CLI locally.

cargo install arbor-graph-cli

npm

The official npm wrapper requires Node.js 18 or newer and downloads a platform binary. You can invoke it through npx:

npx @anandb71/arbor-cli --version

Using npx does not make arbor a global command. Keep the same prefix for subsequent commands, or use the release binary for an MCP client that launches arbor directly.

The upstream installation guide also covers install scripts and pinned releases. For reproducible environments, select an available version in the channel you use.

Verify and start#

arbor --version
arbor --help
arbor doctor

doctor runs environment diagnostics. It may report missing optional components such as the visualizer or inactive services; inspect the specific message rather than assuming every warning prevents CLI use.

Once the command is available, follow the quickstart from the root of a project you want to index.

When updating#

Read the release notes, update using your chosen channel, and run arbor --version again. Graphs built by an older version refresh automatically on first use from v3.0.3; run arbor index --no-cache for a full rebuild before comparing results across versions.

Graph resolution and ranking have changed between releases. Node identities, edges, and centrality scores are not a stable basis for comparisons across versions without rebuilding the graph.