Skip to main content
Devin often needs to be logged into web apps — your staging environment, an admin dashboard, a SaaS tool — before it can do useful work. Instead of repeating a login every session, log in once and have Devin save the browser profile so all future sessions start authenticated.

​
The workflow

1

Log in manually in the Interactive Browser

Open the Desktop tab in the session and drive the browser yourself: complete the login, including SSO redirects, MFA prompts, and CAPTCHAs. See Interactive Browser.
2

Ask Devin to save the browser profile

Say “save the browser profile” or “persist my login sessions”. Devin calls its save_browser_profile tool, which zips the browser data directory (cookies, localStorage, and other Chrome profile data) and attaches it to your organization’s blueprint as a file. Other phrasings work too — “save browser cookies”, “remember my browser logins”, “keep my browser state”, “save the browser to my snapshot”.
3

Approve the blueprint update

Devin proposes a one-time update to the organization-level blueprint, adding an initialize step named Initialize browser profile that unzips the saved profile into the browser data directory. Review it in your timeline and approve it.
4

Future sessions start authenticated

Every new session in the organization restores that browser state during setup, so Devin’s browser is already logged in when the session starts. No further approvals needed.
The restore step is a normal blueprint initialize step, referencing the profile zip through a $FILE_BROWSER_PROFILE file attachment:
To refresh expired sessions, log in again and ask Devin to save the profile again — the tool replaces the existing step rather than adding a second one.

​
Limitations and security

Saved profiles are organization-level, not per-repository. Anyone in your organization can start a session that loads the profile, including the logins, cookies, and session tokens it contains. Only save profiles for accounts your whole organization is allowed to use — prefer a dedicated service account over a personal one.
  • No browser extensions. Only profile data is restored. Extension-based tools (for example, MetaMask) are not loaded, so flows that depend on an extension won’t work.
  • Saved passwords are excluded. Chrome’s password store is skipped, along with caches — so the profile carries session state, not credentials. Store credentials as Secrets instead.
  • Size limit. The profile zip must be under 200 MB.
  • Sessions still expire. Cookies restored from the profile expire on the app’s normal schedule; re-save the profile when they do.

​
Alternatives