Skip to main content
Dated evidence: an authenticated request to the hosted catalog returned HTTP 404 on 2026-09-14T01:46:46.905Z. Later releases deployed the generic command routes: production version 6b10560e (deployed 2026-09-20T16:54:01.875157Z from commit 732cadc) serves 125 authenticated commands according to its source and release receipt. Read GET /v1/commands with your credential before depending on a command. See capability status and release evidence.

Behavior and output

Calls POST /v1/commands/NAME and prints the decoded JSON response. Arguments come from —args JSON_OBJECT, —file FILE, or one or more —set PATH=VALUE overlays (dotted paths; values parse as JSON when they can). A retired command name resolves to its canonical command from the catalog snapshot before the request. —dry-run prints the resolved command, arguments, scopes and read/write class without sending anything. -y answers confirmations that later commands may ask for. Requires a configured HTTPS origin and credential. Every failure is one JSON error object with code, message and next when stdout is not a terminal.

Arguments

NAME required; —args JSON_OBJECT, —file FILE or —set PATH=VALUE (repeatable), mutually exclusive with each other; —dry-run; -y; —json.

Exit status

0 on success; 2 on usage, configuration, input or request failure. Read configuration and file ownership before automating this command. Read local file contracts for artifact fields. Browse the local command index for related commands.
Check the selected environment and workspace access before calling hosted operations. See capability status.