Devin
Give the Sazabi agent the Devin CLI (devin) in its sandbox to start and manage AI coding sessions.
About
This CLI connection makes the Devin CLI (devin) available in the Sazabi agent's sandbox. The agent can use it for AI coding sessions. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Devin API key (
DEVIN_API_KEY), available from your Cognition account settings.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Devin in the catalog
In Settings > Sandbox CLIs, find Devin under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: DEVIN_API_KEY — the API key for your Devin (Cognition) account. 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 Devin CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type devin --env DEVIN_API_KEY=<your-devin-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 devin 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 Devin 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 devin.