Grok Bot won't sign in on Windows? Fix the hand-off, the account, then the network

Most Grok Bot sign-in errors on Windows come from one of four places: a browser hand-off that never returned to the app, an account that lacks Grok Bot access or uses Legacy Privacy Mode, a network path Cursor rejects, or a Bot computer that needs an update while you are actually signed in. Update the app first, then work through those in order. Reinstalling repeatedly and buying a different plan did not fix any of the reported cases.

The short answer#

• On Grok Bot 0.75.2 or later (Settings → Updates → Check for Updates)
• App kept open for the whole browser sign-in, and the browser said it succeeded
• Signed in with the account that actually holds a Grok Bot plan
• Legacy Privacy Mode off, and a Privacy Mode choice explicitly saved
• SSO users signed in through the organization login
• Desktop tried without VPN or proxy if the phone app works
• Signed in but sending fails: tried Update Bot's Computer before any Reset
• IT has allowed accounts.spacex.ai and accounts.x.ai before October 30, 2026
• Version, plan, sign-in method and timestamp noted for a forum report

Update before anything else#

The 0.75.2 release notes (October 22) rework sign-in. Browser sign-in now waits up to 20 minutes and offers Copy link, Reopen link resumes the same attempt, a failed connection tells you to check your network instead of blaming the browser, and the desktop app connects directly unless you have turned on a system proxy. A reinstalled app also skips onboarding for an account that already finished it.

Earlier fixes matter too. 0.71.2 (October 14) shows accounts without access a plain access notice instead of setup or load errors. The October 11 release relaunches a blank window after an update and offers reload or quit in a crash loop, which covers the "black window for days" reports. 0.78.1 (October 27) returns you to the approval screen after you buy a plan mid-sign-in, so the app finishes signing in.

Cursor's help adds that Grok Bot forces an update once your version is more than 14 days old and a newer one exists, showing Update required. The Windows build is listed for Windows 10 and 11 (x64); see our download guide for the right installer.

Fix the browser hand-off#

Grok Bot signs you in through the browser and then returns to the app. The official troubleshooting page describes these steps:

1. Keep the Grok Bot app open for the entire browser sign-in.
2. Wait until the browser page confirms sign-in succeeded.
3. If the app did not pick it up, switch back manually and choose Sign in on the welcome screen. If you are already inside the app, use Sign In with Cursor from Settings.
4. Confirm in the browser that the account you used has Grok Bot on its plan.
5. If your organization uses SSO, complete that login rather than a personal account. The docs treat this as its own failure mode.
6. On a self-serve Grok Business seat, sign out and use Sign in with Grok with the Grok account that holds the seat. Since 0.75.5, if the seat does not cover Grok Bot yet, the usage message tells you to ask your Grok Business admin to connect your team.

The sign-in page may now show Grok or xAI branding. SpaceXSI's docs say Grok Bot uses the shared xAI sign-in path. Signing in does not merge your X, Grok and Cursor accounts or change your plan, so pick the right account.

Check the account, not the PC#

Symptom → Fix

• Authentication loop no local fix touches → Legacy Privacy Mode. The getting-started page says Grok Bot needs cloud data storage, so accounts on Legacy Privacy Mode must move to a supported data setting. On a team, only an admin can change it. A September 9 staff answer adds that an explicitly saved Privacy Mode choice is required before Grok Bot can reach its computer.
• "Grok Bot is having trouble connecting", and Recover and Reset fail → Check for an ended trial. On October 8 staff found one such account's one-week trial had ended a month earlier and the app showed it as a connection error. Sign in at cursor.com with the same account, choose a plan that includes Grok Bot or link SuperGrok, then fully quit and reopen the app.
• Which plans qualify → Cursor's plans help says Grok Bot is included on The X Subscription's Premium, Super and Ultra, for individuals and team seats, but not on Plus or Free. Our pricing guide has the details.

Check the network#

If the phone app works and the desktop does not, suspect the route. On October 12 Cursor staff told one user that between October 10 and early October 12 the desktop's connection went through a VPN or proxy route Cursor's servers did not accept; reinstalling could not fix that. Try the desktop without the VPN or proxy before resetting anything.

In the big Windows thread, one sign-in that never completed was declined on the backend because of where the computer was connecting from: Cursor is not available in every region.

The October 30, 2026 domain move#

SpaceXSI's sign-in domains page says Cursor sign-in moves from authenticator.cursor.sh to accounts.spacex.ai and accounts.x.ai on October 30, 2026. It is not a forced logout, and SSO settings such as Okta tiles and ACS URLs stay the same. Companies filtering traffic (Zscaler and similar) must update allowlists first. Send IT this:

Please allow these hosts before October 30, 2026 so Grok Bot sign-in keeps working.

Preferred wildcards:

*.spacex.ai *.x.ai *.grok.com *.grokusercontent.com *.grokipedia.com

Minimum hosts if wildcards are not possible:

accounts.x.ai accounts.spacex.ai auth.x.ai auth.grok.com

auth.grokusercontent.com auth.grokipedia.com grok.com

Keep allowing:

*.cursor.sh *.cursor-cdn.com *.cursorapi.com *.cursorvm.com

Update any bookmarks that point at authenticator.cursor.sh.

When you look signed in but nothing works#

The Windows 0.44.0 thread, opened September 9 with 36 replies and over a thousand views, gathered people for whom update, logout, login and cache clearing all failed. Cursor staff split it in two.

Before blaming your PC, check the status guide: a cursor.com sign-in incident looks identical from your side.

"Local tools are turned off… set to 'Never'"#

A related case surfaced on October 16. Local tool execution was refused with that message even with the setting on Always allow. On October 18 Cursor staff said the message is misleading: for some newer accounts the app does not finish linking your computer, and until it does, the computer is treated as Never whatever Settings says.

1. Sign in at grok.com with the same account you use in Grok Bot.
2. Open Settings from the account menu, go to Privacy, click Edit, choose an option and save (saving matters, even with the same option).
3. Wait about a minute and ask the Bot again.
4. If it still refuses, quit Grok Bot completely and reopen it.
5. Check all your logins (X, Grok, Cursor) point to the same account; one reporter fixed it by merging accounts.

One user said this worked; two others, on October 19 and 20, said it did not. Staff said it has also cleared on its own after about a day for some. The setting now lives at Settings → Computer → Your computer → Execution on this computer.

Bots or plan missing after switching to The X Subscription#

A thread opened October 21, at about 790 views by October 25, collects reports of vanished Bots, sign-in loops, "That Grok account is already linked to another Cursor account", "Cursor session expired" and "Can't spin up this bot" after switching plans or unifying accounts. Staff said on October 21 that Bots are not deleted: the switch can leave Bots on one account and the plan on another. Switching is opt-in and permanent once done.

1. Sign out of Grok Bot everywhere, including the apps and grok.com.
2. Sign back in with the same method you used to create the Bots.
3. If they are still missing, note which side you land on: plan with no Bots, or Bots with a subscribe prompt.
4. Email support@x.ai with your account email and the X or Grok account you linked. Keep to one ticket; users said later tickets were closed as duplicates.
5. Until it is sorted, do not reset the Bot's computer, delete anything, buy a second subscription or retry the unify flow.

Staff said split accounts need a fix on Cursor's side; no general fix had been announced when we checked on October 25.

Common mistakes#

• Reinstalling over and over. It did not resolve any reported case.
• Resetting the Bot's computer when only sending fails. Update it instead.
• Signing in with a personal account when your company uses SSO.
• Ignoring the VPN when the phone app works fine.
• Opening multiple support tickets for the same account split.

Our take#

Update, then check the account before touching your PC: Legacy Privacy Mode, an expired trial and the wrong account explain more Windows sign-in failures than anything local. If you are behind a corporate firewall, get the new domains allowlisted before October 30. Our troubleshooting matrix maps the rest.

Frequently asked questions#

Why does Grok Bot sign-in never complete?#

Keep the app open during the browser sign-in, confirm the browser reports success, then return to the app and choose Sign in again if it did not switch back. Use your organization's SSO login if you have one. If your Cursor account uses Legacy Privacy Mode, Grok Bot will not work until the data setting is changed.

I updated, logged out and cleared the cache, and still get an authentication error. What now?#

In the 36-reply Windows 0.44.0 thread, most people stayed signed in and only sending failed. Cursor staff said updating the Bot's computer, now Settings, Computer, Update Bot's Computer, fixed it while keeping Bots and data. When login itself never completes, staff checked accounts on the backend; one session was declined because Cursor is not available in every region.

What changes on October 30, 2026?#

Cursor sign-in moves from authenticator.cursor.sh to accounts.spacex.ai and accounts.x.ai. Existing sessions stay signed in and SSO settings such as Okta tiles and ACS URLs do not change. Companies with firewall or proxy allowlists must add the new hosts before that date, or sign-in will fail.

My Bots disappeared after I switched to The X Subscription. Are they gone?#

Cursor staff said on October 21 that they are not. The switch can leave Bots on one account and the plan on another. Sign out everywhere, including grok.com, and sign back in with the method you used to create the Bots. If they are still missing, email support@x.ai, and do not reset, delete or buy a second subscription meanwhile.

Why does the Grok Bot sign-in page show Grok or xAI branding?#

SpaceXSI's docs say Grok Bot now uses the shared xAI sign-in path, with no separate Grok Bot login, so the page may show Grok or xAI branding. Signing in only authenticates you; it does not link or merge your X, Grok and Cursor accounts or change your plan. Pick the account that holds your plan.