bex / CLI

Your platform. At your prompt.

Deploy services. Follow logs. Launch your favorite coding models. One CLI for the work between a good idea and a shipped project.

Install Bex CLI Read the docs

macOS & Linux. Windows via WSL.

bex — ~/your-project

# Make yourself at home
bex login

# Pick your workspace
bex workspaces -o json
bex workspace set "$BEX_WORKSPACE_ID"

# Deploy an existing service
bex deploys create "$BEX_SERVICE_ID" --wait

Set the variables to your workspace and service IDs.

A little less UI. A lot more flow.

One native binary

JSON, YAML & text

Hosted or self-hosted

Open source, inspectable

From first deploy to everyday ops

Keep your hands on the keyboard.

Explore every command

Ship the next version.

Trigger a deploy and wait for the result. A failed deployment returns a nonzero exit code, so your next step has a clear signal.

bex deploys create "$BEX_SERVICE_ID" --waitDeployment guide

Get straight to the logs.

Inspect your services, review deploy history, and tail application logs without breaking your train of thought.

bex logs --resources "$BEX_SERVICE_ID" --tailLogging guide

Make it repeatable.

Use structured output in scripts and CI. Supply an issued OAuth access token with BEX_ACCESS_TOKEN for unattended commands.

bex services -o jsonSet up CI authentication

Also in your toolbelt

Your coding agent. Your choice of model.

Launch Claude Code with GLM, Kimi, DeepSeek, or Muse. Each provider gets its own settings and history. Bring your key; Bex handles the wiring.

Meet the coding launchers

Requires an installed Claude Code runtime and your own provider API key. Provider usage is billed by the provider.

A place of its own.

Bex keeps its login configuration in a dedicated directory. Coding providers get separate configurations, too.

~/.bex/cli.yaml

Point it at your platform.

Use hosted Bex by default, or set BEX_HOST to the API base URL of your own installation.

BEX_HOST

An upgrade you can verify.

Direct binary upgrades verify release signatures and checksums before replacing the executable. Homebrew installs stay with Homebrew.

bex upgrade --check

Your next command

Good tools start with a simple install.

Install Bex, sign in, and choose your workspace. Your terminal is ready for the next thing.

macOS / Linux · arm64 / x86_64

On Windows, use the Linux build inside WSL.

Browse CLI releases

Install the CLI

brew install bex-co/tap/bex

Requires Homebrew. Keep it current with brew upgrade bex.

Make the connection

bex login

Complete the authorization in your browser, then return to your terminal.

Choose your workspace and get started

Read the source. Know your tools.

Explore the Bex CLI implementation, installation guide, and compatibility notes on GitHub.

Explore on GitHub