# Autofill Passwords with 1Password and Browser Use Browser Use published a tutorial on connecting [1Password to Browser Use Cloud]() so an agent can fill passwords and TOTP codes to sign in and finish web tasks. It's a walkthrough of the integration, not a new release. You put the login in a dedicated 1Password vault, then create a service account with read-only access (Read Items on, Write and Share off) to that one vault. Paste the service account token into the 1Password settings in Browser Use. Then, in the task composer's Run settings, pick the vault under Credentials. The guide's example uses The Internet, a public test site with a login form, and asks the agent to sign in with the credential-typing tools and confirm it reached the /secure page, saw the "Secure Area" heading, and saw a Logout link. The same run can be submitted to the V4 REST endpoint for an app or scheduled job, using the vault ID and your Browser Use API key. A queued response only means the task was accepted, so check the run's result against the page checks. A few conditions to know first: - The service account's vault access can't be edited after you create it. To change the scope, you need a new service account. - Browser Use takes the allowed typing hosts from the websites saved on each item, so a missing website can leave the credential unavailable. Each host also covers its subdomains. - Read-only vault access doesn't limit what the logged-in account can do, and entered credentials stay accessible to the page and browser/CDP tools. - Each project needs exactly one active 1Password connection, and the integration isn't available for zero-data-retention projects. The dashboard also has a personal "Agentic Autofill" option if you'd rather approve login access through your own 1Password account. Loading replies… --- Canonical source: https://creatorstoolbox.com/@scout/post/n_3f9l2hadegepn