Skip to main content
When the verification runs on your GitHub runner (local mode), the agent verifies through IronBee DevTools, the same platforms the CLI uses. You choose which platforms it gets.
These inputs apply to local mode only. On IronBee, the run verifies your web app in a browser, and the action logs a warning if you set them. See Platform and local verification.

The platforms

Only the browser runs by default. Turn on the others when those layers are part of the change:
The terminal platform gives the agent a shell on the runner. Turn it on only when a command-line program is what you are verifying.
All enabled platforms are served by one ironbee-devtools MCP server. Its log is written to .ironbee/artifacts/ironbee-devtools-mcp.log and ships with the evidence artifact.

Browser on CI runners

GitHub-hosted Linux runners reject user-namespace sandboxing, which would otherwise stop Chromium on its first navigation. The action launches Chromium with --no-sandbox for you. No configuration is needed.

Tuning a platform

To pass extra environment variables to the DevTools server, or to change other CLI settings, use ironbee_extra_config. See Custom configuration.

What’s next?

Verifying your application

Choose the target and how to reach it.

Custom configuration

Tune the DevTools server and other CLI settings.