Skip to main content
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, from the IRONBEE_JOB_URL output, or from the project’s Verifications tab. See Verification detail.

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: 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:
  • 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.
The report’s links point at console.ironbee.ai. To use a different host, set ironbee_console_url to the hostname, without a scheme:

What’s next?

Running in GitLab CI/CD

Pipeline sources, fixes and the report.

Diagnostics

Find out why a run didn’t behave as expected.