A fresh branch for every idea.
Parallel agents need independent places to act. Two agents clicking in the same tab can undo each other’s progress, even when their connections are separate.
Start from a useful baseline
A browser fork begins with a consistent snapshot of a prepared profile. Each fork gets a new browser ID and independent future filesystem writes. The source can remain the starting point for later workflows.
Separate state, separate access
A copied login is still sensitive. Access tokens must be issued for the new browser rather than inherited from its parent. A fork is a resource copy, not permission to share an account with another user.
Make parallelism visible
The Cloudbrowser console design gives each browser a preview and an explicit lifecycle state. Paused forks can wait until there is a concurrency slot and a task ready to run.