AUTHENTICATION

Profiles

Profiles keep browser state alive across runs so agents can work with authenticated sites without repeating login every time.

What profiles store

Cookies and session tokens.
Local storage and IndexedDB data.
Tabs and browser history used by persistent sessions.
Site-specific preferences and consent state.

Use a profile

cdp url

wss://brapi.remote-browser.dev/connect?apiKey=YOUR_API_KEY&profileName=Personal%20Profile&region=auto&timeout=5

Passing profileName loads an existing profile or creates it on first use.

Naming

Use stable profile names per agent, workflow, or customer account. Avoid sharing one profile across unrelated agents that may overwrite each other's tabs or session state.

Next step2FA