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 step’s artifacts

The pipe copies what it keeps into .ironbee/upload/. A step keeps only the files its artifacts: names, so list that folder on the step:
With WORKING_DIRECTORY set, the folder is under that directory, such as packages/web-app/.ironbee/upload/**. Open the files from the step’s Artifacts tab in the pipeline. They hold: Use the app logs when a verification fails because the app itself stopped or errored.

Runs on your runner

A run inside the pipe records to the IronBee Console and also puts its evidence in the artifacts:
  • 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 step’s page, and the IRONBEE_ARTIFACTS_URL output carries the same link.
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 Bitbucket Pipelines

Pipelines, fixes and the report.

Diagnostics

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