The official sign-in checks

Grok Bot signs you in through the browser and then returns to the app. The troubleshooting page covers the ways that hand-off fails.

Documentation: Official troubleshooting ↗ Getting started and eligibility ↗

  1. Keep the Grok Bot app open for the entire browser sign-in.
  2. Confirm the browser page says sign-in succeeded before switching back.
  3. If the app did not pick it up, return to it manually and choose Get started or Sign In with Cursor again.
  4. Verify in the browser that the account you signed into actually has Grok Bot access on its plan.

The setting most people miss

Grok Bot requires cloud data storage. The getting-started page says accounts using Legacy Privacy Mode must move to a supported Cursor data setting before use. On a team, only an administrator can change it. If you have had Cursor for a long time and privacy mode was on, this is the most likely cause of an authentication loop that no local fix touches.

Documentation: Getting started and eligibility ↗ Official troubleshooting ↗

What the Windows threads found

The Windows 0.44.0 thread, 36 replies and nearly a thousand views, collects reports where update, logout and login, and cache clearing all failed. Some were entitlement problems fixed on the account side; some coincided with the late-August computer incident. A separate thread describes Windows sending messages that never get replies after a reset, which is a computer-health issue rather than sign-in; our not-responding guide covers that. One user reported a fully black window for days.

If your case matches, post your app version, plan, sign-in method, and timestamp in the existing thread. Buying a different plan or reinstalling repeatedly did not resolve the reported cases.

Documentation: Forum: Windows 0.44.0 authentication error persists ↗ Forum: sent messages but never replies after reset (Windows) ↗ Forum: black window, cannot get in ↗

  • Legacy Privacy Mode is off, or your admin has changed the data setting.
  • The signed-in account's plan shows Grok Bot access.
  • You are on the latest build from Settings, Beta, Check for Updates.
  • You have your version, plan, and timestamp ready to report.

Quick answers

Why does sign-in never complete?

The official docs say to keep the app open while the browser sign-in finishes, confirm the browser reports success, return to the app manually if it does not switch back, and retry Get started or Sign In with Cursor. If the account uses Cursor's Legacy Privacy Mode, Grok Bot will not work until the data setting is changed.

I updated, logged out, and cleared the cache. Still an authentication error. Now what?

That exact sequence is the title of a 36-reply Windows thread. Check the Legacy Privacy Mode setting first, confirm your plan actually shows Grok Bot access, then add your version and timestamp to that thread; several reports there were resolved server-side rather than by anything local.

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗