Install

Install the browserlane binary on macOS, Linux, or Windows, then download Chrome for Testing.

browserlane ships as a single native binary, bl, for macOS, Linux, and Windows. The fastest way to get it is the one-line installer.

One-line install

curl -fsSL https://browserlane.com/install.sh | sh

irm https://browserlane.com/install.ps1 | iex

The installer detects your platform, verifies the download's checksum, installs bl, and puts it on your PATH.

Re-run to update

Running the installer again fetches the latest release and replaces your existing bl — that is the supported way to update.

Manual download

Prefer to grab the archive yourself? Download the asset for your platform from the latest release, extract it, and put bl on your PATH.

Platform	Asset
macOS (Apple Silicon)	`bl-*-aarch64-apple-darwin.tar.gz`
macOS (Intel)	`bl-*-x86_64-apple-darwin.tar.gz`
Linux (x64)	`bl-*-x86_64-unknown-linux-gnu.tar.gz`
Windows (x64)	`bl-*-x86_64-pc-windows-msvc.zip`

Build from source

If you'd rather build it yourself, you need Rust stable.

git clone https://github.com/browserlane/browserlane
cd browserlane
cargo build --release
./target/release/bl --version

The binary lands at ./target/release/bl.

First run

Download Chrome for Testing

bl drives its own build of Chrome for Testing (and a matching chromedriver) that it keeps in a local cache. Fetch it once:

bl install

This is required before your first automation — bl doesn't download Chrome on demand, so a browser command errors with "Chrome not found" until the cache is populated.

Verify the install

bl --version

To confirm the browser is in place, check:

bl is-installed   # exit 0 = Chrome + chromedriver present, exit 1 = missing
bl paths          # print the cache, Chrome, and chromedriver paths

Updating & uninstalling

bl update           # install the latest release
bl update --check   # report whether a newer release exists (no changes)
bl uninstall        # remove bl and the PATH entry it added
bl uninstall --purge  # also remove the Chrome cache and screenshots

bl update swaps in the new binary as a fresh file rather than overwriting the old one in place. That side-steps a macOS Gatekeeper quirk where a binary overwritten on top of an existing one can be killed on launch. Re-running the install script has the same effect.