> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dropbear.dreamscalelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat the Dropbear Python SDK and CLI as the supported public integration surfaces.
> Prefer context-managed sessions and model-specific observation helpers.
> Do not infer or recommend internal control-plane APIs.

# Installation

> Install the Dropbear SDK and CLI, authenticate, and keep the launch package up to date.

Dropbear `0.1.0a2` supports Python 3.11 through 3.14 for cloud policy
inference. Install only the extras required by your local robot or simulator
stack.

## Choose an install

<CodeGroup>
  ```bash uv (recommended) theme={null}
  uv add "dropbear==0.1.0a2"
  uv tool install "dropbear==0.1.0a2"
  ```

  ```bash pip theme={null}
  python -m pip install "dropbear==0.1.0a2"
  ```
</CodeGroup>

The base package includes the Python SDK, CLI, transport, and observation
helpers. Pin the exact version while the SDK is pre-release.

| Install           | Use it for                                             | Compatibility    |
| ----------------- | ------------------------------------------------------ | ---------------- |
| `dropbear`        | Existing robot controllers and cloud inference         | Python 3.11–3.14 |
| `dropbear[so101]` | Dropbear's SO-101 setup, calibration, and dry-run path | Python 3.12–3.13 |
| `dropbear[sim]`   | The local `dropbear sim` LIBERO path                   | Linux or WSL2    |

Install an extra in the project that owns the corresponding hardware or
simulator:

<CodeGroup>
  ```bash SO-101 theme={null}
  uv add "dropbear[so101]==0.1.0a2"
  ```

  ```bash Local LIBERO theme={null}
  uv add "dropbear[sim]==0.1.0a2"
  ```
</CodeGroup>

<Note>
  Your own Franka or simulator integration should use its existing controller
  dependencies plus the base `dropbear` package. Dropbear does not provide a
  Franka controller.
</Note>

## Sign in

Browser login is the default:

```bash theme={null}
dropbear login
```

The CLI opens a one-time approval page. After approval, it verifies the
credential and writes `~/.dropbear/config.toml` with user-only permissions.

For a headless machine, paste an API key into the hidden prompt:

```bash theme={null}
dropbear login --api-key
```

You can also pass an API key as the option value, but shell history and process
inspection can expose it. Prefer the hidden prompt or an existing secret
manager.

<Warning>
  Do not commit `~/.dropbear/config.toml`, paste keys into source files, or log
  them in CI. Create and revoke keys in the
  [dashboard](https://dropbear.dreamscalelabs.com/dashboard/keys).
</Warning>

## Verify the machine

```bash theme={null}
dropbear doctor
dropbear status
```

`doctor` checks the robot-neutral installation, authentication, and network
path. `status` reports live model-region capacity without opening a session.

If either command fails, use the command's printed recovery step and then open
[Troubleshooting](/troubleshooting).

## Upgrade

Update both the project dependency and standalone CLI so their behavior stays
aligned:

<CodeGroup>
  ```bash uv theme={null}
  uv add --upgrade "dropbear==0.1.0a2"
  uv tool upgrade dropbear
  dropbear --help
  ```

  ```bash pip theme={null}
  python -m pip install --upgrade "dropbear==0.1.0a2"
  dropbear --help
  ```
</CodeGroup>

You are ready when `dropbear --help` lists `login`, `doctor`, `sim`, `status`,
`run`, `robots`, and `sessions`.

Continue to the [Python quickstart](/quickstart) to request one non-actuating
prediction.