Connect provider capacity
Add encrypted provider credentials, validate them, and let routing policy decide where each workload belongs.
Supported providers
Native LinuxDocker sandbox
native/linuxCloudflare BrowserBrowser + CDP
cloudflare/browserE2BSandbox + desktop
e2b/sandboxBrowserbaseManaged browser agent
browserbase/agentConnect credentials
Provider keys are validated before being encrypted. Read APIs return credential field names, never secret values.
./bin/tctl providers connect e2b \
--api-key "$E2B_API_KEY"Select a provider
Use a concrete provider when the workload depends on its behavior, or a portable alias such as t/browser, t/computer, or t/sandbox when portability matters.
Fallback behavior
Creation-time fallback is explicit. Once a computer reaches ready, provider failures are surfaced instead of silently migrating state to another backend.