Fly.io
Give the Sazabi agent the Fly.io CLI (flyctl) in its sandbox to deploy and manage Fly.io applications.
About
This CLI connection makes the Fly.io CLI (flyctl) available in the Sazabi agent's sandbox. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Fly.io API token (
FLY_API_TOKEN), generated fromfly tokens createor the Fly.io dashboard under Account > Access Tokens.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Fly.io in the catalog
In Settings > Sandbox CLIs, find Fly.io under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: FLY_API_TOKEN — your Fly.io API token. Optionally, set FLY_TOKEN_TYPE to override the token type header if required by your token configuration. 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 Fly.io CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type fly --env FLY_API_TOKEN=<your-fly-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 flyctl 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 Fly.io 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 fly.