Sessions
A session is a stateful browser environment. By default, run() creates one automatically. Create one manually to run multiple tasks in the same browser.
Live view & recording
Every session has a liveUrl for real-time monitoring. You can also create a shareable public link.
When to use sessions
- Auto-session (default): Simple one-off tasks.
run() creates and cleans up a session for you with a US proxy.
- Manual session: Multi-step workflows, custom proxy location, or when you need the live URL for debugging.
See Browser Infrastructure for the full list of session parameters (profile_id, proxy_country_code, browser_screen_width, etc.).
Profile Sync
The easiest way to authenticate: sync your local browser cookies to the cloud.
The interactive script walks you through selecting a local browser profile and uploading it. After sync, create a session with that profile and the agent is already logged into all your sites.
Profiles
A profile is persistent browser state — cookies, localStorage, saved passwords. Login once, and the state survives across sessions.
Manage profiles
Usage patterns
- Per-user profiles: Create one profile per end-user. Store the profile ID in your database.
- Per-site profiles: Separate profiles for different services (e.g., “linkedin”, “github”, “jira”).
- Warm-up profiles: Pre-login to common services once, then every automation starts already authenticated.
Profile state (cookies, localStorage) is only saved when the session ends. Always call sessions.stop() when you are done — if a session is left open or times out, changes may not be persisted.
Refresh profiles older than 7 days to keep login state fresh. Cookies expire.