Let an AI agent sign in without seeing your password

To let an AI agent sign in to a website safely, never give it the password. Save the login with a tool that types it into the site for the agent. In Brainwrite, a bot asks Brainwrite to fill a saved login, and Brainwrite types the username, password and 2FA code into that site's login page. The bot only hears whether it worked.

Why pasting a password into chat is a bad idea

Agents do useful work behind logins: partner portals, billing dashboards, supplier sites. The quick fix is to paste the password into the chat. Then it is in the conversation, in logs and in whatever the model sees next. A web page the agent reads could even try to talk it into using that password somewhere else.

So a Brainwrite bot never asks for a password or a one-time code in chat. If you paste a token anyway, the bot won't use it. It tells you to rotate it and asks again on a secure card.

Step 1: let the bot ask

When a bot reaches a site it can't get into, it stops and shows a Sign in needed card. The card names the site and quotes the bot's reason. You get three choices:

• Open takes you to the bot's own browser, already in your control. You sign in yourself, then choose Done and the bot carries on.
• Save a login opens a short form for the username, the password and, optionally, the site's 2FA setup key.
• Cancel tells the bot you said no.

Step 2: save the login once

Saved logins are encrypted on the computer Brainwrite runs on and never shown again. A login saved from a card is for the bot that asked. One added in Settings → Logins is for every bot unless you pick bots.

A login fills only on its own site, over https. A login for example.com fills on accounts.example.com, never on example.com.evil.test. For a company that shares a domain, such as acme.okta.com, tick Only on this exact address.

If your team already keeps logins in 1Password, choose Connect 1Password. Paste a service account token that can read one vault, and its logins appear as From 1Password.

Step 3: let it handle 2FA

Save the site's 2FA setup key with the login. That is the key, or the otpauth:// address in the site's QR code. Brainwrite then makes the one-time code as it fills the form, the way an authenticator app does. For codes sent by email, a bot can read the code in your connected inbox and type it into that site. It never pastes a code anywhere else.

Tokens work the same way

APIs need tokens, not passwords. A bot asks for one with a Secret needed card that names the one https site it may go to. The bot names the secret, and Brainwrite adds the real value only when it sends the request. Anything the site sends back is cleaned of the token before the bot sees it. Every secret lives in one place, with what it may be used for.

Put it to work

Pair saved logins with an automation and the boring monthly jobs run on their own. Downloading a payout report or pulling an invoice list from a portal with no API are good examples. See month-end close and invoice chase for teams that do this.