vulkro cloud

Work the Vulkro Cloud issue queue for your code repositories from the terminal: connect to a workspace or to Pro Cloud, list what to fix, triage, assign and start cloud scans.

vulkro cloud connect https://<name>.vulkro.com   # a workspace
vulkro cloud connect --pro                       # Pro Cloud, after vulkro login
vulkro cloud todo --fail-on high

Subcommands

Command	What it does
connect [<url>] [--pro] [--allow-scans] [--no-browser]	Approve this machine in the browser (workspace) or use your Vulkro sign-in (--pro). --allow-scans asks for core:write so scan works in a workspace.
status	The connected cloud and who you are.
disconnect	Forget the connection on this machine.
repos	Repositories you can see, with open issues and gate.
todo	The queue, ranked. --repo, --branch, --severity, --view, --rule, --risk, --search, --limit, --fail-on <severity>.
show <fingerprint> [--evidence]	One issue, with its trace hops when asked.
triage <fingerprint> --state <state> [--reason ...] [--expires <date>]	Set or propose a triage state.
assign <fingerprint> <me|member id|none>	Workspace only.
scan [--repo ...] [--branch ...] [--wait] [--timeout ...]	Start a cloud scan. With no --repo, the repository matching this checkout's origin remote.

Every command takes --json. The connection is saved to ~/.vulkro/cloud.json; in CI set VULKRO_CLOUD_URL and VULKRO_CLOUD_TOKEN instead. No local licence is needed: the workspace or your Pro plan is the entitlement.

Exit codes

Code	Meaning
0	Success.
1	todo --fail-on found issues, a scan --wait failed its quality gate, or Pro Cloud refused for no plan (vulkro: license_required).
2	Error.

See Connect the CLI.