The feature is intended for Browserbase browser sessions in which an agent reaches a sign-in page and needs access to a user's account.
The agent requests a relevant login, and the user approves or denies that request in 1Password. If approved, 1Password fills and submits a password or one-time code directly in the browser. Browserbase says the credential value is not returned to either the agent or the application, and that 1Password removes the filled credential after the site accepts the login.
Browserbase says teams can configure sessions without persisted session recordings or session logs. Its implementation guide covers OAuth, token handling, extension setup, and current prerequisites. The announcement does not establish pricing, supported websites, availability across all Browserbase plans, or measured security and reliability outcomes in production.