Clerk
Give the Sazabi agent the Clerk CLI (clerk) in its sandbox to manage Clerk applications, users, and authentication configuration.
About
This CLI connection makes the Clerk CLI (clerk) available in the Sazabi agent's sandbox. The agent can manage Clerk applications, users, and authentication configuration. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Clerk secret key (
CLERK_SECRET_KEY).
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Clerk in the catalog
In Settings > Sandbox CLIs, find Clerk under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: CLERK_SECRET_KEY — your Clerk secret key (starts with sk_). Optionally set CLERK_PLATFORM_API_KEY if your use case requires platform-level API access. 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 Clerk CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type clerk --env CLERK_SECRET_KEY=<your-clerk-secret-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 clerk CLI (for example clerk users list) 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 Clerk 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 clerk.