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
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:
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.logholds the agent’s output.ironbee-devtools-mcp.logis the DevTools server’s log.
IRONBEE_ARTIFACTS_URL output carries the same link.
Console links
The report’s links point atconsole.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.