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

# Bitbucket

> Give the Sazabi agent the Bitbucket CLI (bb) in its sandbox to manage repositories, pull requests, and pipelines.

[All Bitbucket integration capabilities](https://docs.sazabi.com/catalogs/integrations/bitbucket.md)

## About

This CLI connection makes the Bitbucket CLI (`bb`) available in the Sazabi agent's sandbox. The agent can manage repositories, pull requests, and pipelines in your Bitbucket account. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.

## Prerequisites

* A Sazabi project.
* A Bitbucket API token or app password (`BITBUCKET_TOKEN`) and the email address associated with your Bitbucket account (`BITBUCKET_EMAIL`).

## Set up in the dashboard

Configure the sandbox in the dashboard under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis).

**Step 1**

### Find Bitbucket in the catalog

In [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis), find Bitbucket under **Browse sandbox CLIs** and choose to connect it.

**Step 2**

### Provide credentials

Enter the required values: `BITBUCKET_TOKEN` — your Bitbucket API token or app password; `BITBUCKET_EMAIL` — the email address associated with your Bitbucket account. Optionally set `BITBUCKET_WORKSPACE` to default commands to a specific workspace slug. Save to store them securely; Sazabi injects them into the sandbox when the agent runs.

## Set up with the CLI

You can also configure the Bitbucket CLI connection with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/sandbox-clis.md)).

```bash theme={"system"}
sazabi sandbox-clis connect bitbucket --env BITBUCKET_TOKEN=<your-bitbucket-token> --env BITBUCKET_EMAIL=<your-bitbucket-email>
```

To validate the credentials without saving, run the same command with `test` in place of `connect` (the test command also requires the `--env` flags).

## Verify

Ask the agent, in a thread, to run the `bb` CLI (for example `bb repositories list`) and confirm it returns real output from your account. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated, recheck the credentials.

## Troubleshooting

**Command not found** — Confirm the Bitbucket CLI connection is enabled for the project under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis).

**Authentication fails** — Recheck the credential values; a rotated or revoked token must be re-entered under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis) or with `sazabi sandbox-clis connect bitbucket`.

## Further reading

> [card] [Working with the agent](https://docs.sazabi.com/guides/investigate/working-with-the-agent.md)
>
> Put the connected CLI to work in an investigation thread.

> [card] [Set up the sandbox](https://docs.sazabi.com/guides/investigate/sandbox.md)
>
> How the sandbox works and its security model.

> [card] [Sandbox CLIs](https://docs.sazabi.com/catalogs/sandbox-clis.md)
>
> Browse the catalog and connect more tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.