These variables apply to local mode only. On IronBee, the run verifies your web app in a browser, and the pipe 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 kept with the step’s evidence.
Browser in a pipe
The pipe launches Chromium with its sandbox off, because a pipe’s container has no user namespaces for Chromium to sandbox with. No configuration is needed. Chromium and its system dependencies are installed on every run in local mode. To keep the browser between runs, add a custom cache; see Caching. Local mode’s Chromium and Claude Code run inside the pipe, so on a step with Docker Compose they share the Docker service’s memory with your app.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.