# Install and sign in

> Install the free bitsrun command line on macOS, Linux or Windows, sign in through your browser, and deploy a model from your terminal.

Source: https://bitsrun.com/docs/cli/
Updated: 2026-11-09

`bitsrun` is one free program that does two jobs:

- **A command line for your BitsRun account.** Deploy models, check which GPU a model needs, manage API keys and uploads, and see what you spent. Every command is listed in [Command reference](https://bitsrun.com/docs/cli/commands/).
- **A coding agent in your terminal.** Type `bitsrun` with nothing after it and it opens an agent that reads and edits your code and runs commands after you approve them, with any model provider. See [bitsrun coding agent](https://bitsrun.com/docs/agent/).

## Install

Pick the line for your computer. The install script chooses the right build and checks its SHA-256 checksum before installing.

### macOS and Linux

```bash
curl -fsSL https://get.bitsrun.com | sh
```

It installs to `~/.local/bin`. If that folder is not on your PATH yet (common on a new Mac), the script prints the line that adds it to your shell's startup file. Run that line, then open a new terminal. On Alpine Linux, run `apk add libstdc++ libgcc` first.

### Windows

Open PowerShell and run:

```powershell
irm https://get.bitsrun.com/win | iex
```

It installs to `%LOCALAPPDATA%\bitsrun\bin` and adds that folder to your PATH. Open a new terminal window afterwards so the PATH change applies. Windows on Arm is not covered by this script yet: install with npm instead.

### With npm

If you already use Node.js 22 or later. This also works on Windows on Arm and on Linux machines that are not x64 or arm64:

```bash
npm install -g bitsrun
```

> [!TIP]
> To install somewhere else, set `BITSRUN_INSTALL_DIR` before running the script, for example `curl -fsSL https://get.bitsrun.com | BITSRUN_INSTALL_DIR=$HOME/bin sh`.

The [install page](https://bitsrun.com/install/) shows the same three options, each with a **Copy** button.

Check that it works:

```bash
bitsrun --version
```

## Sign in

```bash
bitsrun login
```

1. Your browser opens on bitsrun.com. Sign in with your email code or passkey if you are not already signed in.
2. Click **Allow**. The page names the computer asking for access, so you know which one you are approving.
3. Back in the terminal, bitsrun confirms it:

```text
Signed in as MacBook Pro. This session lasts until 2027-02-07.
Next: bitsrun deploy qwen3:8b
```

The session lasts 90 days and is saved in a file only you can read: `~/.config/bitsrun/credentials.json` on macOS and Linux, `%APPDATA%\bitsrun\credentials.json` on Windows.

### Signing in over SSH or without a browser

On a remote server, or with `--no-browser`, bitsrun prints a link instead of opening a browser:

```bash
bitsrun login --no-browser
```

Open the link on any device where you can sign in, click **Allow**, then paste the code the page shows into the terminal.

### See and remove signed-in computers

Every computer that ran `bitsrun login` is listed in the dashboard under **API keys**, in the **Signed-in CLIs** section, with when it was last used. Click **Sign out** next to any you do not recognize. To sign out the computer you are on:

```bash
bitsrun logout
```

Signing in again on the same computer replaces its old session, so you never collect stale ones. More in [Sessions and devices](https://bitsrun.com/docs/account/sessions-and-devices/).

## Your first deploy from the terminal

```bash
bitsrun deploy qwen3:8b --name "Support chat" --key
```

This creates a private endpoint, picks the smallest GPU that fits, and creates an API key that only works with this endpoint. The key is printed once, so save it in your password manager or secret store right away. The output ends with a `curl` command you can paste to try it. [Call your endpoint](https://bitsrun.com/docs/get-started/call-your-endpoint/) explains the next steps.

## Keep bitsrun up to date

```bash
bitsrun upgrade
```

It downloads the latest version, checks it against a signed list of checksums, and swaps the file in place. If you installed with npm, update with `npm install -g bitsrun@latest` instead.

## What can go wrong

| What you see | What to do |
|---|---|
| `bitsrun: command not found` | Open a new terminal window. If it still fails, add `~/.local/bin` (macOS, Linux) to your PATH. |
| `You are not signed in. Run bitsrun login.` | Your session ended or was signed out from the dashboard. Run `bitsrun login` again. |
| The browser does not open | Copy the link bitsrun printed into any browser, or use `bitsrun login --no-browser`. |
| `We could not replace ...` during upgrade | Run the install script again, or upgrade with the same permissions you used to install. |

Errors from your account show a **Request id for support**. Include it when you write to support@bitsrun.com.