Custom configuration

Most behavior is controlled by the action’s dedicated inputs. For anything else, ironbee_extra_config passes raw JSON that is deep-merged into the .ironbee/config.json the action generates. Your keys win over the defaults.

ironbee_extra_config applies to local mode only, when the verification runs on your runner. On IronBee, the action logs a warning and ignores it.

How it works

Pass a JSON object as a string. It’s merged on top of the configuration the action generates, so you only list the keys you want to change:

- uses: ironbee-ai/ironbee-action@v1.1.0
  with:
    ironbee_api_key: ${{ secrets.IRONBEE_API_KEY }}
    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
    verification_mode: local
    ironbee_extra_config: |
      {
        "maxRetries": 5
      }

Any key from the IronBee CLI configuration is accepted. See the CLI configuration reference for the full set. During the run, the action writes its own .ironbee/config.json, so a configuration file committed to your repository isn’t used. The action restores your file when the run ends.

Tuning the DevTools server

The local-mode platforms are served by one ironbee-devtools MCP server. Pass extra environment variables to it under ironbeeDevTools.env:

- uses: ironbee-ai/ironbee-action@v1.1.0
  with:
    ironbee_api_key: ${{ secrets.IRONBEE_API_KEY }}
    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
    verification_mode: local
    ironbee_extra_config: |
      {
        "ironbeeDevTools": { "env": { "BROWSER_HEADLESS_ENABLE": "true" } }
      }

See the CLI’s DevTools MCP overrides for the keys the server accepts.

IronBee always sets its own invariants (the tool-name prefix, metadata flags and platform) last. They can’t be overridden through ironbee_extra_config.

Integrations

GitHub Action

Custom configuration

How it works

Tuning the DevTools server

What’s next?

Local-mode platforms

Configuration

​How it works

​Tuning the DevTools server

​What’s next?

Local-mode platforms

Configuration

How it works

Tuning the DevTools server

What’s next?