Pasting your bank password into a chatbot so it can pay a bill for you has always been a terrible trade — and on 22 October 2026, 1Password launched 1Password for Agents to kill that habit. It is a sign-in platform that lets personal AI agents log in to your accounts on your behalf without ever seeing your credentials: the agent proves who it is with a digital key, you approve the login on your own device, and 1Password types the password into the form itself. This guide walks you through exactly how the flow works, which agents support it, and the checks to run before you tap approve.
What is 1Password for Agents?
1Password for Agents is a trust layer between your AI agent and your logins: the agent never receives your password, secret or credential at all. Announced by 1Password on Thursday 22 October 2026 and reported by TechCrunch the same day, it targets the shortcut most agent users already take — dropping a password into a chat window so the agent can get into an account. “Handing over a password, secret, or credential is a common shortcut to an agent, but can leave people with sensitive information in places they can no longer control as a copy gets saved for the next time,” the company said in its launch blog post.
The product logic is simple, and 1Password’s chief product officer Aashish Tripathi stated it plainly: “An agent should be able to do the job it’s been asked to do without getting permanent access to everything behind the account.” In other words, an agent asked to reorder groceries has no business walking away with the keys to your email, your bank and your cloud storage.
How the approval flow works, step by step
Every login is a four-step handshake — the password travels only between 1Password and the sign-in page, never to the agent. Here is the flow as described in the launch coverage:
- The agent hits a sign-in form and identifies itself. Instead of asking you for the password, the agent sends a unique digital key to 1Password to verify its identity.
- You get an alert on your own device. 1Password shows you which credential the agent is asking for and why — which account, for what task. Nothing proceeds until you personally confirm.
- 1Password fills the form, not the agent. Once you approve, 1Password types the credential directly into the sign-in page on the agent’s behalf.
- The credential is removed — access is per session. Reporting notes that 1Password then removes the credential so the agent cannot read or reuse it as it continues the task. Approval grants one session, not permanent access; a future task starts the handshake again.
Think of it as a bouncer at the door of each account: the agent shows its ID, you wave it in, the bouncer opens the door — but the agent never gets a copy of the key.
Which AI agents are supported?
At launch, 1Password names five partner agent lines: Meta’s Muse, Anthropic’s Claude Duet, OpenAI’s ChatGPT Work and Dots, Grok Bot, and agents from startup Town. SiliconANGLE’s launch-day reporting adds that with 1Password connected, Grok Bot can sign in without anyone pasting a password into it, and that Town — which raised $108 million this week — has signed up too.
Two caveats worth knowing before you rely on a specific agent:
- Rollout is staggered. One report described launch-day integrations as starting with Muse and Grok Bot, with Dots, Claude Duet and others following — while other outlets list them all as launch partners. Treat the partner list as announced-but-rolling-out, and check 1Password’s own site for the current status of your agent.
- More partners are lined up. Perplexity and Ramp were reported as coming next, and 1Password says it is working with additional companies to expand the service.
On availability: the platform is included with eligible Individual and Family accounts on 1Password.com, but .eu and .ca accounts are not yet supported at launch. If your vault lives on a European or Canadian 1Password domain, this is a wait — not a launch feature. If you use Dots specifically, our Cowork vs Dots head-to-head explains what that agent is built for.
How to set it up
Setup is a one-time pairing between 1Password and your chosen agent — after that, every login is just an approve tap. The exact screens will vary by agent as integrations roll out, but the documented pattern is:
- Update 1Password and pick your agent. Make sure your 1Password app is on the latest version, then choose your agent of choice from the supported list above.
- Connect the agent to 1Password. Follow the pairing flow — this is where the agent registers its digital identity key with your vault, the key it will present at every future sign-in.
- Trigger a sign-in and approve it on your phone. Ask the agent to do something that needs a login. When the approval alert arrives, check it matches the task you actually asked for — account name, site, and reason — then approve.
- Watch the session boundary. When the task ends, the session ends. The next task re-asks. If an agent ever asks you to paste a password into chat instead, that is the old pattern — decline and route it through the approval flow.
Transparency note: this walkthrough is desk-researched from the launch reporting of 22 October 2026 — we have not run the pairing flow hands-on yet, so treat the step labels as the documented pattern rather than tested screenshots. Our standards for tool coverage are on our how-we-test page.
The approve-or-deny checklist: 6 questions before you tap approve
The approval alert is only as good as your judgment in the three seconds you read it — run this checklist every time. This is the part no launch announcement writes for you:
- Is this the task I asked for? The alert tells you which credential and why. If you asked the agent to check a flight and it wants your bank login, deny — that is a scope break.
- Is the account worth delegating? Treat accounts like airport security zones: email and banking are the highest-trust zone. An agent that only needs your grocery account should never be approved for your inbox.
- What can the agent do once inside? 1Password protects the credential, not the data behind it. An agent inside your email can still read every message. Approve access to the account, not just the login.
- Is this the right agent? A general assistant and a single-purpose shopping agent have different blast radii. Keep high-trust accounts paired to as few agents as possible.
- Would I type this password in myself right now? If the answer is “not on this device” or “not for this,” the agent should not get in either.
- Can I revoke it? Session access ends the session, but also check the account itself: does the site show active sessions you can kill, and do you know where? Revocation is a feature you test before you need it.
For the wider discipline of agent permissions — what an agent should and should not be allowed to touch — see our AI agent permissions guide.
Why banks are the reason this launched now
The timing is not a coincidence: US banks have begun detecting AI agent activity inside customer accounts. TechCrunch tied the launch to an Axios report that banks are now spotting agentic activity in user accounts — and struggling to tell whether it comes from the customer or from an agent acting for them. Chase has told customers they “should not give their usernames and passwords to anyone.” We have been tracking this collision: several banks and services have moved from tolerating agents to actively blocking them, as covered in our piece on banks blocking AI agents.
| The old way (pasting passwords into chat) | 1Password for Agents | |
|---|---|---|
| Who sees the password | The agent, the chat log, and anywhere it gets copied | Only 1Password and the sign-in page |
| Duration of access | Permanent — until you change the password | One session — re-approval required next time |
| Your involvement | None after pasting | You approve each login on your own device |
| Agent identity | Unverified — any agent with the password gets in | Digital key verifies the agent to 1Password |
Honest limits you should know
This fixes credential sharing — it does not make AI agents safe by itself. Keep these limits in mind:
- Data access ≠ credential access. An agent that cannot see your password can still read everything the account shows it. A read-only-view agent in your inbox is still an agent reading your inbox.
- Bank policy still applies. Chase’s warning — do not share logins with anyone — was aimed at exactly this behaviour. An approval flow does not override a bank’s terms of service; if your bank prohibits third-party access, an agent logging in could still breach your agreement.
- Geography gaps at launch. .eu and .ca 1Password accounts are not supported yet, per launch reporting.
- It is day one. Partner integrations are rolling out in stages and details may shift. Re-check 1Password’s announcement page before building a workflow around a specific agent.
Frequently asked questions
Does the AI agent ever see my password with 1Password for Agents?
No. The agent sends a digital key to prove its identity, you approve the request on your own device, and 1Password fills the credential into the sign-in form directly. The credential is then removed so the agent cannot read or reuse it, and access lasts for that session only.
Which AI agents work with 1Password for Agents?
Announced partners include Meta’s Muse, Anthropic’s Claude Duet, OpenAI’s ChatGPT Work and Dots, Grok Bot, and Town’s agents, with Perplexity and Ramp reported as coming next. Reporting differs on which integrations are live on day one, so verify your agent’s status on 1Password’s site.
Is 1Password for Agents free?
It is included with eligible Individual and Family accounts on 1Password.com. Accounts on 1Password’s .eu and .ca domains are not supported at launch.
Is it safe to let an AI agent into my bank account this way?
Safer than pasting your password into a chat, but not risk-free — and not necessarily within your bank’s rules. US banks are actively detecting agent activity in customer accounts, and Chase advises customers not to share credentials with anyone. Check your bank’s policy on third-party access before approving an agent login.
How is this different from 1Password’s earlier Claude integration?
In July 2026, 1Password and Anthropic released a beta letting Claude complete tasks needing usernames, passwords and authentication codes without those credentials reaching the model. 1Password for Agents generalises that idea into a platform across many agents, with the digital-key identity check and per-session approval flow as the standard pattern.
Sources and methodology
Launch details and mechanics: TechCrunch, 22 October 2026; SiliconANGLE, 22 October 2026; eligibility and regional limits via AI Weekly’s launch summary, 23 October 2026. Partner rollout details are attributed per outlet where reports differ. Claims rest on launch-day reporting verified 2026-10-23; the setup walkthrough and checklist are desk-researched analysis, not hands-on testing.
Govind Dheda covers AI tools, guides and prompts for OpenAIMaster — what is new, what is worth using, and how to put AI to work.


