Use this file to discover all available pages before exploring further.
Kernel browsers are sandboxed Chromium instances that boot in under 30ms. Your agent creates them on demand, drives them, and tears them down — no infra to provision, no servers to run.
Most of what you’ll tune at creation time falls into four buckets:
Headless vs headful
headful (default) supports live view, replays, and better stealth — ideal for agent workflows on bot-detected sites. headless is lighter (1 gb vs 8 gb), good for simple scraping.
Stealth and proxies
Turn on stealth mode and route through residential, ISP, or datacenter proxies when you’re hitting sites with bot detection.
GPU acceleration
Required for WebGL, video, and canvas-heavy workloads. Trades off standby support.
Profiles and auth
Persist cookies, storage, and logged-in sessions across runs with a profile, or hand auth off to Kernel entirely with managed auth.
A browser stays alive as long as something is driving it — a CDP or WebDriver client, a Live View viewer, or an in-flight computer controls request. After five seconds with none of those active, it enters standby — state is preserved, billing stops. Once in standby, after the configurable timeout (60s by default) elapses it’s deleted.We recommend you delete a browser explicitly when you’re done with it:
Once you have a browser, you need to drive it. Head to Control to see the four primitives Kernel exposes — computer use, playwright execution, CDP, and WebDriver BiDi — and when to reach for each.