Skip to main content
To do anything behind a login — check email, post to a dashboard, pull data from an account — the browser needs to be authenticated. A browser profile saves that login state (cookies, sessions) so you log in once and reuse it forever. There are two ways to get a logged-in profile: let the agent log in, or sync your existing local logins.

Option 1 — the agent logs in with your credentials

Create a profile, then have the agent log in inside it. The session is saved back to the profile.
Prefer not to send raw passwords in a task? Sync your existing browser logins instead — no credentials in the request.

Option 2 — sync your existing logins

If you’re already logged into these sites in your own browser, sync those cookies into a profile — no passwords, no re-login. See Sync cookies.

Two-factor authentication (2FA)

For accounts with 2FA, the agent can pause and hand control to you to complete the challenge, then continue.

How it fits together

  • A profile is standalone, project-owned login state — create and manage it.
  • Pass browser_profile_id into any run (or standalone browser) to start logged in.
  • One profile per identity you automate (my-gmail, my-linkedin, …); reuse across as many runs as you like.