Installation

Install a native Code Buster release or build the canonical Rust CLI from source. Native packages do not require a Rust toolchain. The executable is named cb.

Pre-1.0 software: Code Buster is under heavy development. It can already support local repository exploration and provide additional context to AI coding agents, but behavior and findings may change before version 1.0.0. Do not yet use it as a blocking quality gate in a production pipeline. Treat CI and report integrations as evaluation or non-blocking visibility.

Homebrew

On Apple Silicon macOS:

brew install tool-bunker/tap/code-buster
cb version

Upgrade later with:

brew update
brew upgrade code-buster

Install script

On Apple Silicon macOS or x86-64 Linux:

curl -fsSL https://toolbunker.dev/codebuster/install | sh

The script downloads the latest native release, verifies its SHA-256 checksum, and installs cb under ${PREFIX:-$HOME/.local}/bin.

To inspect the script before running it:

curl -fsSL https://toolbunker.dev/codebuster/install -o install-code-buster.sh
less install-code-buster.sh
sh install-code-buster.sh

Windows

From PowerShell on x86-64 Windows:

irm https://toolbunker.dev/codebuster/install.ps1 | iex

The script verifies the release checksum and installs cb.exe under $HOME\.local\bin. Add that directory to PATH when the installer asks.

To inspect it before execution:

Invoke-WebRequest https://toolbunker.dev/codebuster/install.ps1 -OutFile install-code-buster.ps1
Get-Content .\install-code-buster.ps1
& .\install-code-buster.ps1

Cargo

With Rust 1.88 or newer installed, build and install the pinned release:

cargo install code-buster --version 0.11.0 --locked
cb version

Build from source

Run these commands from the code-buster/ directory:

cargo build --release --locked
./target/release/cb version

The release executable is self-contained and can be copied to a directory on your PATH.

During development, run the debug build directly:

cargo run --locked -- version

Use the release executable for performance measurements and release evidence so startup behavior matches distributed builds.