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

# Evidence in GitLab

> Where the recording, screenshots, logs and report of each GitLab component run are, on IronBee and in the job's artifacts.

Every run keeps the evidence behind its verdict. Where you find it depends on where the verification ran.

***

## Runs on IronBee

The evidence of a run on IronBee is in the IronBee Console:

* the recording
* screenshots
* the actions the agent took
* network requests, traces and logs

Open it from the **View session in IronBee Console** link in the [report](https://docs.ironbee.ai/gitlab-component/guides/running-in-ci.md#the-report), from the `IRONBEE_JOB_URL` output, or from the project's **Verifications** tab. See [Verification detail](https://docs.ironbee.ai/console/verification-detail.md).

***

## The job's artifacts

The job uploads one artifact archive, `ironbee-verification-evidence`, whether the job passes or fails. GitLab keeps it for 30 days. Browse it from the job's page, under **Job artifacts**. It holds:

| File | When |
| - | - |
| `report.md` | Every run: the report, since GitLab has no job summary |
| `app.log` | When the component started your app: the app's output |
| `app-service-logs.txt` | When you set `app_logs_command`: the app's own logs |
| The verification evidence | Local mode, when the run produced any. See below |

Use the app logs when a verification fails because the app itself stopped or errored.

### Runs on your runner

A run on your runner records to the IronBee Console and also puts its evidence in the artifact:

```
cycle-1/
  screenshots/
  recordings/
cycle-2/
  screenshots/
  recordings/
claude-output.log
ironbee-devtools-mcp.log
sessions/<id>/        # agents/<agentId>/: verdict.json, actions.jsonl
```

* Screenshots and recordings are grouped by verification cycle.
* `claude-output.log` holds the agent's output.
* `ironbee-devtools-mcp.log` is the DevTools server's log.

The report links to the artifacts, and the `IRONBEE_ARTIFACTS_URL` output carries the link for later jobs.

***

## Console links

The report's links point at `console.ironbee.ai`. To use a different host, set `ironbee_console_url` to the hostname, without a scheme:

```yaml theme={null}
include:
  - component: gitlab.com/ironbee-ai/ironbee-gitlab/verify@v1
    inputs:
      ironbee_console_url: 'console.example.com'
```

***

## What's next?

> [card] [Running in GitLab CI/CD](https://docs.ironbee.ai/gitlab-component/guides/running-in-ci.md)
>
> Pipeline sources, fixes and the report.

> [card] [Diagnostics](https://docs.ironbee.ai/gitlab-component/advanced/diagnostics.md)
>
> Find out why a run didn't behave as expected.


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