They do not. You already signed in, and a companion works there
Three models exist. Strawberry uses the one where no password moves anywhere and the two-factor challenge you already answered still covers the work.
Three answers, and which one a product uses tells you most of what you need to know. Credential hand-over: a cloud agent takes your passwords so its own machine can sign in as you. Scoped tokens: it never sees a login page and can do only what the token allows. Session reuse: it works in the browser on your computer, where you are already signed in, so no login happens at all.
Strawberry uses session reuse, plus a connected account where a real API exists. Companions work in the accounts you are already logged into, so there is no password to hand over, no vault to trust and no remote machine impersonating you. You connect an account once and see exactly what it can reach before you allow it. The full model is on the security page.
| Stored credentials (cloud VM) | API tokens | Your browser session | |
|---|---|---|---|
| Where your password goes | Vendor infrastructure | Nowhere (token instead) | Nowhere (no login happens) |
| Works on sites without APIs | Yes | Not built for it | Yes |
| 2FA | Engineered around | Not applicable | Already satisfied by you |
| Finishing a run with the lid closed | Yes | Yes | Yes. Keep Awake holds the machine awake |
| Revoking access | Change password, trust deletion | Revoke token | Close the browser |
What is wrong with an agent storing your password?
A copy of your password on someone else’s infrastructure is a second place your password lives, a second breach surface, and a login pattern your security team cannot tell apart from an attacker in a datacenter.
Session reuse deletes that problem instead of managing it. Nothing to store, nothing to leak, and every action originating from your own machine on your own network.
What happens with two-factor authentication?
It works, because the session that passed 2FA is the one being used.
You answered the challenge on your device the last time you signed in, and a fresh challenge lands on your phone as usual while the companion waits.
Under the credential model, 2FA is an obstacle the vendor engineers around: forwarding codes to a machine you cannot see, or asking you to approve pushes for it.
What this looks like on a real task
A monthly investor update.
The numbers live in four logged-in places: the payment dashboard, the analytics tool, the bank and the CRM. A companion opens all four in your session, pulls this month’s figures and assembles the update.
No password was typed anywhere new and no credential moved. That is the pattern behind an agentic browser that works in your accounts.
Access and permission are two separate dials
A companion in your session can act as you, which is the point and the reason for the second layer. Consequential actions pause on an approval card before they run, and Ask Always mode in Settings → AI permissions makes everything wait. You hold both dials, and the security page walks through each one.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents