Temporal
Give the Sazabi agent the Temporal CLI (temporal) in its sandbox to connect to and inspect your Temporal Cloud namespace.
About
This CLI connection makes the Temporal CLI (temporal) available in the Sazabi agent's sandbox. The agent can use it against your Temporal Cloud namespace. The tool is baked into the sandbox image; connecting it authenticates (or configures the connection for) the already-installed CLI.
Prerequisites
- A Sazabi project.
- Your Temporal Cloud namespace address (
TEMPORAL_ADDRESS, e.g.<namespace>.<accountId>.tmprl.cloud:7233) and a Temporal Cloud API key (TEMPORAL_API_KEY).
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Temporal in the catalog
In Settings > Sandbox CLIs, find Temporal under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required values: TEMPORAL_ADDRESS (your Temporal Cloud namespace endpoint, including the port) and TEMPORAL_API_KEY (your Temporal Cloud API key). Save to store them securely; Sazabi injects them into the sandbox when the agent runs.
Set up with the CLI
You can also configure the Temporal CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type temporal --env TEMPORAL_ADDRESS=<your-namespace-address> --env TEMPORAL_API_KEY=<your-temporal-key>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 temporal CLI (a read-only or status command) and confirm it returns real output. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated or cannot connect, recheck the credentials.
Troubleshooting
Command not found — Confirm the Temporal CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.