Browser-use profiles
Browser-use profiles let you run the DevAgent browser with a specific identity — a logged-in user, a particular cookie jar, a custom user-agent. Useful when an agent needs to log in, reproduce a session-specific bug, or emulate multiple users.
Create a profile
- Open Settings → Browser → Profiles.
- Click Add profile, give it a name.
- Optionally seed it with cookies, a user-agent, and a viewport size.
- For sites that reject DevAgent's default Chrome-shaped UA (some Google sign-in flows), create a profile that keeps the native Electron user agent instead of spoofing. Default profiles still use the cleaned Chrome UA for broader Cloudflare compatibility.
You can also create a no-spoof profile from the CLI with devagent tab profile create --no-ua-spoof when you script browser setup.
Cookie import and Google sign-in
Import cookies from Chrome or Edge (or from a cookie file) into a profile from Settings or the browser toolbar. Google cookies are excluded — import menus show Google logins aren't imported and tell you to Sign in to Google directly in DevAgent. After an import that skipped Google cookies, a separate warning names the host that ran the import: open a browser in DevAgent on that host with the same profile, then sign in.
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.