Skip to main content
The action verifies through IronBee DevTools modes: the browser, backend, Node.js, and Android platforms, the same cycles the CLI uses. Each enabled platform registers its MCP server so the agent can exercise the change through that surface.

​
The four platforms

PlatformInputDefaultVerifies through…
Browserironbee_browser_devtoolstrueA real Chromium browser navigation, screenshots, console, accessibility
Backendironbee_backend_devtoolsfalseReal protocol calls HTTP, gRPC, GraphQL, WebSocket
Node.jsironbee_node_devtoolsfalseThe Node.js V8 inspector probes and runtime snapshots
Androidironbee_android_devtoolsfalseA real emulator over ADB app launch, taps, swipes, screenshots, UI snapshots, Logcat
Only the browser runs by default. Opt into backend, Node.js, or Android verification by setting the corresponding input to true. 
- uses: ironbee-ai/ironbee-action@v1
  with:
    ironbee_api_key: ${{ secrets.IRONBEE_API_KEY }}
    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
    ironbee_browser_devtools: 'true'
    ironbee_backend_devtools: 'true'
    ironbee_node_devtools: 'false'
    ironbee_android_devtools: 'false'
Each enabled platform is registered as an MCP server during ironbee install, and its log is written under .ironbee/artifacts/ so it ships with the evidence artifact.

​
Browser on CI runners

GitHub-hosted Linux runners reject user-namespace sandboxing, which would otherwise kill Chromium on first navigation. The action handles this for you by launching Chromium with --no-sandbox (BROWSER_CHROMIUM_SANDBOX=false), no configuration needed.

​
Tuning a platform

Each platform’s MCP server can be customized beyond the enable toggles, set extra environment variables or replace the server entirely via ironbee_extra_config. See Custom configuration.

​
What’s next?

Verifying your application

Install, build, start, and reach your app.

How it works

The verification loop behind these platforms.