What happened
1Password says its 1Password for Agents integration lets Claude Duet fill saved logins when a task requires website sign-in. The support guide, published November 5, 2026, covers Claude Duet on iOS, Android and the web. It requires a 1Password Individual or Family account on 1Password.com; Team and Business accounts, plus accounts on 1Password.ca and 1Password.eu, are not currently supported.
The guide requires 1Password app version 8.12.42 or later on the same computer or mobile device as Claude Duet. It lists Claude Duet for iOS version 1.261107.0 or later, Android version 1.261103.17 or later, or the web app at claude.ai/duet. Users need a Claude Pro, Max or Ultra account with access to Claude Duet. On mobile, the connection is under Settings > Connections; on the web, it is under Settings > Credentials. The user selects 1Password, signs in to the 1Password account and approves the connection.
When a task needs a sign-in, Claude Duet prompts the user to use 1Password. 1Password displays an approval prompt identifying Claude Duet and suggesting a Login item. The user can review that suggestion or search for another login, then approve. 1Password fills the approved login and submits the sign-in form, returning the user to Claude Duet. The website controls how long the session remains active, and may require additional verification such as multi-factor authentication. 1Password says some websites block automated access; users can ask Claude Duet to sign out after a task.
The supported credentials are usernames, passwords and one-time passwords from Login items in a Personal or Private vault. Passkeys, items that depend on an identity provider such as Google or Facebook, other item types and shared vaults are not supported. An approval lasts 30 days, after which Claude Duet must request access again and the user must approve it. Users can disconnect via their 1Password.com account’s Integrations area under “Autofill for AI”; this removes approved login requests and stops the integration from continuing to sign in.
What the archive adds
New Runtime’s earlier coverage described Claude connectors using Enterprise Managed Auth to avoid per-user OAuth consent prompts (Claude connector authentication note, November 3, 2026). That was a different authentication capability. The 1Password guide is a new, specific credential-filling integration, not evidence that the reported iOS “Saved logins” interface has shipped.
Trend signal
This supports the pattern that agent-ready software exposes a small set of observable, permissioned capabilities: agent-ready software exposes capabilities. Here, a user approves a specific suggested login, can disconnect the integration, and must renew the approval after 30 days. The bounded workflow is a concrete example, although the guide does not establish how broadly agents can compose such permissions across services.
Why now
The support guide is dated November 5, 2026, and specifies minimum app versions for the mobile clients. Those version requirements make the instructions actionable for users checking whether their setup can connect now. The guide does not explain the timing of the release or connect it to the reported iOS interface sighting.
Why it matters
Credential use is a consequential boundary for agents: a task can move from reading public pages to acting inside a user’s accounts. This flow puts a human approval in front of each approved login use and identifies which agent is asking, while keeping credentials in 1Password rather than asking users to paste them into a prompt. The 30-day renewal and disconnect control also give administrators and users a defined way to revoke continued access.
The limits matter as much as the capability. A team relying on shared vaults, passkeys or business accounts cannot assume the workflow will work. Even with supported credentials, websites may block automation or require another verification step. Builders should treat the integration as a narrowly scoped sign-in mechanism, not as general unattended authentication, and design tasks to handle denial, reapproval and sign-out.
Limits and uncertainty
1Password’s guide documents setup and stated support boundaries, but it does not quantify successful sign-ins, website coverage or failure rates. It does not independently establish the security properties of the full Claude Duet runtime or say how session cookies are handled after sign-in. The underlying websites determine session duration and may impose extra verification or block automated access. The guide also does not verify the separate report of an iOS “Saved logins” section; the documented integration alone is not proof that interface has shipped.
Skill to build now
For a supported account, test one low-risk website before using the integration for consequential tasks. Put its Login item in a Personal or Private vault, confirm the saved website matches the sign-in domain, and inspect the approval prompt before granting access. Record when approval expires and test the disconnect flow so your team knows how to revoke the integration.
Reader takeaway
Claude Duet can use 1Password for a user-approved website login, but the workflow is constrained: supported account plans, current apps and personal/private-vault Login items are required. Treat each sign-in as an explicit permission decision, and do not assume shared vaults, passkeys or business accounts are covered.