Porter
Give the Sazabi agent the Porter CLI (porter) in its sandbox to inspect and manage porter.run apps, deployments, and logs.
About
This CLI connection makes the Porter CLI (porter) available in the Sazabi agent's sandbox. The agent can use it for porter.run apps, deployments, and logs. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Porter API token (
PORTER_TOKEN), available from your Porter account settings. - Optionally:
PORTER_PROJECT— your Porter project ID, to scope commands to a specific project.PORTER_CLUSTER— your Porter cluster ID, to scope commands to a specific cluster.PORTER_HOST— the Porter API host, if you are using a self-hosted Porter instance.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Porter in the catalog
In Settings > Sandbox CLIs, find Porter under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: PORTER_TOKEN — your Porter API token. Optionally, provide PORTER_PROJECT, PORTER_CLUSTER, and/or PORTER_HOST to narrow the scope or point at a self-hosted instance. 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 Porter CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type porter --env PORTER_TOKEN=<your-porter-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 porter 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 Porter CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.