GROK BOT / fix-google-login-in-grok-bot-browser

Grok Bot

Fix Google login inside the Grok Bot browser (and missing Import cookies)

Fix Google login inside the Grok Bot browser (and missing Import cookies)

Cursor staff (deanrie, Sep 1, 2026) call Google login inside the Grok Bot browser a known limitation, not user misconfiguration. Login sharing works reliably for sites that keep sessions in cookies. Google and many app-style sites store part of the session in localStorage or IndexedDB, so signing in inside the agent browser may fail, ask again, or drop after the computer is recreated.

Missing “Import cookies from Chrome”

Under Settings → Computer, many users only see Current computer and Execution. Staff say Import cookies from Chrome is not broadly available yet and remains in development. That UI is the expected current state. Do not assume the feature is hidden behind a toggle you can enable.

Sign in with computer takeover

Official troubleshooting for sites that keep asking for login:

  1. When the Bot pauses on a sign-in page, take over the computer (or the Bot browser).
  2. Sign in yourself on the handed-over session.
  3. Complete any 2FA or CAPTCHA prompts on that session.
  4. Confirm the signed-in page finished loading.
  5. Tell the Bot to continue from there.

Do not paste passwords, one-time codes, or recovery codes into chat.

Per-agent browser sign-in

Staff (kevinn) track cases where signing in through one Bot should make that login available to other Bots on the same computer, yet a separate sign-in still appears. Intended model: Bots share one computer’s files, browser sessions, and logins. Cookie-based sites follow that model more reliably than Google-style localStorage sessions. See the per-agent browser thread.

Pitfalls

  • After Recover, Update, or Reset Agent Computer, a Google (or similar) session can drop even when cookie logins survive. Plan to take over and sign in again.
  • Cookie import from Chrome does not exist as a general user feature today. There is no documented workaround that copies Chrome cookies into the agent computer.
  • Corporate SSO / YubiKey for public SaaS uses the same takeover pattern. For VPN-only work hosts, see Reach VPN-only work apps from Grok Bot.