A browser that stays yours

Understand browsers, profiles, forks and connections.

Browser

A browser is a persistent Cloudbrowser resource with a stable ID. It maps to an isolated Sandbox0 sandbox running Google Chrome. The ID survives pause and resume.

Profile

The profile holds Chrome cookies, local storage and browser configuration. It lives in the durable filesystem. A website can still expire a login or request a fresh authentication.

Fork

A fork gets a new browser ID and independent future writes. It inherits the source profile at the snapshot point, including applicable login state. Connection grants are never inherited.

Connection

CDP is for automation. Live View is for humans. Both reach the same Chrome, but their credentials are separate and scoped to one browser. Concurrent control of the same tab requires coordination.

Persistence is not uninterrupted execution

Ordinary pause/resume preserves files and restarts Chrome. It does not guarantee JavaScript heap, live sockets or in-progress page operations. Retained-memory recovery is a separate capability to qualify before offering it.