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

> ## Agent Instructions
> IronBee (ironbee.ai) is an AI QA engineer: it verifies code changes against the running app and keeps the evidence. It is not related to the IronBee open-source web application firewall.
> The console is at https://console.ironbee.ai.
> Install the CLI with `npm install -g @ironbee-ai/cli`, sign in with `ironbee login`, and set up a project with `ironbee install`.
> In GitHub workflows, use the action as `ironbee-ai/ironbee-action@v1` and pass the `IRONBEE_API_KEY` secret as the `ironbee_api_key` input.
> In GitLab pipelines, include the component `gitlab.com/ironbee-ai/ironbee-gitlab/verify@v1`; it reads the `IRONBEE_API_KEY` CI/CD variable by default.
> In Bitbucket Pipelines, run the pipe `docker://ghcr.io/ironbee-ai/ironbee-bitbucket:v1` and pass `IRONBEE_API_KEY: $IRONBEE_API_KEY` and `BITBUCKET_OAUTH_TOKEN: $BITBUCKET_OAUTH_TOKEN` under its `variables:`.
> Console scenarios (https://docs.ironbee.ai/console/scenarios) and CLI saved scenarios (https://docs.ironbee.ai/cli/guides/scenarios) are separate features.
> For plans and prices, link to https://ironbee.ai/pricing; the website is the source of truth for them.

# Local-mode platforms in Bitbucket

> Choose the IronBee DevTools platforms the agent verifies through when the Bitbucket Pipe runs the verification on your runner.

When the verification runs inside the pipe (local mode), the agent verifies through IronBee DevTools, the same platforms the [CLI uses](https://docs.ironbee.ai/cli/concepts/how-it-works.md). You choose which platforms it gets.

> [!NOTE]
>
> These variables apply to local mode only. On IronBee, the run verifies your web app in a browser, and the pipe logs a warning if you set them. See [Platform and local verification](https://docs.ironbee.ai/bitbucket-pipe/concepts/verification-modes.md).

***

## The platforms

| Platform | Variable | Default | Verifies through |
| - | - | - | - |
| Browser | `IRONBEE_BROWSER_DEVTOOLS` | `"true"` | A real Chromium browser: navigation, DOM, console, accessibility, screenshots, recording |
| Backend | `IRONBEE_BACKEND_DEVTOOLS` | `"false"` | Real protocol calls: HTTP, gRPC, GraphQL, WebSocket, databases, logs |
| Node.js | `IRONBEE_NODE_DEVTOOLS` | `"false"` | The Node.js runtime: tracepoints, exceptions, variables, HTTP capture |
| Python | `IRONBEE_PYTHON_DEVTOOLS` | `"false"` | The Python runtime through debugpy: tracepoints, exceptions, logs, thread dumps |
| Terminal | `IRONBEE_TERMINAL_DEVTOOLS` | `"false"` | CLI, REPL and TUI programs, driven through a pseudo-terminal |

Only the browser runs by default. Turn on the others when those layers are part of the change:

```yaml theme={null}
- pipe: docker://ghcr.io/ironbee-ai/ironbee-bitbucket:v1
  variables:
    IRONBEE_API_KEY: $IRONBEE_API_KEY
    ANTHROPIC_API_KEY: $ANTHROPIC_API_KEY
    BITBUCKET_OAUTH_TOKEN: $BITBUCKET_OAUTH_TOKEN
    VERIFICATION_MODE: "local"
    IRONBEE_BROWSER_DEVTOOLS: "true"
    IRONBEE_BACKEND_DEVTOOLS: "true"
```

> [!WARNING]
>
> The terminal platform gives the agent a shell in the pipe. Turn it on only when a command-line program is what you are verifying.

All enabled platforms are served by one `ironbee-devtools` MCP server. Its log is written to `.ironbee/artifacts/ironbee-devtools-mcp.log` and kept with the step's [evidence](https://docs.ironbee.ai/bitbucket-pipe/advanced/evidence.md).

***

## Browser in a pipe

The pipe launches Chromium with its sandbox off, because a pipe's container has no user namespaces for Chromium to sandbox with. No configuration is needed.

Chromium and its system dependencies are installed on every run in local mode. To keep the browser between runs, add a custom cache; see [Caching](https://docs.ironbee.ai/bitbucket-pipe/configuration/configuration.md#caching). Local mode's Chromium and Claude Code run inside the pipe, so on a step with Docker Compose they share the Docker service's memory with your app.

***

## Tuning a platform

To pass extra environment variables to the DevTools server, or to change other CLI settings, use `IRONBEE_EXTRA_CONFIG`. See [Custom configuration](https://docs.ironbee.ai/bitbucket-pipe/advanced/custom-configuration.md).

***

## What's next?

> [card] [Verifying your application](https://docs.ironbee.ai/bitbucket-pipe/guides/verifying-your-app.md)
>
> Choose the target and how to reach it.

> [card] [Custom configuration](https://docs.ironbee.ai/bitbucket-pipe/advanced/custom-configuration.md)
>
> Tune the DevTools server and other CLI settings.


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