PRODUCT NOTES · DESIGN JOURNAL

Your browser is a workspace, too.

A useful browser session holds more than an open page. It holds the setup that made the work possible: a login, preferences, and the context of a task.

A place to return to

For recurring browser tasks, preparing a fresh profile every time creates repeated work. A persistent browser keeps the profile on a durable filesystem, so a later run can reuse the state that has actually been saved.

A human can help an agent get started

A live viewer lets a person sign in and check the browser. An agent then attaches to that same Chrome over CDP. There is no need to export a password into an automation script.

Persistence has boundaries

A website can expire its own session or request fresh authentication. Persisting profile files also does not preserve every in-memory page operation. Cloudbrowser’s design makes those distinctions explicit.

Explore the product design in our docs