If you use Claude to do things in your browser, you no longer have to type your password for it or paste it into the chat. With 1Password for Claude, Claude asks 1Password for a login, you approve it with Touch ID, and 1Password fills it in directly on the website. Claude never sees the password or the one-time code. Setup takes about five minutes on a Mac with a paid Claude plan. This guide walks through it, explains what you are actually approving, and covers the problems people hit most often.

Key facts (from 1Password’s and Anthropic’s official help pages):

• What it does: Claude requests a saved login, you approve, swap or deny it in a 1Password prompt, and 1Password fills it on the page. Claude only learns which login it used (1Password Support).
• Status: Anthropic calls it a beta for paid plans (Pro, Max, Team, Enterprise) using Claude Desktop on macOS, and it requires Claude in Chrome (Claude Help Center).
• You need: a Mac, the 1Password for Mac app and 1Password browser extension (both 8.12.28 or later), the Claude desktop app and the Claude in Chrome extension.
• Supported items: usernames, passwords and one-time codes (TOTP) from Login items, plus “Sign in with Google/Facebook”-style logins. Passkeys, credit cards and identities are not supported.
• Team/Enterprise: off by default. An Owner has to switch it on.
• Bigger picture: on October 22, 2026, 1Password announced 1Password for Agents, a wider program for agents including Meta’s Muse, OpenAI’s ChatGPT Work and dots, and others. Most of those integrations are still “rolling out” or “coming soon” (1Password blog). The Claude integration is the one you can set up today with published step-by-step instructions.

Why this matters

Browser agents are useful right up until they hit a login page. Until now you had two bad choices there. You could take over the session and type your password yourself every time. Or you could paste your password into the chat, which hands it to the agent. 1Password’s announcement describes this exact problem. It also notes that passwords saved in your browser or written in notes don’t help, because agents can’t use them either.

1Password for Claude adds a third option. The agent asks, you approve on your own device, and the password goes straight from your vault into the website. It never passes through Claude.

If you’re new to letting AI act in a browser, read our browser agent guide for the general idea. Our Claude Code permissions guide explains how Claude decides what it may do without asking.

Before you start: the checklist

Go through this list first. Almost every failed setup comes down to one missing item.

You need	Notes
A Mac	Both official help pages list macOS only. There is no Windows or mobile version of this integration yet.
A paid Claude plan	Pro, Max, Team or Enterprise. The free plan can’t use it, because Claude in Chrome itself requires a paid plan.
The Claude desktop app	Download it from Anthropic (install guide).
Google Chrome with Claude in Chrome	Anthropic says Claude in Chrome is not supported on other Chromium-based browsers (so not Edge, Brave or Arc), and not on mobile.
1Password for Mac, version 8.12.28 or later	Update it from the app if you’re on an older version.
The 1Password browser extension, version 8.12.28 or later	It must be installed in the same Chrome you use with Claude.
A 1Password account	Anthropic’s page says individual, family and business plans all work. 1Password says the wider “1Password for Agents” program costs nothing extra on Individual and Family accounts on 1Password.com, and that 1Password.eu and 1Password.ca accounts aren’t supported yet. If your account lives on .eu or .ca, expect this not to work for now.

Step 1: Set up Claude in Chrome

If Claude can already control your Chrome browser, skip to Step 2.

Anthropic’s Claude in Chrome guide describes two parts.

Install the extension:

1. Open Google Chrome.
2. Go to the Claude extension in the Chrome Web Store and click Add to Chrome.
3. Sign in with your Claude account.

Connect it to the desktop app:

1. In Claude Desktop, click your initials in the lower-left corner and choose Settings.
2. Go to Customize, then Connectors.
3. Find Claude in Chrome, click Configure, and turn the connector on.

Anthropic notes one gotcha here. In regular chats, the Claude in Chrome connector is off by default, so you need to enable it for each conversation from the Connectors drop-down. Claude Cowork can also use Chrome. Anthropic says Cowork also has a built-in browser that’s rolling out gradually. If you already use Claude in Chrome, it stays your preferred browser for Cowork. You can switch in Settings > Cowork > Preferred browser. The 1Password integration is documented for Claude in Chrome, so keep Chrome selected while you use it.

Step 2: Connect 1Password to Claude

1. Open both the 1Password desktop app and the Claude desktop app. Make sure 1Password is unlocked.
2. In Claude Desktop, go to Customize > Connectors (under Settings).
3. Find 1Password and click Connect.
4. The 1Password app shows a pairing prompt. Approve it with Touch ID or your 1Password account password.

If you’re signed in to more than one 1Password account (say, personal and work), click the down arrow next to the account name in that prompt to choose which one Claude may ask. Pairing is per account.

Anthropic says you may also see two shortcuts. One is a banner in Claude Desktop when it detects 1Password. The other is an in-chat prompt the first time a task needs a login. Either one leads to the same connection.

You only pair once. 1Password’s security page says the pairing is remembered, so you won’t redo it for each task. You will still approve each login, as explained below.

Step 3: Try it with a real task

1Password’s own test uses Claude Cowork:

1. In Claude Desktop, click +New and choose Cowork.
2. Ask for something that needs a login. 1Password’s example is: “go to the Amazon website, sign in, and check the status of my latest order”.
3. When Claude reaches the sign-in page, 1Password shows an authorization prompt with a suggested Login item for that site.
4. Check that it’s the right account. If you have several logins for the site, use the down arrow to pick another one, or use the search bar in the prompt to find a different item.
5. Approve with Touch ID. The 1Password extension fills the login and submits it, and Claude carries on with the task.

The Claude extension may separately ask whether Claude may navigate to the website. That prompt comes from Claude, not 1Password, and it’s normal.

If the site uses “Sign in with Google” (or Facebook) and that’s how the item is saved in 1Password, Claude asks for both the site’s Login item and the linked Google item, then signs in through the provider.

Good first tasks

Start with a low-stakes site you trust: checking an order status, downloading an invoice from a utility account, or reading your library loans. Leave banking, email and admin consoles until you’ve seen how the flow behaves. Anthropic says Claude asks for permission before it opens financial sites, and it recommends trusted sites for anything sensitive.

What exactly are you approving?

This is the part most people skip, and it’s what makes the feature safe or unsafe in practice. Here’s what the official 1Password security page and the Claude Help Center say.

What Claude can see. Claude gets the item’s title, the username or email, and the websites saved on the item. That’s about what 1Password’s normal autofill suggestions show. It does not see passwords, one-time codes or the rest of your vault. Other than that, it only gets “success” or “failure” messages.

What happens during the fill. Claude stops reading the page while 1Password fills and submits the form. 1Password checks that the sign-in went through. If it fails, 1Password clears the filled values from the page before handing control back. So Claude never comes back to a page with your password still sitting in a field.

How long access lasts. Approvals are per task. There’s no standing approval, and a new agent session means a new prompt. The approved login is kept encrypted, in memory only, and deleted when the task ends, when the browser closes, or after nine hours at most. Each grant also shows up in the item’s usage history in 1Password.

Agentic Mode. When Claude takes control of a Chrome tab, the 1Password extension hides its own buttons, suggestions and save prompts in that tab. That way Claude can’t click its way into items you didn’t approve. Agentic Mode turns on whenever Claude drives the browser, even if you never connected 1Password for Claude.

The fill only goes to matching sites. 1Password uses its normal autofill rules, so a login is only filled on a page that matches the website saved on the item. That’s a useful defense if a malicious page tries to trick the agent into requesting your bank login.

What it does not protect you from

1Password is clear that its guarantees stop at the sign-in. Once Claude is signed in, it can see and do whatever that account allows, and the agent’s own safeguards govern what happens next. 1Password’s FAQ says to “review the task and the account before approving access.”

Anthropic’s Claude in Chrome safety page adds two warnings that matter here:

• Prompt injection. Hidden instructions in a web page or email can try to steer Claude into actions you didn’t ask for. Anthropic uses classifiers to screen for this, but it says the risk “is not zero.”
• Screenshots. Claude takes screenshots of the tabs it works in. Anything visible there, like your account balance or messages, becomes part of the conversation. Anthropic suggests a separate Chrome profile without your sensitive accounts.

A practical rule: approve only the login the current task needs, and deny anything unexpected. If you asked Claude to check an Amazon order and 1Password suddenly asks to release your email login, deny it and look at what Claude was reading.

1Password also lists the risks it accepts as out of scope. It can’t protect you from someone who already has full control of your Mac. And once a password is submitted to a website, it’s in that website’s hands, the same as when you sign in yourself.

For Team and Enterprise Claude plans

On Team and Enterprise, 1Password for Claude is off by default. An Owner or Primary Owner has to turn it on:

1. Sign in to Claude with the Owner or Primary Owner account.
2. Go to Organization settings > Claude in Chrome.
3. Turn on Enable for your team if it isn’t already on.
4. Turn on Password managers.

After that, eligible users will see the connect options. They still have to install the apps and extensions themselves. Anthropic also notes that organizations with HIPAA enabled have Claude in Chrome off by default, and that it isn’t covered under the Business Associate Agreement.

For 1Password Business accounts

If your 1Password account belongs to a company, an administrator must allow it first:

1. The admin signs in on 1Password.com.
2. Selects Policies in the sidebar.
3. Selects Manage under “Sharing and permissions”.
4. Turns on Allow AI agents to autofill for users.

If you’re on a Business account and the Connect step fails or nothing happens, this policy is the first thing to check.

Troubleshooting

1Password suggests the wrong login, or none at all. 1Password matches the item’s saved website against the sign-in page’s address. If they differ (for example, the item says example.com but the sign-in happens on login.example-auth.com), open the item in the 1Password app, click Edit, fix the website field, click Save and try again. In the prompt, you can also use the search bar to pick another item.

I can’t use my 1Password extension while Claude is working. That’s Agentic Mode. To get your extension back, or to fill logins on other sites yourself, close the Claude tab group in Chrome. You can also open the extension to confirm Agentic Mode is on or to cancel the current task.

No 1Password option appears in Connectors. Check the version numbers first (8.12.28 or later for both the app and the extension). Make sure both apps are open and 1Password is unlocked. Confirm you’re on a Mac with a paid Claude plan. On Team/Enterprise, ask an Owner whether Password managers is switched on. On a 1Password Business account, ask your admin about Allow AI agents to autofill for users.

It works in Cowork but not in a normal chat. In regular chats, the Claude in Chrome connector is off until you enable it for that conversation from the Connectors drop-down.

I’m using Edge, Brave or Arc. Claude in Chrome supports Google Chrome only, so the integration won’t work in other Chromium browsers.

The site uses a passkey. Passkeys aren’t supported yet. Add a password login to the item if the site allows it, or sign in yourself and let Claude continue.

Claude asks me to type a credit card or address. Only Login items and one-time codes are supported. Cards and identities won’t be filled through this flow, so think twice before typing card details for an agent.

How to disconnect

In Claude Desktop, go to Customize > Connectors and click Disconnect next to 1Password. Your vault isn’t affected. 1Password also stresses that the integration is optional, and that 1Password works exactly as before if you never connect an agent.

What about other AI agents?

1Password’s October 22 announcement names integrations for Muse (from Meta), Anthropic’s Claude Duet, OpenAI’s ChatGPT Work and dots, Grok Bot, and Town’s Townie. As of the announcement, Muse and Grok Bot were “rolling out over the coming days”, while Claude Duet, ChatGPT Work and dots, and Townie were “coming soon”. 1Password also listed Instinct, Browserbase, Browser Use, Dana, KERNEL, Perplexity, Ramp, Tomo and Wajo as coming soon. Its product page offers a waitlist for agents that aren’t ready yet.

The basic flow is meant to be the same everywhere: the agent asks, you approve on your device, and 1Password fills the login. But 1Password says “availability, platforms, and capabilities vary by partner integration”, and how often you’re asked to approve may differ too. Don’t assume the Claude details above (per-task approval, the nine-hour cap, Agentic Mode in Chrome) carry over to another agent until its own help page says so.

If you’d rather keep agents fully away from your real accounts, isolating them is the other approach. See our guide to sandboxing AI agents with NVIDIA OpenShell.

FAQ

Does it cost extra? 1Password says 1Password for Agents comes at no additional cost on Individual and Family accounts on 1Password.com. You still need a paid Claude plan for Claude in Chrome.

Can Claude read my whole vault? No. According to 1Password, connecting an agent doesn’t give it your vault. It requests a login for a task, and you decide. Even approved items reach Claude only as a title, username and website.

Do I have to approve every time? For Claude, yes, once per task or agent session. 1Password says there are no standing approvals.

Does it work on Windows or my phone? Not today. Both official pages list a Mac, Claude Desktop and Claude in Chrome as requirements.

Is this the same as saving passwords in Chrome? No. 1Password’s announcement points out that agents can’t use browser-saved passwords. That’s why Claude has to stop and hand control back to you on those sites.

Sources

• 1Password Support: Use 1Password to sign in to websites with Claude
• 1Password Support: About the security of 1Password for Claude
• Claude Help Center: Get started with 1Password for Claude
• Claude Help Center: Get started with Claude in Chrome and Use Claude in Chrome safely
• 1Password blog: Introducing 1Password for Agents (October 22, 2026) and the 1Password for Agents product page

For more hands-on guides, see the 7minai homepage.