Skip to main content
Run a named cloud operation. The example is a local preview. Without --dry-run, the named operation runs with your configured access and may write data. The CLI presents no confirmation prompt; server approval requirements still apply.

​
Example

Prints a proposed list_projects request without a network call or credential. Dry-run reads local configuration and does not validate arguments against the server schema.

​
Options

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

​
Exit status

0 on success; 2 on usage, configuration, input or request failure.
Runs the named cloud operation and prints its decoded JSON result on stdout. API-key connections call POST /v1/commands/NAME.Saved CLI OAuth connections call the named MCP tool; their tokens never become REST credentials. Arguments come from --args JSON_OBJECT, --file FILE or repeated --set PATH=VALUE assignments.Dotted paths select nested fields; values parse as JSON when possible. A retired command name resolves to its canonical name from the bundled catalog.Execution requires a configured HTTPS origin and usable API-key or saved OAuth credentials.--dry-run reads local configuration and prints the command, arguments, scopes and read/write class without a request or credential. It does not validate arguments against the server schema. -y and --yes are accepted; the current generic call presents no confirmation prompt, and server approval requirements still apply.With --json or nonterminal stdout, service failures go to stderr as {error: …}. REST preserves the public server envelope; OAuth filters credential-like content before displaying it.Recovery fields, including details.next, are optional. Local parser, argument-file and configuration failures can use text on stderr.Generic calls do not automatically retry an uncertain operation.
With the configured origin and a credential holding projects:read, prints the server result as JSON on stdout. Service errors go to stderr; inspect their code and optional recovery details.
Read configuration and file ownership for environment variables, compatibility aliases and writer locks. Read local file contracts for artifact fields. Browse the CLI index for related commands.
Check the selected environment and workspace access before calling hosted operations. See capability status.