Grok Bot: per-agent browser still requires separate sign-in despite account-level login promise

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Grok Bot launch notes say the computer is account-scoped and a login should be available to all bots. In practice, each agent has its own browser window and the same site still needs a fresh human sign-in / 2FA handoff per agent.

Actual Behavior: Auth appears scoped to each agent’s browser window, so N agents ⇒ N login handoffs for the same account.

Steps to Reproduce

  1. Agent A opens a site that needs login → user signs in on that agent’s browser → leave session open.
  2. Agent B (different agent) opens the same site.
  3. Agent B is signed out → second full human auth handoff for the same account.

Expected Behavior

Sign in once per account for the fleet; other agent browsers inherit or reuse that auth (first login / real step-up 2FA still human). Matches the announced account-level computer/logins model.

Operating System

Linux

Version Information

Cursor 3.15.6 (Grok Bot 0.16.0)

Additional Information

MCP connectors stay preferred where they exist; this is about the browser path agents already use. Happy to help validate a fix.

Ref: Introducing Grok Bot

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hi @manolito_nora

Thanks for the detailed report. Signing in through one Bot should make that login available to the other Bots on the same computer, so requiring separate sign-ins is not intended or caused by your setup. This is an issue we’re tracking, and we’ve shared your report with the team. Will keep you updated on progress, please let me know if you have any more specific context you’d like to add, e.g. “This happened with Gmail, or Github etc”

8

Thanks Kevin. The repeat handoff we keep hitting is Google (accounts.google.com → Gmail / Calendar / Drive). Agent A signs in, session stays open on that bot’s browser. Agent B opens the same Google account on the same computer / same Cursor account and still gets a full sign-in + 2FA. Same thing on other logged-in web apps on that machine (e.g. Monarch). MCP Gmail/Calendar connectors are fine; this is only the browser path. Happy to retest when you have a build.

9

I am having similar problem where agent browser signs out of google accounts every few hours

10

Got it! Thanks for the heads up.