Sazabi
Sandbox CLIs

DBOS Cloud

Give the Sazabi agent the DBOS Cloud CLI (dbos-cloud) in its sandbox to manage durable workflow applications.

About

This CLI connection makes the DBOS Cloud CLI (dbos-cloud) available in the Sazabi agent's sandbox. The agent can use it to manage durable workflow applications. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.

Prerequisites

  • A Sazabi project.
  • A DBOS Cloud refresh token (DBOS_CLOUD_REFRESH_TOKEN), obtained by authenticating with dbos-cloud login and copying the resulting refresh token from your DBOS Cloud account.

Set up in the dashboard

Configure the sandbox in the dashboard under Settings > Sandbox CLIs.

Find DBOS Cloud in the catalog

In Settings > Sandbox CLIs, find DBOS Cloud under Browse sandbox CLIs and choose to connect it.

Provide credentials

Enter the required value: DBOS_CLOUD_REFRESH_TOKEN — the refresh token for your DBOS Cloud account. Save to store it securely; Sazabi injects it into the sandbox when the agent runs.

Set up with the CLI

You can also configure the DBOS Cloud CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).

sazabi sandbox-clis set --type dbos-cloud --env DBOS_CLOUD_REFRESH_TOKEN=<your-refresh-token>

To validate the credentials without saving, run the same command with test in place of set (the test command also requires the --env flags).

Verify

Ask the agent, in a thread, to run the dbos-cloud CLI (a read-only or status command) and confirm it returns real output from your account. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated, recheck the credentials.

Troubleshooting

Command not found — Confirm the DBOS Cloud CLI connection is enabled for the project under Settings > Sandbox CLIs.

Authentication fails — Recheck the credential values; a rotated or revoked token must be re-entered under Settings > Sandbox CLIs or with sazabi sandbox-clis set --type dbos-cloud.

Further reading