# Install the frbit CLI

Source: https://docs.fortrabbit.com/platform/automation/cli/install
Published: 2026-11-17
Updated: 2026-11-17
Reviewed: 2026-11-17

> Install the frbit CLI with the install script, Homebrew, npm or a release archive, keep it current and remove it again.


## Install script

The shortest path on macOS and Linux:



```shell
curl -fsSL https://www.fortrabbit.com/install.sh | sh
```

With Homebrew on the machine, the script installs with `brew`. Without it, the script downloads the GitHub release for the operating system and CPU, verifies its SHA-256 checksum and installs `frbit` in `~/.local/bin`, or `/usr/local/bin` as root. It prints the line to add when that folder is not on `PATH`, and runs `frbit doctor` at the end. A `frbit` installed with Homebrew or npm stays: the script prints how to update it and installs nothing.

Upgrade by running the script again. `FRBIT_VERSION` installs a specific release and `FRBIT_INSTALL_DIR` another folder, both without Homebrew:



```shell
curl -fsSL https://www.fortrabbit.com/install.sh | FRBIT_VERSION=1.0.0 sh
curl -fsSL https://www.fortrabbit.com/install.sh | FRBIT_INSTALL_DIR="$HOME/bin" sh
```

`--setup-agent` also connects Claude Code and Codex after the install, the same as `https://www.fortrabbit.com/agents.sh`:



```shell
curl -fsSL https://www.fortrabbit.com/install.sh | sh -s -- --setup-agent
```

## Homebrew

The fortrabbit tap has a formula for macOS and Linux. Homebrew verifies the checksum of each release and sets up shell completion:



```shell
brew install fortrabbit/tap/frbit
brew upgrade frbit
```

## npm

The npm package pulls the binary for the platform as an optional dependency, so do not install it with `--omit=optional`:



```shell
npm install --global @fortrabbit/cli
npm update --global @fortrabbit/cli
```

## Release archives

The [GitHub releases](https://github.com/fortrabbit/frbit-cli/releases) have archives, checksums and software bills of materials, Windows included. Unpack `frbit` into a folder on `PATH`, and download again to upgrade. The asset names stay the same, for binary installers such as eget, ubi and mise:

| Platform | Asset |
| -- | -- |
| macOS Apple silicon | `frbit_macOS_AppleSilicon.tar.gz` |
| macOS Intel | `frbit_macOS_Intel.tar.gz` |
| Linux arm64 | `frbit_linux_arm64.tar.gz` |
| Linux x86-64 | `frbit_linux_amd64.tar.gz` |
| Windows arm64 | `frbit_windows_arm64.zip` |
| Windows x86-64 | `frbit_windows_amd64.zip` |

## Confirm the install



```shell
frbit version
```

It prints the installed release, its source commit and build date. Then [sign in and link the project](/platform/automation/cli/setup).

## Updates

Interactive sessions check GitHub for a newer stable version at most once per day. The check is silent on network errors and can be turned off with `export FRBIT_NO_UPDATE_NOTIFIER=1`. Agents never see the notice; `frbit doctor` checks the version on every run. Upgrade with the command of the install method above.

## Uninstall

`frbit uninstall` removes the CLI with everything it set up. All steps, older versions included: [remove the agent setup](/platform/automation/uninstall#cli).
