Autopilot Suites (CLI)

# Generate a suite (manual trigger, no schedule)
obs suite generate https://example.com --name "Smoke Tests" --max-tests 5

# Generate with a cron schedule
obs suite generate https://example.com --cron "0 */6 * * *"

# Pass plain variables to the test runner
obs suite generate https://example.com --var USERNAME=admin

# Pass a secret without putting it on the command line: omit =VALUE and the
# CLI prompts for it with a hidden input, keeping it out of shell history and ps
obs suite generate https://example.com --var PASSWORD

# Or load several at once from a file
obs suite generate https://example.com --var-file .env.test

# List all suites
obs suite list

# Get full suite details (tests, variables, schedule)
obs suite get <id>

# Trigger a run and stream results
obs suite run <id> --wait

# Check the latest execution status
obs suite status <id>

# Wait on a specific execution
obs suite wait <id> <executionId>

# Delete a suite (-y skips the confirmation prompt)
obs suite delete <id> -y

# Show current binding (provider, repo, branch, hooks, masked token, last fired)
obs suite ci status <id>

# Generate or rotate the inbound webhook token (each call invalidates the previous one)
obs suite ci webhook-token <id> -y

# Tear down the integration (invalidates the token, unbinds the repo)
obs suite ci disconnect <id> -y

TOKEN=$(obs suite ci webhook-token 42 -y --json | jq -r '.data.token')
gh secret set OBS_WEBHOOK_TOKEN -b "$TOKEN" --repo acme/marketing-site