Browser-use profiles

Browser-use profiles let you run the Orca browser with a specific identity — a logged-in user or a particular cookie jar. Useful when an agent needs to log in, reproduce a session-specific bug, or emulate multiple users.

Create a profile

  1. Open Settings → Browser → Profiles.
  2. Click Add profile, give it a name.
  3. Optionally seed it with cookies and a viewport size.

Browser identity

The browser user agent is an app-wide choice because documents and web workers must present one coherent identity. Open Settings → Browser → Browser identity to choose between the cleaned identity and Electron's native identity. The change takes effect after you restart Orca.

Native is the default. It keeps Electron's identity without the Orca token, which Cloudflare's security checks, Google sign-in and WhatsApp Web accept. A few sites turn Electron away, so Orca makes two exceptions: Microsoft Teams receives the user agent without the Electron token, and Chase receives the cleaned identity.

Cleaned removes the Orca and Electron tokens from the user agent, leaving a Chrome-shaped identity. It doesn't make the embedded browser identical to Chrome, and Cloudflare's full-page security check can loop in this mode. Google sign-in hosts still see Electron's own identity, because Google rejects sign-in from a browser claiming to be Chrome or another browser. If you chose a mode before, Orca keeps your choice.

Import cookies from Chrome or Edge (or from a cookie file) into a profile from Settings or the browser toolbar. Orca replaces existing cookies only for domains included in the import, so sign-ins for unrelated sites in the same profile stay intact. Google cookies are excluded — import menus show Google logins aren't imported and tell you to Sign in to Google directly in Orca. After an import that skipped Google cookies, a separate warning names the host that ran the import: open a browser in Orca on that host with the same profile, then sign in.

Clear default cookies on the Default profile removes every cookie in it after you confirm, signing you out of sites in that profile.

When a site requests a discoverable passkey from a USB security key and the key offers multiple accounts, Orca opens an account picker instead of silently canceling the sign-in. Choose the account you want or cancel the request. Platform passkeys stored by the operating system are not available in Orca yet; this flow is for external FIDO security keys.

Use a profile

Pick the profile from the browser toolbar. All tabs in that pane use it until you switch. Agent-driven browser commands inherit the active profile.

Isolation

Each profile has its own storage partition — cookies, local storage, cache. Profiles don't leak into each other.