1Password launches a tool that lets AI agents sign in without seeing your password
On October 22, 2026 1Password announced 1Password for Agents. When a personal AI agent reaches a login page, it asks the user for a credential; the user approves the request inside 1Password, which fills the details into the site so the agent never receives them. Integrations for Muse and Grok Bot come first, rolling out over the coming days.
The agent signs in and never sees the password
1Password introduced its new platform on October 22, 2026 in a company blog post titled "Introducing 1Password for Agents", bylined John Torrey. The company describes the flow this way: an agent reaches a sign-in page, stops and asks for the credential it needs, the user reviews the request and approves it in 1Password, and 1Password then fills the details into the destination site itself. Neither the password nor a one-time code is handed to the agent.
TechCrunch's Lucas Ropek covered the launch the same day and describes the mechanics from the agent's side: the agent sends 1Password a unique digital key to confirm its identity, the user receives an alert about the login attempt, and once the user confirms, 1Password signs the agent in. The report adds that 1Password is working with other companies to broaden the service.
Which agents, and who can use it
According to 1Password's post, integrations for Meta's Muse and SpaceXSI Grok Bot are rolling out over the coming days. Integrations for Anthropic's Claude Duet, OpenAI's ChatGPT Work and dots, and Town Townie (web and iOS) are listed as coming soon. Instinct, Browserbase, Browser Use, Dana, Kernel, Perplexity, Ramp, Tomo and Wajo are also named as coming soon. That is the list as the post gives it. The company says people can join a waitlist if their agent is missing, and businesses building personal agents can contact its partnerships team.
The company draws two boundaries on scope. The feature is available at no additional cost for Individual and Family accounts on 1Password.com, and accounts on 1Password.eu or 1Password.ca are not supported at the moment. Availability, platforms and capabilities also differ by partner integration, and the safeguards and controls vary from one integration to the next. Users can see what will be shared and can disconnect the integration whenever they like.
Two poor ways to hand an agent a password
1Password argues that users currently have two options: take over the agent session and type the username and password by hand each time, or paste the password into a prompt. The second option could leave the credential in the agent's hands beyond the task at hand. The company also says browser-saved passwords are not built for agents to sign in with. That is a vendor positioning its own product, but the problem it describes matches what anyone running agents will recognise.
TechCrunch ties the launch to a banking development. It relays an Axios report from the same day saying U.S. banks have started detecting agent activity inside customer accounts and that most of them cannot tell whether it traces back to a user request. Per TechCrunch, a Chase spokesperson told Axios that customers should never share their login names and passwords with anyone. We could not open the Axios piece, so this rests on TechCrunch's account. We touched on agent identity earlier in our July 29 piece on Cyera and Oasis.
The sources say nothing about Türkiye, so this section is commentary
Neither source mentions Türkiye, availability there or Turkish language support. The 1Password post says the feature is offered to Individual and Family accounts on 1Password.com and that 1Password.eu and .ca accounts are not currently supported. TechCrunch gives no pricing or detailed rollout dates. This section is therefore not a fact drawn from the sources but UNALSOFT commentary.
Our reading: most of the named agents are still marked coming soon, and it is unclear whether a user in Türkiye could reach them. So the news is better read as a signal about how credentials should be delegated in agent-based automation than as a tool to adopt today. The sources do not say: support for accounts in Türkiye, a Turkish interface, partners in Türkiye or a local launch date.
The UNALSOFT view
We read this less as a product launch and more as a design principle: an agent does not need to hold a password to do its job, because approval and filling can sit in a separate layer. For a business planning automation that signs in to sites on a customer's behalf, the practical question is to write down up front which account the agent reaches, with whose approval and for how long. In agentic AI projects we treat that flow as the first line of the setup. The feature in this story is tied to 1Password accounts and specific agents, so the same assumption should not be carried over to other tools.
How will your agents sign in?
If you are planning agent-based automation, a short conversation is enough to settle the access and credential flow together.