How an agent signs in without seeing your password

1Password for Agents launched on 22 October. The product page calls the feature Agentic Autofill, and the audience is anyone who has started letting a personal AI agent do work that needs a sign-in. When the agent reaches a login form, it “uses a unique digital key to verify its identity to 1Password,” in the words of the launch announcement: a credential the agent presents so the vault can tell which agent is asking. You see which stored login it needs and why, then approve on your own device. 1Password fills the password or one-time code into the form itself instead of sending it to the agent, and the agent carries on with the task.

The launch blog frames this as the end of two shortcuts: taking over the session to type your password every time, or pasting the password into a prompt. Aashish Tripathi, 1Password’s chief product officer, made the case for a narrower grant in the launch announcement: “The old model where you hand over a credential and hope for the best doesn’t work,” he said, adding that an agent “should be able to do the job it’s been asked to do without getting permanent access to everything behind the account.”

Rollout status is a separate story from the announcement. The platform is available; most named integrations are not. Only Meta’s Muse and SpaceXSI’s Grok Bot are “rolling out over the coming days across all platforms.” Anthropic’s Claude Duet, OpenAI’s ChatGPT Work and dots, and Town’s Townie (web and iOS) are “coming soon.” Instinct, Browserbase, Browser Use, Dana, KERNEL, Perplexity, Ramp, Tomo and Wajo are in the works, with no rollout date.

One naming detail: the vendor’s pages mostly write SpaceXSI, including the credit to “Tido Carriero, Head of Product at SpaceXSI” and the URL of the Grok Bot page, which also contains one instance of “SpaceXAI.” We use SpaceXSI, and the inconsistency stays visible.

Availability has edges. The blog says the feature is “currently available at no additional cost for 1Password Individual and Family accounts on 1Password.com,” and the product page says all Individual and Family plans include it. Accounts on 1Password.eu and 1Password.ca are not currently supported, and the Grok Bot page adds Business and Team Starter Pack accounts to that integration’s exclusions. The product page adds: “Availability and setup requirements can vary by integration, region, device, and sign-in method.”

What you approve is a sign-in

The prompt concerns a stored login. You see “which credential it needs and why,” and when more than one saved login matches the site, you choose which one 1Password uses. It does not ask you to approve an action, a purchase or a permission inside the account.

Frequency is not fixed. The product page FAQ answers, “How often you are asked to approve access may vary by integration,” which means approval is not necessarily one-shot and the vendor does not say how long a grant lasts or whether it can be widened. An August 2025 security-principles post set out the design intent: “1Password will enable authorization via an auth prompt of multiple specific credentials for a certain number of uses, a given amount of time, or in some cases more scoped usage.” That was written before launch as a principle. 1Password’s support pages for the feature were closed to us (HTTP 403), so the detail in this section comes from 1Password’s launch announcement, its blog posts, the product page and the partner pages.

Credential delivery is described; key issuance is not. The announcement says the agent “uses a unique digital key” without saying who issues it or how it is bound to one agent. A 2025 post on the browser-agent work says credentials travel over “an end-to-end encrypted channel between the approving 1Password device and remote instance of 1Password’s extension in the browser,” and that “any request made for credentials must be approved by a human by default.”

Disconnecting stops future use. The blog says you “can see and approve what will be shared and disconnect the integration at any time,” and the partner pages describe disconnecting when you no longer want Muse or Grok Bot using your stored logins. We found no documented way to end a session already open at the destination site.

Where it stops

The approval decides how the agent gets in. What happens next belongs to the agent and the site it signed into.

Inside an approved session, the agent has your authority

1Password answers this in its own FAQ. Asked what an agent can do after signing in, the product page says: “An agent may be able to see information or take actions within the signed-in account. Its behavior there depends on the agent and the website. Review the task and the account before approving access.” The Grok Bot page repeats the warning, and from that point the agent works with the account’s standing authority.

That limit also defines what the design does about prompt injection. Keeping the password out of the model’s context closes one class of attack, since an injected instruction cannot make the agent surrender a credential it never holds. An agent already signed in and following instructions from a poisoned page is a different problem. 1Password acknowledges the general risk in its own writing: a 2025 post about MCP states that “Prompt injection and hidden tool instructions can cause agents to inadvertently exfiltrate secrets,” and that “No strong revocation model exists once secrets are passed into context.” That post covers credential handling in general, and applying it to an approved session is our reading.

Where an agent brings its own guardrails, they belong to the agent. Meta’s Muse page says “Muse asks for confirmation before carrying out sensitive actions, such as making a purchase or sending an email.” 1Password does not enforce that, and the other partner pages omit it. The vendor’s summary: “The safeguards and controls vary by integration.”

The site cannot tell your agent from a rogue one

What arrives at the website is a signed-in session on a real account. A bank or a merchant sees a valid sign-in, and cannot tell that a person approved it a moment earlier or that the agent was steered there from another page.

Axios, as reported by TechCrunch on the same day as the launch, said US banks have begun to detect agentic activity inside customer accounts and that most banks cannot tell whether it is tied to a user’s request. TechCrunch reported that bankers described the situation as “horrifying,” and quoted a Chase spokesperson telling Axios that customers “should not give their usernames and passwords to anyone.” We could not read the Axios article, so the bank detail is secondhand. The general point holds without it: a relying party authenticates a credential.

What the vault does not cover

The feature as documented is browser sign-in. Agentic Autofill “helps a supported agent sign in through a browser,” filling the password or one-time code into the page, with credentials injected through 1Password’s browser extension. Non-web logins belong to separate 1Password developer tools: an SSH agent, Environments for local .env files, a CLI, shell plug-ins for tools such as AWS and Claude Code, and a beta sandbox for NVIDIA OpenShell that gives sandboxed coding agents scoped, time-limited access to secrets.

We found no independent audit, penetration test or third-party assessment of this feature. 1Password’s trust centre lists company-level certifications such as SOC 2 Type 2 and ISO/IEC 27001, a penetration-test report behind an access request, and a HackerOne bug bounty. None is presented as an assessment of 1Password for Agents, and the penetration-test report could not be read. Public web search was unavailable during research, so “we found none” covers the vendor’s pages, its trust centre, TechCrunch and the developer documentation.

Whether to switch it on

The feature solves a particular problem: your agent needs a sign-in, and you would rather not paste the password into a chat window or hand over the session. On an Individual or Family account at 1Password.com, with an integration that has actually rolled out, it improves on both habits.

It does not give you a review of what the agent does next. 1Password advises reviewing the task and the account before you approve, because the agent inherits that account’s authority once inside. Approve where you are comfortable with the agent acting on the site’s terms for the length of its task, and disconnect integrations you have stopped using: that ends future sign-ins and leaves an open session alone.