Render
Give the Sazabi agent the Render CLI (render) in its sandbox to manage Render services and deployments.
About
This CLI connection makes the Render CLI (render) available in the Sazabi agent's sandbox. The tool is baked into the sandbox image; connecting it authenticates (or configures the connection for) the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Render API key (
RENDER_API_KEY). Generate one in your Render account settings. Optionally, a Render workspace ID (RENDER_WORKSPACE_ID) to scope operations to a specific workspace.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Render in the catalog
In Settings > Sandbox CLIs, find Render under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: RENDER_API_KEY (your Render API key). Optionally, enter RENDER_WORKSPACE_ID to restrict the CLI to a specific workspace. 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 Render CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type render --env RENDER_API_KEY=<your-render-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 render 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 Render CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.