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

# Platform and local verification in GitLab

> Where the GitLab component runs the verification, how it picks from the project's visibility, and which inputs apply to each mode.

The IronBee GitLab component can run the verification in two places:

* **Platform mode:** on IronBee. The console calls this **On IronBee**.
* **Local mode:** on your GitLab runner. The console calls this **On your GitLab runner**.

Everything after the verification works the same way in both modes: the verdict, the fix, the commit and the report. Only a run on IronBee can be [published on the merge request](https://docs.ironbee.ai/gitlab-component/guides/running-in-ci.md#the-report) by IronBee itself. The `verification_mode` input picks the mode: `auto` (the default), `platform` or `local`.

***

## Compare the two modes

| | Platform (on IronBee) | Local (on your runner) |
| - | - | - |
| Where the agent runs | IronBee's infrastructure | Your GitLab runner |
| Model access | IronBee's | Your Anthropic API key or Claude Code OAuth token |
| Runner setup | None: no Chromium, no DevTools install | Chromium, IronBee DevTools and Claude Code, installed on every run |
| Anthropic credential | Only to fix what it finds | Required |
| What it verifies | Your web app, in a browser | The [DevTools platforms](https://docs.ironbee.ai/gitlab-component/guides/verification-platforms.md) you enable: browser, backend, Node.js, Python, terminal |
| Evidence | The IronBee Console | The IronBee Console and the job's artifacts |
| Private projects | Need the project's group [connected to IronBee](https://docs.ironbee.ai/integrations/gitlab.md) | Work with any checkout |

***

## How `auto` decides

With `verification_mode: auto`, the component decides from two things it can check without calling IronBee: the project's visibility, and whether an Anthropic credential is set.

| Project visibility | Anthropic credential | Mode |
| - | - | - |
| Public | Any | Platform. IronBee can check out a public project without the GitLab connection |
| Private or internal | Set | Local. The component can't check whether the GitLab connection covers the project, so it uses the engine it knows can run |
| Private or internal | Not set | Platform, the only engine available. This needs the project's group connected to IronBee |

The first line of the plan in the job log names the mode and the reason.

> [!TIP]
>
> If your project is private or internal and its group is [connected to IronBee](https://docs.ironbee.ai/integrations/gitlab.md), set `verification_mode: platform` explicitly. Otherwise `auto` runs on your runner whenever an Anthropic credential is set.

A private project whose group isn't connected can still be verified on IronBee: set `ironbee_bind_repository: 'false'` to verify the running application without a checkout of the repository.

***

## Inputs that apply to one mode

The component warns in the job log when you set an input that doesn't apply to the mode it runs in.

**Platform mode only**

| Input | Purpose |
| - | - |
| `ironbee_project` | The project the run reports to. Empty derives it from the git remote |
| `ironbee_environment` | The project environment whose variables and secrets the run uses |
| `ironbee_bind_repository` | Bind the run to the repository so it verifies the changeset |
| `ironbee_job_timeout_minutes` | The run's timeout on IronBee |
| `app_restart_command`, `app_logs_command`, `app_wait_seconds` | An app that runs on the runner, reached through a tunnel |
| `app_headers`, `app_secret_headers` | Request headers for a deployed URL |

**Local mode only**

| Input | Purpose |
| - | - |
| `ironbee_browser_devtools`, `ironbee_backend_devtools`, `ironbee_node_devtools`, `ironbee_python_devtools`, `ironbee_terminal_devtools` | The DevTools platforms the agent verifies through |
| `ironbee_extra_config` | Raw IronBee CLI config. See [Custom configuration](https://docs.ironbee.ai/gitlab-component/advanced/custom-configuration.md) |
| `claude_code_model`, `claude_code_max_turns`, `claude_code_args` | The Claude Code agent on your runner |

`claude_code_cli_version` and the Anthropic credential also apply to the fix step in platform mode. See [Configuration](https://docs.ironbee.ai/gitlab-component/configuration/configuration.md) for every input.

***

## What's next?

> [card] [How it works](https://docs.ironbee.ai/gitlab-component/concepts/how-it-works.md)
>
> The run from the plan to the report.

> [card] [GitLab](https://docs.ironbee.ai/integrations/gitlab.md)
>
> Connect your GitLab group so IronBee can read private projects.


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