Installing the CLI
collector manages Collector from the terminal: sign in, set projects up, read and settle issues, follow logs live, and upload your builds' source maps. It's one static binary, for people, their AI agents and CI. If it's your first time, start with The CLI in two minutes.
macOS and Linux
curl -fsSL https://packages.chrom.ar/collector/install.sh | sh
The installer checks the download against the release's checksums and puts collector in /usr/local/bin when it can, else ~/.local/bin (COLLECTOR_INSTALL_DIR picks another). Run it again to upgrade.
Or with Homebrew:
brew install chrom-ar/tap/collector
Or with Go:
go install github.com/chrom-ar/collector-cli/cmd/collector@latest
Debian, Ubuntu and derivatives
Add Chroma's apt repository once; from then on, sudo apt upgrade brings each new release:
curl -fsSL https://packages.chrom.ar/chroma.gpg | sudo tee /usr/share/keyrings/chroma.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/chroma.gpg] https://packages.chrom.ar/apt stable main" | sudo tee /etc/apt/sources.list.d/chroma.list
sudo apt update && sudo apt install collector
Fedora, RHEL and CentOS Stream
sudo curl -fsSLo /etc/yum.repos.d/chroma.repo https://packages.chrom.ar/rpm/chroma.repo
sudo dnf install collector
sudo dnf upgrade brings new releases. On openSUSE: sudo zypper addrepo https://packages.chrom.ar/rpm/chroma.repo and sudo zypper install collector. Packages and repositories are signed.
Windows and others
Every release publishes archives and .deb, .rpm and .apk packages for macOS, Linux and Windows, on amd64 and arm64, on the releases page.
Keeping it up to date
At most once a day, the CLI tells you when a newer release is out. It never updates itself: upgrade with the same method you installed it with.
If you used the npm CLI
This CLI replaces @chrom-ar/collector-cli, the npm package, which is deprecated. Its tokens aren't carried over: run collector login again.