bru run accepts options for environments, data files, request filtering, security, and reporting. Add them after the files or folders you want to run:
Options
Basic options
Setup options
See Running a Collection with Environments for more details.
Request options
Secret Manager options
The
--secrets-env-file flag is used together with --env when your environment file has an externalSecrets block configured. See Secret Managers for credential file formats and full usage examples for each provider.
SSL & Security options
--noproxy bypasses every proxy for a single run, and --client-cert-config points to a JSON file describing per-domain client certificates. The CLI does not read certificates from the desktop app’s Preferences, so mTLS in CI always goes through this flag. See Proxy & mTLS for the config file format and how CLI certificates are merged with the ones in bruno.json.
Output & Reporting options
The three reporter flags can be combined in one run to produce several formats at once, and the
--reporter-skip-* flags let you keep credentials and payloads out of the artifacts you publish in CI. See Reports for the output of each format, including the v4 change to the JUnit classname attribute.
Next Steps
Now that you’re familiar with the command options, explore these guides to get the most out of Bruno CLI:- Run Collections - Worked examples for every way to run a collection with the options above
- Reports - Create detailed test reports in multiple formats
- Proxy & mTLS - Route requests through a proxy and configure client certificates
- Secret Managers - Fetch secrets from HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault at runtime
- bru import - Import OpenAPI and WSDL specifications into Bruno collections
- bru docs - Generate and publish standalone HTML API documentation from the CLI