bdy sandbox exec status

$bdy sandbox exec status [options] <identifier> <command-id>

Show the status of a command started with exec Required scopes: SANDBOX_READ

ARGUMENTS

identifier

Sandbox identifier (required)

command-id

Command ID (required)

OPTIONS

--context <name>

Connection and scope context: default, git, link or a saved name. Overrides the globally active context for this invocation.

--examples

Show only examples; with this flag --format accepts text, json or jsonl

--verbose

Show REST API requests, responses, timing and retries on stderr

-w, --workspace <domain>

Workspace URL handle. Can be set via variable: BUDDY_WORKSPACE

-p, --project <name>

Project name. Can be set via variable: BUDDY_PROJECT

--scope <scope>

Force scope (WORKSPACE, PROJECT, ENVIRONMENT). By default calculated by provided options and environmental variables (--project,

--environment

BUDDY_PROJECT, linked project)

-e, --environment <identifier>

Environment identifier

--format <text|json>

Output format: json, text. JSON CLI errors: {error:{code,message,hint}}, exit 1 (2 or 3 with --exit-code). Default: text (choices: "text", "json")

--exit-code

Use semantic exit codes: 0 success, 1 unsuccessful, 2 command error, 3 not found, 8 pending

-h, --help

display help for command

Documentation for bdy v1.25.20

Last modified on Oct 14, 2026

Examples

Return the execution state using semantic exit codes
bdy sandbox exec status sandbox-identifier command-id --exit-code$

Show status of command
bdy sb exec status sandbox-identifier command-id$

Show status of command in sandbox from another workspace
bdy sb exec status sandbox-identifier command-id -w workspace -p project$