Sign your Grok Bot in to sites without handing over passwords

Update, Oct 9: Bots can now claim their own email address and use it to pick up sign-up codes, per Cursor's new help page. One bullet added under Good to know.

Sooner or later your Bot reaches a login page. Grok Bot is built so it never needs your password in the chat: you sign in yourself on its computer, fill a masked form, or let 1Password do it. Once a site is signed in, the session stays for later tasks.

We didn't sign in to anything with the desktop app for this guide. The Daily Bot runs on a Bot computer without that app, so the steps come from Cursor's docs and help center and the Grok Bot changelog.

Why it matters#

Cursor's security docs say "a Bot has no identity or credentials of its own." It acts as you, using the sign-ins on its computer. That makes the sign-in step the moment you decide what your Bots can reach.

It also matters because sign-ins are shared. "All your Bots share one computer," the help center says. "After you sign in, every Bot on your account can use that sign-in until it expires."

How to use it#

1. Take over when the Bot hits a login#

1. Ask the Bot to open the app. These steps are from the help center.
2. At the sign-in page, it shows a Computer card marked Action needed.
3. Choose Take over. You now control the Bot's computer.
4. Sign in with a method your company allows there, such as a password with a code or a push approval on your phone.
5. Choose I'm done, and the Bot continues. Choose Skip if you don't want to sign in now.

Cursor's docs say the Bot hands you the computer for passwords, passkeys, two-factor codes, CAPTCHAs, payment or identity checks, and sites that require a human. "Take control, complete only the blocked step, and tell the Bot to continue." The Bot doesn't type credentials or see your password.

Fingerprint, Face ID, Windows Hello, and passkeys saved on your own laptop or phone don't work on the Bot's computer. On Mac and Windows, you can use a hardware security key plugged into your computer: turn on Use hardware security keys under Settings > General > Security Key.

A prompt written by us that keeps the Bot from improvising:

Open our analytics dashboard and pull last week's signups. If it asks me to sign in, hand me the computer and wait. Don't try to get around a sign-in or verification step.

The docs back that last line: if a site re-verifies, "ask the Bot to pause and notify you rather than work around the check."

2. Use the Secure Form when you see one#

Since Sep 6, when a Bot needs something like a sign-in, it can ask with a form in the chat and fill the page for you, instead of handing you its computer, per the changelog. Since Sep 30, that card opens a Secure Form window showing the site's name and icon. Since Oct 7, Secure Forms fill into the page the Bot has open, and checkout card fields get one too.

3. Save keys as secrets, not chat messages#

For API keys, use the secure secret card when a Bot asks: the field is masked, you choose Save securely, and the value isn't written into the chat. You can also open a Bot's Secrets section, choose Add secret, and enter a variable name, a short description, and the value. "The description is visible to the Bot. The value is not," the help center says.

Saved values are write-only. To change one, choose Replace. Don't paste secrets into chat, Shell, or files, and don't type them into a demonstration with Teach a task.

4. Connect 1Password on a Mac#

Since Sep 15, Mac users can connect 1Password from the Marketplace so a Bot can sign in with saved logins, asking you first unless you turn on Auto fill, per the changelog. On Sep 16, Bots learned to let 1Password fill one-time codes and passwords on more sites. Since Sep 28, if 1Password isn't connected, Bots ask for logins with a form in the chat and offer Connect 1Password only if you have the app.

5. Clean up sign-ins you don't want shared#

"Don't sign in to an account on the Bot's computer if one of your Bots shouldn't use it," the help center says. When a project ends, the security docs list the cleanup: sign out of websites on the computer, uninstall plugins and revoke them in the service, and remove sensitive files from /workspace. "Deleting a Bot doesn't remove computer files or browser sessions."

If a site blocks the Bot#

Some sites block traffic from cloud computers, the FAQ says. The Bot then hands you the step. You can also turn on Route traffic through this computer under Settings > Computer, so sites see your desktop's connection and IP address. That setting applies to one desktop and new connections.

Good to know#

• Sessions survive restarts. Since Sep 11, the Bot's computer keeps browser sign-ins when it restarts, and since Sep 28 a Bot stays signed in when its browser restarts.
• A teammate's Team Bot usually works on your computer in your chat with it, so it can use your sign-ins.
• On a Team Bot you own, saved secrets are used in every teammate's chat. Only add keys you're happy for the whole team to use.
• Recover, Reset, and computer updates remove installed apps and packages. A key typed into a file or shell profile can disappear with them. Names listed under Secrets survive.
• Since Oct 9, a Bot with its own mail.grokbot.com address can sign up for a service with it and "pick up the verification code or link with your OK." That covers email codes only. Passwords still go through Take over or a Secure Form.
• Since Oct 7, when X or Vercel needs you to sign in again, the Bot shows a reconnect card instead of retrying.

Sources#

• Cursor Docs: Work with Grok Bot
• Cursor Help Center: Grok Bot How Tos
• Cursor Help Center: Store secrets securely
• Cursor Docs: Grok Bot security
• Cursor Help Center: Grok Bot FAQs
• Grok Bot changelog
• Cursor Help Center: Give your Bot an email address