# frbit CLI

Source: https://www.fortrabbit.com/features/cli
Created: 2026-08-23
Reviewed: 2026-08-23

> There is a self-service dashboard. Some prefer the terminal. frbit is our command line interface to operate the platform. Deploy, read the build output, set a variable, list what is running.


There is a self-service dashboard. Some prefer the terminal. `frbit` is our command line interface to operate the platform. Deploy, read the build output, set a variable, list what is running.

* [github.com/fortrabbit/frbit-cli](https://github.com/fortrabbit/frbit-cli)

## Automation on a documented interface

Everything it does is a call to the [public API](/features/public-api). `--json` prints the response unchanged for whatever runs next.

## AI Agent support

`frbit setup agent` detects Claude Code and Codex, registers the [MCP server](/features/mcp-server) with each and installs the [agent skills](/features/agent-skills). It is the shortest path from a fresh machine to an agent that can operate the platform.

Install routes for macOS, Linux and Windows, and every command with its options:

:BlockLink{title="CLI documentation" path="/platform/automation/cli" property="docs"}

## FAQ

### What does it need installed?

**Nothing** — The CLI is a self-contained binary with no runtime dependency, which is what makes it fit a CI pipeline or a container as easily as a laptop. Install with the script, with Homebrew, with npm, or from the release archives — Windows included.

### How does it authenticate in CI?

**One environment variable** — An interactive session signs in once and the credential lands in the operating-system credential store. A job passes `FRBIT_TOKEN` for a single process instead, which takes precedence over anything stored. Separate accounts are kept apart by profile.

### Can it be used in a script?

**That is what `--json` is for** — Read commands print the API response unchanged with `--json`, ready for `jq`. Bear in mind that responses can carry environment-variable values and application log output, so CI logs deserve the same care as a terminal capture.

### What does it have to do with agents?

**It sets them up** — One command detects the installed coding agents, registers the [MCP server](/features/mcp-server) with each and installs the latest [agent skills](/features/agent-skills). One command takes a fresh machine to an agent that can operate the platform.

---

- [Public API](/features/public-api)
- [MCP server](/features/mcp-server)
- [CLI docs](/platform/automation/cli)