Supabase
Give the Sazabi agent the Supabase CLI (supabase) in its sandbox to manage Supabase projects, run migrations, and inspect your database.
About
This CLI connection makes the Supabase CLI (supabase) 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 Supabase access token (
SUPABASE_ACCESS_TOKEN). Generate one in your Supabase account settings under Account > Access Tokens.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Supabase in the catalog
In Settings > Sandbox CLIs, find Supabase under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: SUPABASE_ACCESS_TOKEN (your Supabase personal access token). 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 Supabase CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type supabase --env SUPABASE_ACCESS_TOKEN=<your-supabase-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 supabase 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 Supabase CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.