Browserbase and 1Password bring secure sign-in to browser agents

Let agents sign in to websites with credentials from 1Password—without exposing the password to the agent or your application.

Most useful work on the web happens behind a login. That creates a difficult tradeoff for anyone building browser agents: give the agent access to the accounts it needs, or keep credentials out of the workflow entirely.

Today, Browserbase and 1Password are making that tradeoff unnecessary.

With 1Password Agentic Autofill in Browserbase sessions, an agent can request access to a login, wait for the user to approve or deny the request in 1Password, and continue its task once 1Password signs it in. The credential value is not returned to the agent or the application.

Access when the agent needs it, control when it matters

The flow is simple:

• The agent asks. It reaches a sign-in page and requests the relevant login.
• The user decides. They see an approval request from 1Password and choose whether to grant access.
• 1Password signs in. If approved, 1Password fills and submits the password or one-time code directly in the browser.

Once the website accepts the login, 1Password removes the filled credential so the agent cannot read or reuse it as it continues the task.

This gives agents the access they need to work across authenticated dashboards, SaaS tools, and test environments without putting credentials in prompts, application code, or model context.

Security built into the sign-in flow

The user stays in control at the moment access is requested. Credentials remain protected by 1Password, while Browserbase provides the browser infrastructure the agent needs to complete the workflow.

Teams with stricter data-handling requirements can also configure Browserbase sessions without persisted session recordings or session logs. The implementation guide covers the full scope of these settings, along with the OAuth flow, token handling, extension setup, and current prerequisites.

Authentication should not require every team to build its own secret-handling system. Browserbase and 1Password give developers a safer, more direct path from an agent reaching a login screen to getting useful work done.

Read the Browserbase implementation guide or learn more about 1Password for Agents.