What does each one do?
- ›runnerID by Torchrunner: runnerID's own vault.
- ›1Password Secure Agentic Autofill: Your 1Password vault.
- ›TinyFish: Your connected 1Password or Bitwarden vault.
- ›runnerID by Torchrunner: runnerID types it into the page; the model never receives it.
- ›1Password Secure Agentic Autofill: Browserbase: the 1Password browser extension fills and submits without returning the values. Anchor and Browser Use Cloud: a 1Password service account.
- ›TinyFish: Resolved at the browser automation layer during a run; the agent sees labels and field names only.
- ›runnerID by Torchrunner: No.
- ›1Password Secure Agentic Autofill: 1Password says credentials never enter the LLM context. Browser Use notes that once typed, values are on the page, and its v4 agent can reach them through browser or CDP tools.
- ›TinyFish: No: kept out of prompts, logs and screenshots.
- ›runnerID by Torchrunner: Generated and typed.
- ›1Password Secure Agentic Autofill: Resolved at run time in Anchor and Browser Use Cloud.
- ›TinyFish: Supported when the vault item has a TOTP field; hardware keys and push are not.
- ›runnerID by Torchrunner: Yes, one per identity.
- ›1Password Secure Agentic Autofill: Not stated.
- ›TinyFish: Not stated.
- ›runnerID by Torchrunner: Yes.
- ›1Password Secure Agentic Autofill: Not stated.
- ›TinyFish: Browser Context Profiles keep session state.
- ›runnerID by Torchrunner: Site rules, plus approval by email link for risky actions.
- ›1Password Secure Agentic Autofill: Browserbase: a person approves the request in the 1Password desktop app.
- ›TinyFish: Not stated.
- ›runnerID by Torchrunner: Append-only log of every action; revoke shuts it all off at once.
- ›1Password Secure Agentic Autofill: Not stated.
- ›TinyFish: Not stated.
- ›runnerID by Torchrunner: A browser runnerID can reach (a hosted browser or one on your own server), where it types the password itself; a laptop browser through the helper's local route; codes, approvals and the log over MCP for hosted agents.
- ›1Password Secure Agentic Autofill: Partner browsers: Browserbase, Anchor, Browser Use Cloud.
- ›TinyFish: TinyFish web agent runs.
- ›runnerID by Torchrunner: Free (1 identity, 100 logins and codes a month, no card); Solo $12 a month (1 identity), Builder $29 (5), Team $99 (25).
- ›1Password Secure Agentic Autofill: Not stated.
- ›TinyFish: Not stated.
Where the password is filled, and what else is covered
The safe pattern is the same in all three: the model asks for a login, and something outside the model puts the password into the page. The difference is where that something lives. With 1Password, it is the 1Password extension or a service account inside a partner's hosted browser. With TinyFish, it is TinyFish's browser layer during a run. With runnerID, it is runnerID, which types into the browser your agent already uses.
- ›If runnerID can reach the browser (a hosted browser or one on your own server): Agents that drive a browser runnerID can reach, such as a hosted browser (Browserbase, Steel) or one on your own server, get the strongest mode: runnerID types the password itself.
- ›If the browser is on your own laptop: When the browser runs on your own laptop, the helper uses its local route: the password passes through your own code once to be typed, and still never reaches the model.
- ›If a hosted agent's browser is out of runnerID's reach: Hosted agents that connect over MCP get authenticator and emailed codes returned to them, and approvals and the log work the same. Typing a password into the page needs the runnerID helper next to the browser (Stagehand, Playwright or Browser Use), on a laptop or in a cloud container.
A login is often more than a password. Sites send a six-digit code, email a link, or ask again on a new device. 1Password and TinyFish both cover authenticator codes stored with the vault item, and TinyFish keeps sessions in profiles. runnerID puts all of it on one identity: the vault, authenticator codes, its own inbox for emailed codes and sign-in links, saved sessions, site rules with approval by email link, and an append-only log with revoke.
- ›You already keep team logins in 1Password and run agents in Browserbase, Anchor or Browser Use Cloud: 1Password Secure Agentic Autofill keeps those logins in the vault you have.
- ›You run TinyFish web agents and keep logins in 1Password or Bitwarden: its vault connection fills them inside the run.
- ›You run your own agent (Playwright, Stagehand, Browser Use, or an MCP client such as Claude or Cursor) and want logins, codes, an inbox, sessions, approvals and a log in one place: that is what runnerID is for.
Navvi is an open-source (MIT) MCP server. Its README describes persistent personas, a gopass credential vault that autofills so the AI does not see the password, persistent sessions, and 2FA by handing the screen to a person over VNC. It also lists an anti-detection browser, CAPTCHA handling and account signup. runnerID does none of those three: it is the verified agent of a real business, working through its own seat on accounts the owner controls, where the site offers one.
Bitwarden's Agent Access SDK is open source and in early alpha. An agent requests one credential at a time through an end-to-end encrypted flow that a person approves, and aac run passes approved fields to a child process as environment variables. The values reach a process you run rather than being typed by a service.
Free is $0 for 1 identity and 100 logins and codes a month, with no card. Solo is $12 a month for 1 identity, Builder $29 a month for 5, and Team $99 a month for 25, with no monthly limit. Paid plans are monthly through Stripe, cancel any time, and every plan has the same features.
Questions
Do runnerID, 1Password Secure Agentic Autofill and TinyFish keep the password away from the AI model?
All three keep the password out of the AI model. 1Password Secure Agentic Autofill fills from a 1Password vault inside partner browsers such as Browserbase, Anchor and Browser Use Cloud. TinyFish fills from a connected 1Password or Bitwarden vault during its own web agent runs. runnerID by Torchrunner keeps logins, codes, an inbox, sessions, approvals and a log in one identity you plug into your own agent.
What does runnerID cost?
Free is $0 for 1 identity and 100 logins and codes a month, with no card. Solo is $12 a month for 1 identity, Builder $29 a month for 5, and Team $99 a month for 25, with no monthly limit. Paid plans are monthly through Stripe, cancel any time, and every plan has the same features.
Sources, checked October 24, 2026
- ›1Password, "Closing the credential risk gap for browser-use AI agents": https://1password.com/blog/closing-the-credential-risk-gap-for-browser-use-ai-agents
- ›Browserbase docs, 1Password Agentic Autofill: https://docs.browserbase.com/integrations/1password/agentic-autofill
- ›Anchor docs, 1Password integration: https://docs.anchorbrowser.io/integrations/1password
- ›Browser Use Cloud docs, 1Password guide: https://docs.browser-use.com/cloud/guides/1password
- ›TinyFish docs, Credentials: https://docs.tinyfish.ai/key-concepts/credentials
- ›Navvi on PyPI: https://pypi.org/project/navvi/
- ›Bitwarden, "Introducing the Agent Access SDK": https://bitwarden.com/blog/introducing-agent-access-sdk/
- ›bitwarden/agent-access on GitHub: https://github.com/bitwarden/agent-access
Steel belongs to its owner. 1Password is a trademark of AgileBits. TinyFish, Navvi, Bitwarden, Browserbase, Anchor, Browser Use, Stagehand and Playwright belong to their owners. runnerID and Torchrunner are independent and are not affiliated with, endorsed by or sponsored by any of them.