Context.dev
Give the Sazabi agent the Context.dev CLI (context-dev) in its sandbox for brand lookups, web scraping, and screenshots.
About
This CLI connection makes the Context.dev CLI (context-dev) available in the Sazabi agent's sandbox. The agent can run brand lookups, web scraping, and screenshots using your Context.dev account. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Context.dev API key (
CONTEXT_DEV_API_KEY).
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Context.dev in the catalog
In Settings > Sandbox CLIs, find Context.dev under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: CONTEXT_DEV_API_KEY — your Context.dev API key. 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 Context.dev CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type context-dev --env CONTEXT_DEV_API_KEY=<your-context-dev-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 context-dev CLI (a read-only command against your account) and confirm it returns real output. 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 Context.dev 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 context-dev.