> ## 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 GitLab

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

When the verification runs on your GitLab runner (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 inputs apply to local mode only. On IronBee, the run verifies your web app in a browser, and the component logs a warning if you set them. See [Platform and local verification](https://docs.ironbee.ai/gitlab-component/concepts/verification-modes.md).

***

## The platforms

| Platform | Input | 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}
include:
  - component: gitlab.com/ironbee-ai/ironbee-gitlab/verify@v1
    inputs:
      verification_mode: local
      ironbee_browser_devtools: 'true'
      ironbee_backend_devtools: 'true'
```

> [!WARNING]
>
> The terminal platform gives the agent a shell on the runner. 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 ships with the job's [evidence artifacts](https://docs.ironbee.ai/gitlab-component/advanced/evidence.md).

***

## Browser on GitLab runners

A GitLab Docker job has no user namespaces for Chromium to sandbox with, so Chromium would stop on its first navigation. The component launches it with its sandbox off for you. No configuration is needed.

Chromium and its system dependencies are installed with `apt-get`, so a custom `image` needs Node 22, bash, git, curl and apt-get. The browser is cached between runs; see [Caching](https://docs.ironbee.ai/gitlab-component/configuration/configuration.md#caching).

***

## 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/gitlab-component/advanced/custom-configuration.md).

***

## What's next?

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

> [card] [Custom configuration](https://docs.ironbee.ai/gitlab-component/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.