Output and errors

Default output

tab open prints the created tab ID:

$ radius tab open https://example.com
tab_42

This makes IDs easy to capture:

tab="$(radius tab open https://example.com)"
radius tab focus "$tab"

Other successful mutations are silent by default. Query commands print human-readable output.

Add --json when a script or agent needs structured output:

radius tab open https://example.com --json

{
  "id": "tab_42",
  "tabId": "tab_42",
  "workspaceRevision": 92
}

For concurrency guards and event-oriented output, see JSON and concurrency.

Human-readable errors are written to stderr:

TAB_NOT_FOUND: Tab tab_42 is not live

With --json, stderr contains a machine-readable error:

{
  "error": {
    "code": "TAB_NOT_FOUND",
    "message": "Tab tab_42 is not live"
  }
}

Common errors include:

Error	Meaning
`RADIUS_NOT_RUNNING`	Radius is not running or ready.
`INSTANCE_AMBIGUOUS`	More than one Radius instance is running.
`WINDOW_NOT_FOUND`	The window is no longer available.
`GROUP_NOT_FOUND`	The group is no longer available.
`TAB_NOT_FOUND`	The tab is no longer available.
`INVALID_SPLIT`	The requested split cannot be created.
`COMMAND_TIMEOUT`	The command did not finish before its timeout.
`INVALID_REQUEST`	The command or its arguments are invalid.

Status	Meaning
`0`	Success
`1`	Runtime or command failure
`2`	Invalid command or arguments
`3`	Window, group, or tab not found
`4`	Revision or command conflict
`5`	Connection or instance-selection failure

Scripts should branch on the exit status or error code rather than parsing the message text.