A personal AI assistant can reach a hotel’s sign-in page while organising a trip, then stop at the password. 1Password’s new agent platform gives that step a separate approval path: the agent requests a login, the person reviews the request on their device and the password manager fills the credential into the destination. The company says the model never receives the password itself.[1]
That changes where the reusable secret travels. Instead of entering a model’s conversation or tool arguments, it stays within the credential-handling process. The user chooses whether to approve the request, and the integration completes the sign-in.[1]
Separate the sign-in from the task
The approved login gives an agent an authenticated session. What it can do next depends on the service and integration: accessing information or carrying out a task uses the permissions available in that session. Keeping the password outside the model reduces exposure of the secret, while the user still needs to understand which account and activity the approval enables.[1]
A clear approval screen makes the requested account and purpose visible. Task controls then govern actions after sign-in, such as whether a purchase needs a further confirmation. These are separate stages of delegation, and the product is easiest to evaluate when both remain visible to the person using it.[1]
For a routine task, the benefit is less interruption without passing a reusable password through the assistant. A user can approve the specific login and let the task continue. 1Password also describes a way to disconnect an integration, giving users a control over the relationship as their use of an agent changes.[1]
Check the rollout for the agent you use
The 22 October announcement lists Muse and Grok Bot integrations arriving in the following days. Claude Duet, ChatGPT Work and dots are described as coming soon, with Townie web and iOS support also forthcoming. Eligible Individual and Family accounts on 1Password.com are offered access at no extra charge; the announcement says 1Password.eu and 1Password.ca accounts are not yet supported.[1]
The immediate check for a user is therefore concrete: whether their account region and chosen agent are supported, where an approval request appears and how to disconnect the integration.[1]
As agents move across services, sign-in becomes a recurring part of their work. This design gives that step an explicit owner and approval action while keeping the password in a system built to handle credentials. It is a practical piece of the infrastructure needed to delegate a task across accounts.[1]
Sources & further reading
- Introducing 1Password for Agents 1Password / John Torrey · 22 Oct 2026 · Accessed 25 Oct 2026