These inputs apply to local mode only. On IronBee, the run verifies your web app in a browser, and the component 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:
ironbee-devtools MCP server. Its log is written to .ironbee/artifacts/ironbee-devtools-mcp.log and ships with the job’s evidence artifacts.
Browser on GitLab runners
A GitLab Docker job has no user namespaces for Chromium to sandbox with, so Chromium would stop on its first navigation. The component launches it with its sandbox off for you. No configuration is needed. Chromium and its system dependencies are installed withapt-get, so a custom image needs Node 22, bash, git, curl and apt-get. The browser is cached between runs; see Caching.
Tuning a platform
To pass extra environment variables to the DevTools server, or to change other CLI settings, useironbee_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.