Sentry
Give the Sazabi agent the Sentry CLI (sentry-cli) in its sandbox to upload source maps, manage releases, and interact with your Sentry organization.
About
This CLI connection makes the Sentry CLI (sentry-cli) 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 Sentry auth token (
SENTRY_AUTH_TOKEN). Create one in your Sentry organization settings under Settings > Auth Tokens. Optionally, your Sentry organization slug (SENTRY_ORG) to scope CLI commands to a specific organization.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Sentry in the catalog
In Settings > Sandbox CLIs, find Sentry under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: SENTRY_AUTH_TOKEN (your Sentry auth token). Optionally, enter SENTRY_ORG (your Sentry organization slug) to avoid passing --org on every command. 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 Sentry CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type sentry --env SENTRY_AUTH_TOKEN=<your-sentry-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 sentry-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 Sentry CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.