1Password for Agents: AI agents log in without your password

1Password launched 1Password for Agents on October 22. Personal AI agents from Anthropic, OpenAI, Meta, Grok, and Town can now sign in to your accounts without the password ever reaching the agent. You approve each sign-in on your own device. In July we covered 1Password's Claude-only version. This is the cross-vendor play, and it lands the same day banks said they're watching for agents in customer accounts.

What actually happened

From 1Password's press release and TechCrunch's coverage:

• The flow: The agent hits a sign-in form and proves its identity to 1Password with a unique digital key. You see which credential it wants and why, then approve or decline. 1Password fills the form directly. The agent never receives the password.
• Named integrations: Meta's Muse, Anthropic's Claude Duet, OpenAI's ChatGPT Work and dots, Grok Bot, and Town's Townie. Partners listed include Browserbase, Browser Use, Perplexity, and Ramp.
• What's missing: The release gives no pricing, plan tiers, or GA status, and doesn't describe agent-specific audit logs or revocation. Per-request approval is the control it describes.
• The context: TechCrunch notes that Axios reported the same day that U.S. banks are detecting agent activity in accounts. A Chase spokesperson told Axios customers "should not give their usernames and passwords to anyone."

Why 1Password for Agents matters for your business

Pasting passwords into chat is now the wrong answer. Your team is already doing it. A browser agent that needs to log in to the supplier portal gets the password in plain text, and that text sits in a transcript forever. A fill-on-approval vault closes that hole.

Bank logins are a separate question. Chase's line is clear. Don't put bank credentials behind an agent, even with a vault in the middle, until your bank says it's allowed. Use the bank's own agent channel or API where one exists.

Approval is the control, so design for it. Every sign-in pings your phone. That's good for the CRM and bad for a job that logs in to twelve vendor portals at 6 a.m. Decide which accounts an agent may use at all before you decide how often you'll tap "approve."

Shared vaults need a rule. Put agent-usable logins in their own vault. Don't let an agent browse the vault that holds payroll and the domain registrar.

Sources: 1Password: 1Password for Agents press release, TechCrunch: 1Password launches a way for AI agents to log in on your behalf.