Every browser agent hits the same wall: the login page. The usual workarounds are bad ones. You paste a password into the chat, where it sits in the conversation, or you sign in yourself and hand over a logged-in browser with everything in it.
On October 22, 2026, 1Password launched 1Password for Agents. When an agent reaches a login page it stops and asks for a credential. You approve the request in 1Password, and 1Password fills the login on the site itself, so the password and the one-time code never reach the agent. It costs nothing extra on 1Password Individual and Family accounts on 1Password.com.
Know which agents it works with
- Launched
- October 22, 2026
- Available now
- Muse, Grok Bot, Townie
- Claude Duet
- Coming soon
Coverage of the launch said it works with Claude. 1Password's launch post is more careful. These are the integrations it lists, and their status on the day of the post:
| Agent | Status | Platforms |
|---|---|---|
| Muse (Meta) | Available | iOS, Android, web |
| Grok Bot (SpaceXSI) | Available | iOS, Android, Windows, macOS, Linux |
| Townie (Town) | Available | iOS, Android, Windows, Mac, Linux |
| Claude Duet (Anthropic) | Coming soon | Not stated |
| ChatGPT Work and dots (OpenAI) | Coming soon | Not stated |
| Browserbase, Browser Use, Perplexity, Ramp and others | Coming soon | Not stated |
For Claude, the version that works today is older and separate: 1Password for Claude, announced on July 16, 2026. It covers Claude in Chrome, driven from the Claude desktop app, on a Mac. That is what steps 2 to 5 set up. Claude Code gets a different integration, for secrets rather than sign-ins, in step 6.
Check your versions
- 1Password
- 8.12.28 or later
- Claude plan
- Pro, Max, Team or Enterprise
- Platform
- Mac only
1Password's support page for Claude lists what you need:
- A Mac. No other platform is listed.
- 1Password for Mac and the 1Password browser extension, both version 8.12.28 or later.
- A paid Claude plan: Pro, Max, Team or Enterprise.
- The Claude desktop app and the Claude in Chrome extension.
Three commands tell you where you stand:
# 1Password for Mac (needs 8.12.28 or later)
defaults read /Applications/1Password.app/Contents/Info.plist CFBundleShortVersionString
# Claude Code (the 1Password plugin needs 2.1.273 or later)
claude --version
# 1Password CLI (the Claude Code shell plugin needs 2.34.0 or later)
op --versionThis is the one step I ran. 1Password for Mac reported 8.12.42, Claude Code 2.1.316, and op was not installed. The extension version is on its details page in Chrome.
Connect 1Password to Claude
- Where
- Claude: Customize, Connectors
- Authorize
- Touch ID or account password
- Undo
- Disconnect, same place
From the docs, not run here
- Open the 1Password desktop app and the Claude desktop app.
- In Claude, go to Customize, then Connectors.
- Find 1Password and click Connect.
- 1Password asks you to authorize the connection with Touch ID or your account password. With more than one account, pick the account first.
To remove it later, go back to Customize, Connectors and click Disconnect next to 1Password.
Approve a sign-in on a throwaway account
- Trigger
- A task that needs a login
- Claude sees
- Which login it used
- Claude never sees
- Password, one-time code
From the docs, not run here
Make a test account on a site you do not care about and save its login in 1Password, with the item's website field set to the exact sign-in URL. That field is how 1Password picks the login.
- In Claude, choose +New, then Cowork, and ask Claude to sign in to the test site.
- 1Password shows the login it suggests for that site. You can approve it, pick a different saved login, search for another item, or deny the request.
- Approve it, and the 1Password extension fills the login on the page. Claude in Chrome may also ask you to allow navigation to the site.
- If the site uses Google or Facebook sign-in, Claude asks for two items: the site's login and the linked provider login.
According to the docs, Claude only learns which login it used. The July announcement adds two details: access lasts for the current task only, and if the sign-in fails, 1Password clears what it filled before Claude gets the page back.
Know what Agentic Mode locks
- Turns on
- When Claude drives the browser
- Locks
- The 1Password extension
- Back to you
- Close the Claude tab group
From the docs, not run here
Agentic Mode is a separate feature of the 1Password browser extension, and it turns on whenever Claude controls your browser, even if you never connected 1Password to Claude. While it is on:
- The 1Password extension is locked and its interface is hidden.
- Inline autofill does not work, and you cannot sign in to other sites through it.
- The agent can only use the logins and one-time codes you approved for the current task.
To get control back, close the Claude tab group.
Claude Code: secrets, not sign-ins
- Plugin
- 1password@1password (beta)
- Claude Code
- 2.1.273 or later
- Claude sees
- Variable names only
From the docs, not run here
Claude Code does not sign in to websites through 1Password. What it gets is a plugin for 1Password Environments: your API keys and connection strings live in 1Password, and Claude Code can list and manage them without reading their values.
- In the 1Password desktop app, go to Settings, Developer and select Integrate with MCP clients.
- Start Claude Code in your project and install the plugin:
/plugin marketplace add 1Password/1password-claude-plugin
/plugin install 1password@1password
# then check the 1Password server is connected
/mcpThe first time Claude Code touches an Environment, the 1Password app asks you what it may do. The docs say the MCP server "never returns secret values stored in 1Password to the agent": Claude sees variable names. An Environment can also be mounted as a local .env file. The MCP server and the mounts work on Mac and Linux only.
If you run Claude Code on an Anthropic API key, a second piece, the 1Password CLI shell plugin, keeps that key out of plaintext. It needs the CLI at 2.34.0 or later:
op signin
op plugin init claude
source ~/.config/op/plugins.sh # add this line to ~/.zshrc to keep itThe key is stored as a 1Password item and handed to claude as ANTHROPIC_API_KEY when it runs, after a Touch ID or system prompt.
.env file, rotate them. Anything that was in Git history or in an agent's context is still out there.What it does not cover yet
- Passkeys and other item types. 1Password for Claude handles usernames, passwords and one-time codes from Login items, plus Google and Facebook sign-in. Passkeys are listed as not yet supported.
- Passwords saved anywhere else. The launch post says passwords saved in the browser or kept in notes do not work for agents. The agent stops until you sign in yourself.
- What happens after sign-in. Approval covers the credential. Once the agent is in, what it can do is up to the agent and the account. 1Password's own wording: "The safeguards and controls vary by integration."
- Agents with nobody to approve. Every sign-in waits for a person to approve it in 1Password. An agent running unattended on a server will wait.
The rules worth keeping
- Test with a throwaway account first, never your main email or your bank.
- Give the agent a clear stopping point, so it finishes and does not wander through the account.
- Disconnect the integration and close the agent's browser session when the task is done.
- Approve each sign-in by reading which login is requested and for which site, every time.
Building an agent or a tool for agents? Launch it on the weekly board: launching is free, every launch is reviewed by a person, and it gets a permanent listing page. Submit it here.
Sources
- 1Password, Introducing 1Password for Agents, October 22, 2026
- 1Password, 1Password for Claude, July 16, 2026
- 1Password Support, Use 1Password with Claude
- 1Password Developer, 1Password plugin for Claude Code and Claude Code shell plugin
Disclaimer: Nick Launches is not affiliated with 1Password or Anthropic. Read on November 2, 2026; availability and requirements change. The sign-in flow was not run for this guide.