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 job_url output, or from the project’s Verifications tab. See Verification detail. When the app ran on your runner, the action also uploads the ironbee-application-log artifact. It holds:
  • the app’s output
  • the output of app_logs_command, when you set it
The artifact is kept for 30 days. Use it 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 uploads the ironbee-verification-evidence artifact, kept for 30 days:
  • 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 artifact, and the artifacts_url output carries its download URL for later steps.
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 CI

Triggers, fixes and the report.

Diagnostics

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