- Platform mode: on IronBee. The console calls this On IronBee.
- Local mode: inside the pipe, on your Bitbucket Pipelines runner. The console calls this On your Bitbucket Pipelines runner.
VERIFICATION_MODE variable picks the mode: auto (the default), platform or local.
Compare the two modes
How auto decides
With VERIFICATION_MODE: auto, the pipe decides from two things it can check without calling IronBee: whether the repository is private, and whether an Anthropic credential is passed.
The first line of the plan in the step log names the mode and the reason.
A private repository whose workspace isn’t connected can still be verified on IronBee: set
IRONBEE_BIND_REPOSITORY: "false" to verify the running application without a checkout of the repository.
Variables that apply to one mode
The pipe warns in the step log when you set a variable that doesn’t apply to the mode it runs in. Platform mode only
Local mode only
CLAUDE_CODE_CLI_VERSION and the Anthropic credential also apply to the fix step in platform mode. See Configuration for every variable.
What’s next?
How it works
The run from the plan to the report.
Bitbucket
Connect your Bitbucket workspace so IronBee can read private repositories.