Log In Once: Reuse Cookies and Profiles Across Browser Use Runs

Browser Use published a tutorial on reusing a login across separate runs with profiles. It walks through a worked example rather than a new release.

A profile stores cookies and local storage, so a fresh cloud browser can pick up an earlier login. Create an empty profile in Browser Use Cloud (Configuration, then Profiles, then Start from Scratch). Pass its ID as profileId in the browser settings when you create a run, log in, and stop the browser to save its state. A later run with the same profile ID starts already signed in. The website still decides how long that login stays valid, so you may need to renew it.

The tutorial checks this on a public test site. The first run logs in. The second starts a new conversation with no credentials and reaches the protected page. The author also connected to each browser to confirm the URL, heading, and Logout link, instead of relying only on the agent's answer. As a control, an empty profile got sent to the login page. This shows reuse on that demo site only. It doesn't guarantee another site will accept a transferred login.

A few details matter for your own setup:

• Stop the browser before the profile can save, and don't click Logout first, or the logged-out state gets saved.
• The API key and the profile have to belong to the same project.
• For real accounts, the tutorial suggests a credential flow like 1Password instead of putting a password in the task.

It also covers the same idea with local Playwright. You save authentication state to a JSON file with storage_state and load it into a new browser context. The cloud runs need a Browser Use API key and credits.