PRODUCT NOTES · DESIGN JOURNAL

Knowing when to take a pause.

An open connection and a running browser are different things. Closing a viewer does not tell an automation platform that its browser is finished.

Pause deliberately

A pause operation stops the browser’s running compute. That is the boundary used by browser-hour accounting. Disconnecting CDP alone leaves the browser running so unattended work is not stopped accidentally.

Files and memory are different

Ordinary filesystem recovery restarts Chrome with its saved profile. An unsent form, a JavaScript timer or an in-flight request is not guaranteed to survive. Retained-memory recovery has separate requirements.

Reconnect with a fresh grant

Cloudbrowser’s proposed access model binds grants to a runtime generation. After resume, an authorized manager obtains fresh access and the agent attaches again. Stable browser identity does not imply immortal credentials.

Explore the product design in our docs