Skip to content

Exit codes

b8e follows the grep/eslint convention: 0 clean, 1 findings, 2+ operational error — so a CI step can swallow findings without swallowing a crash. Generated from the CLI_EXIT constant.

NameCodeMeaning
clean0Ran to completion; nothing gated.
findings1Ran, and produced gating findings. This is the code a continue-on-error: true step is meant to swallow when you want findings reported but not blocking.
crash2The tool failed to run to a valid result — an unresolvable --base, a broken baseline, a failure to emit valid SARIF, or an unexpected error. Distinct from findings so a crash is never mistaken for a clean or advisory run.
run3b8e audit, b8e qa audit, b8e build upload and b8e scan only: the command ran, but produced no usable result — no reports came back, or every journey failed. For b8e scan --url with one URL: the page would not load. For b8e qa audit, also any single journey that failed to run or whose results are unavailable. For b8e qa audit stop: no cloud QA run with that id in the project. For b8e build upload: storage refused the upload, or the build registered but its malware scan did not start. For b8e audit --cloud and b8e qa audit --cloud: the CLI lost the service while following a cloud run and stopped following it; the run may still be going in the cloud, and the message names it. A b8e scan that completed keeps its own exit code even when the upload to the dashboard fails, which is reported on stderr instead.
config4The invocation was invalid: no organization context, a missing --project / --journeys / --group in a non-interactive run, a b8e audit or b8e qa audit project that is not in the organization, or an unrecognised value for an enumerated flag such as ci --format or ci --fail-on.
environment5The browser or host environment is not ready to launch a browser.
empty6A whole-tree scan analyzed zero files: it found none to analyze, or every file it found belongs to a stack it does not support (a tree of only Android View-system code). Distinct from clean, because “I checked everything and it is fine” and “I checked nothing” would otherwise both exit 0 — a misconfigured scan must not read as health. Not returned for a --base diff scope, where analyzing nothing is legitimate (a pull request touching only .md).
auth7Not authenticated, or access denied. Not authenticated: no credential the command accepts was present, or Binclusive found no live session behind it, so it did not run. Every command needs one except --help, --version, the auth group and doctor — either a b8e auth login session, or BINCLUSIVE_API_KEY for a non-interactive run. Access denied: Binclusive refused the credential for what the command named, and the message names it; logging in again does not change that.
incomplete8b8e qa audit only: ran, or is still running, and not every step has been checked — blocked, inconclusive, agent or infra error, or skipped. It reported no Finding: a run with any Finding exits 1 instead.