Runtimes
A runtime is a managed cloud browser running on BCTRL infrastructure. Create it with a configuration, start it to get a connect URL, drive it, then stop it. Browser is the only runtime type today.
Create a runtime
Scope it to a space with spaceId so it inherits that space’s storage, vault, and AI mounts:
Configure the browser
Pass config to set stealth, proxy, fingerprint, extensions, and network behaviour:
See Runtime configuration for the full set of options, and Proxies and Extensions for the resources they reference.
Start a runtime
Starting boots the browser and mints a fresh, run-scoped connect URL:
Every start opens a new run (runId) where the session is recorded. The connectUrl is a credentialed CDP endpoint - see Connect with CDP.
start accepts an idempotency key so retries do not double-start:
List, read, and stop
list returns every runtime in the organization; pass spaceId to narrow to one space.
Update and delete
name and idleTimeoutMinutes are editable any time; config only while the runtime is stopped. The name is a display label - renaming never affects the runtime’s browser state.
Deleting requires the runtime to be stopped; pass { force: true } to stop and delete in one call.
Targets (tabs)
A running browser exposes its pages as targets. List them, open new ones, switch focus, and close them:
Hosted invocations act on the active target by default, so activate is how you point an agent at a specific tab.
Files on a runtime
Move files in and out of a running browser. These operate on the live runtime filesystem, distinct from the durable run artifacts in Run files:
stage copies a durable file into the runtime; collect saves a runtime file back to durable storage.
Next
- Connect with CDP - drive the runtime yourself
- Invocations - hand it to a hosted agent
- Runtime configuration - stealth, proxy, fingerprint

