ironbee_extra_config passes raw JSON that is deep-merged into the .ironbee/config.json the component 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 component 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 component generates, so you only list the keys you want to change:.ironbee/config.json, so a configuration file committed to your repository isn’t used. With ironbee_exclude_files on, the default, the component restores your file when the run ends.
Tuning the DevTools server
The local-mode platforms are served by oneironbee-devtools MCP server. Pass extra environment variables to it under ironbeeDevTools.env:
IronBee always sets its own invariants (the tool-name prefix, metadata flags and platform) last. They can’t be overridden through
ironbee_extra_config.Committing the generated setup
The changes IronBee’s setup makes to.claude/, .mcp.json and .gitignore stay out of the commits the component makes, because they’re its working files rather than the change being verified. To commit the setup it generated together with a fix, for example to use it for local development, set ironbee_exclude_files: 'false'. A run that commits no fix commits no setup either. .ironbee/ stays out either way.
What’s next?
Local-mode platforms
The platforms the DevTools server provides.
Configuration
Every input and output, with defaults.