Browserbase Is Partnering With 1password For Agents

Browserbase and 1Password first announced agentic autofill in October 2025, saying Browserbase customers could give browsing agents access to credentials in their 1Password vault. That earlier post explained why agents need credentials but did not describe what happens at a sign-in page. This October 2026 post does. The agent requests the relevant login, the user sees an approval request from 1Password and can approve or deny it, and if approved 1Password fills and submits the password or one-time code directly in the browser. The credential value is not returned to the agent or the application. Once the website accepts the login, 1Password removes the filled credential so the agent cannot read or reuse it as it continues the task.

Those details settle a question the first announcement left open: whether an agent that can use a password also gets to hold it. According to this post it does not, before or after sign-in, which keeps the password out of prompts, application code and model context. The post also says teams with stricter data-handling rules can run Browserbase sessions without persisted session recordings or session logs, and it refers developers to an implementation guide for the OAuth flow, token handling, extension setup and current prerequisites. The user's approval governs the moment of sign-in, not what the agent does afterwards. The 2025 post described rules about which actions an agent may take, role-based access control, as work Browserbase was building toward, and this post reports nothing new on that.