Use 1Password with an agent: approve a login, then control the task

For Claude, the 1Password setup guide requires a Mac, 1Password desktop and browser extension 8.12.28 or later, Claude desktop, Claude in Chrome and a paid Claude plan. Business and managed Claude accounts can also require administrator approval.

The broader personal-agent integration page describes availability by agent and inclusion in 1Password Individual and Family plans. Do not treat that page as proof that every listed agent is ready on your device. Confirm the provider, operating system and account you will actually use.

Update the required apps and extension, then follow Claude desktop → Customize → Connectors → 1Password → Connect. Complete authorization in 1Password. Use the official setup steps if the labels or availability differ in your account.

Before connecting, choose a disposable account with no billing or administrative access. Save the correct website address with its login. Avoid beginning with a shared production account: that makes it harder to distinguish a harmless trial from a real business action.

Do not paste a password, recovery code or vault export into the conversation to work around a missing connection. If the connector is absent, resolve the account or administrator requirement first.

Use an instruction like this in your supported Claude workflow:

Open the account profile page for my test account.
Use the connected 1Password login flow when sign-in is required.
Stop if the site or account does not match my request.
After login, report the visible account name.
Do not change settings, submit forms, send messages or buy anything.

When prompted, compare the destination with the saved login's website. Approve only the intended account. After sign-in, check the profile yourself: the correct account name is the acceptance result, not just a “logged in” message. This prompt is our suggested trial, not a recorded product test.

The documented Claude integration supports Login items and relevant password or one-time-code fields; passkeys and other item types are not currently supported. Its security design avoids returning those credentials to the model. Read the supported-login details and security explanation for the current boundary.

Once authenticated, the agent may still be able to read private data or operate account controls. Give it a narrow task and retain approvals for consequential actions. If the suggested login is wrong, inspect the item's website address and the current domain before retrying. Do not widen access simply to make a mismatch disappear.

If the browser begins an unintended action, stop the agent. The official Claude integration guide describes closing Claude's Chrome tab group to end its control. For a lasting disconnection, use the integration's documented disconnect controls; do not assume stopping one task revokes every session. 1Password support

Record which step failed: connector availability, authorization, login selection or the destination account. Recheck versions and organization policies before trying again. Keep screenshots free of credentials and personal account data. A successful pairing alone does not prove the entire login workflow works.

This workflow is not an account-free login tool. You need the relevant 1Password entitlement and an eligible paid Claude plan; organization policy may add another gate. Inclusion in a 1Password plan does not include Claude usage. Check current 1Password availability and Claude requirements before subscribing.

Your first trial is complete when the intended account opens, no account data changes, and you can stop the agent. Only then consider a larger workflow. For reusable instructions around that workflow, see how to write a SKILL.md; a skill does not itself grant account access.