CLI intro
Published
Updated
⌨️
Where ClickOps can't go.
frbit is the fortrabbit command line client. It manages apps, environments, deployments and ENV vars. Use it from a terminal, a script or a CI job. It signs in through the browser or with a personal API token. It can also set up the MCP server and skills for coding agents.
About
frbit is a single binary that talks to the public API. Each command acts as the person who signed in, so frbit can do what that person can do in the dashboard. It deploys and restarts environments, reads logs, sets ENV vars, syncs the database and files of the local project, opens a shell on an environment, and creates apps and environments.
Install it first. The usage page has every command.
In the terminal
Most of the daily work next to git deployment is one command each: open a shell, pull the database, sync the uploads, read the deployment log. frbit fills in the SSH user and host, so there is nothing to copy from the dashboard. With the project folder linked to an environment by frbit link, the environment ID can be left out too. The dashboard shows the matching command next to these tasks.
In scripts and CI
A CI job passes a personal API token with each command and stores nothing on the runner. --json prints the API response unchanged, ready for jq. Commands that delete, overwrite or book something ask first. A script answers with --confirm <id> or --yes, and gets exit code 1 without it. A typical job: deploy the environment once the tests passed.
With a coding agent
Claude Code, Codex and other agents call the same commands and read the --json output. frbit setup agent connects Claude Code and Codex in one go: it registers the MCP server and installs the agent skills, which tell the agent which command does what. The agent acts as the person who signed in. Deletes need a sign-in approved with Allow deletes, a small safety net for an agent that is a little too confident.