profile: { name, persist: true }, sign in, stop it: the state is saved. The next session with that name opens signed in. A browser pool can load a profile into every warm browser; keep persist off there, or the browsers overwrite one another.
Profiles work on every browser type.
Listing and deleting
{ "success": true }. The list isn’t paginated and returns every profile in the workspace, so delete what you no longer need. The dashboard’s Profiles page shows the same list and can launch a session on a profile so you sign in by hand through the live view.
Practical notes
- One profile, one session at a time. Two concurrent sessions on the same persisted profile overwrite each other’s state when they stop. Nothing refuses the second.
- The profile is written as the session ends. Wait for
GET /v1/browser/sessionto reportcompletedbefore starting the next session on the same name. - Keep the same
countryacross runs. A profile that signed in from Germany and comes back from Brazil looks like a stolen session. - A profile holds everything Chrome’s does: cookies, local storage, IndexedDB, service workers. Delete it when the account is no longer needed.
- As in desktop Chrome, cookies without an expiry (session cookies) are dropped when the browser closes. Sites that keep you signed in set persistent cookies, which carry over; a login that only sets a session cookie has to be repeated each run.
- The next session on a profile can run on a different machine. The state travels with the name.