Skip to content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Probo Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

Probo CLI

Install prb and manage Probo from a terminal, script, or CI job

View as Markdown

The Probo CLI, prb, lets you work with Probo from a terminal, shell script, or CI job. It covers organizations, frameworks, controls, risks, audits, documents, access reviews, privacy records, webhooks, devices, and administration.

Installation

Section titled “Installation”
Terminal window
brew install getprobo/tap/prb

Verify the installation:

Terminal window
prb version

Sign in and run a command

Section titled “Sign in and run a command”

  1. Sign in

    Terminal window
    prb auth login

    Choose Probo EU, Probo US, or a self-hosted deployment. The CLI starts an OAuth device authorization flow and can save a default organization.

  2. Check the active host

    Terminal window
    prb auth status

  3. List a resource

    Terminal window
    prb framework list

Run prb <command> --help to inspect flags and examples for your installed version.

Global flags

Section titled “Global flags”
Flag Environment equivalents Effect
--no-interactive PROBO_NO_INTERACTIVE=1, CI=true, DEBIAN_FRONTEND=noninteractive, TERM=dumb Disable interactive prompts
--no-color NO_COLOR, TERM=dumb Disable ANSI color output

The CLI also becomes non-interactive when standard input or output is not a terminal. Commands that require confirmation then need their explicit confirmation flag, such as --yes.

Use the CLI in automation

Section titled “Use the CLI in automation”

Use the flags exposed by the specific command. Common patterns include:

  • --json or --output json for machine-readable output on commands that support it.
  • --org <organization-id> to override the default organization.
  • --limit, --order-by, and --order-direction on list commands that expose pagination and sorting.
  • --no-interactive --no-color for deterministic CI output.

For temporary credentials, set PROBO_HOST and PROBO_TOKEN. Avoid printing the token, passing it as a command-line argument, or writing it into a repository. See Configuration for precedence and behavior.

Explore the CLI

Section titled “Explore the CLI”
Authentication Sign in, switch deployments, and manage stored credentials
Configuration Configure tools, timeouts, prompts, hosts, and environment overrides
Autocomplete Complete prb commands and flags in your shell
Command reference Browse every command generated from the current CLI source