The official sign-in checks

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

Update first if you can. The 0.75.2 release notes (October 22) say browser sign-in now waits up to 20 minutes and offers Copy link, Reopen link resumes the same sign-in instead of starting over, the app asks you to check your connection when sign-in can't connect instead of saying it stopped waiting for your browser, the desktop app connects directly unless you have turned on a system proxy, which fixes loading behind some corporate proxies, and a new or reinstalled app skips onboarding for an account that already finished it. 0.71.2 (October 14) says accounts without Grok Bot access finish setup and see just the access notice instead of setup or load errors, and that Restart to Update goes away when an update is withdrawn, with download retries backing off. These are fixes as described in the notes, not a guarantee for every account.

Documentation: Official troubleshooting ↗ Getting started and eligibility ↗ Cursor help: plans and billing (which plans include Grok Bot, Grok Business seats) ↗ Grok Bot changelog 0.71.2 (October 14): access notice, account merges, withdrawn updates ↗ Grok Bot changelog 0.75.2 (October 22): sign-in connection message, 20-minute browser sign-in, corporate proxies ↗ Grok Bot changelog 0.75.5 (October 23): Grok Business seat message, Bots kept after a merge ↗

  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 Sign in on the welcome screen again; if you are already in the app, use Sign In with Cursor from Settings.
  4. Verify in the browser that the account you signed into actually has Grok Bot access on its plan.
  5. If your organization uses SSO, complete the organization login rather than signing in with a different personal account; the troubleshooting page calls this out as a distinct failure mode from a stuck browser hand-off.
  6. If you have a seat on a self-serve Grok Business plan, Cursor's plans help says to sign out of Grok Bot and sign back in with Sign in with Grok using the Grok account that holds the seat. Since 0.75.5, if that seat doesn't cover Grok Bot yet, the usage limit message says to ask your Grok Business admin to connect your team.

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. A Cursor staff answer on September 9, about a Mac that kept showing Can't reach your computer, adds that Grok Bot needs an explicitly saved Privacy Mode choice before it can connect to its computer.

Check that the account still has access, too. On October 8 a Cursor staff member answered a Mac user whose app said Grok Bot is having trouble connecting, and whose Recover and Reset both failed: the account's one-week trial had ended a month earlier, and the app showed the lost access as a connection error, which staff called misleading and are tracking. The fix was to 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. Cursor's plans help, rechecked October 25, says that on The X Subscription Grok Bot is included on Premium, Super and Ultra, for individuals and team seats, but not on Plus or Free, and 0.71.2 says an account without access now sees just the access notice rather than setup or load errors.

Your network can matter as well. On October 12 a Cursor staff member (Colin) told a Mac user whose desktop app could not reach the Bot's computer while the phone app worked that, between October 10 and early October 12, the desktop app's connection was going through a VPN or proxy route Cursor's servers were not accepting; reinstalling and signing in again could not change that. If the phone works and the desktop does not, try the desktop without the VPN or proxy before resetting anything. The 0.75.2 release notes say the desktop app now connects directly unless you've turned on a system proxy, which fixes loading behind some corporate proxies.

Version matters too. Cursor's help says Grok Bot requires an update when your version is more than 14 days old and a newer one is out, showing Update required, and since 0.65.0 automatic updates are on by default. The x.ai/bot download list describes the Windows build as Windows 10 and 11 (x64); see our platforms guide for the right installer.

Documentation: Getting started and eligibility ↗ Official troubleshooting ↗ Forum: persistent Can't reach your computer until a Privacy Mode choice is saved (staff answer, September 9) ↗ Forum: trouble connecting and Reset fails after a trial ended (staff reply, October 8) ↗ Forum: desktop app could not connect through a VPN or proxy route while the phone worked (staff reply, October 12) ↗ Cursor help: how-tos (required updates) ↗ Cursor help: plans and billing (which plans include Grok Bot, Grok Business seats) ↗ Grok Bot downloads (x.ai/bot) ↗ Grok Bot changelog 0.71.2 (October 14): access notice, account merges, withdrawn updates ↗ Grok Bot changelog 0.75.2 (October 22): sign-in connection message, 20-minute browser sign-in, corporate proxies ↗

What the Windows threads found

The Windows 0.44.0 thread, opened September 9 with 36 replies and more than a thousand views, collects reports where update, logout and login, and cache clearing all failed. Cursor staff split it into two cases. Where the app still looks signed in but sending fails with an authentication error, updating Grok Bot's Computer resolved it for most people, and staff reset some computers from their side. Where the browser sign-in never completes, staff checked the session on the backend; in one case it was being declined based on where the computer was connecting from, because Cursor is not available in every region. 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; the October 11 changelog (0.69.0 to 0.70.2) says a blank window after an update now relaunches and a crash loop offers to reload or quit, and that switching accounts now lands within seconds even when another computer is asleep, so install the latest build before anything else.

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. One sign-in dead end does have a release-note fix: 0.78.1 (October 27) says buying a plan during desktop sign-in now returns you to the approval screen, so the app finishes signing in. Before that, check Is Grok Bot down?: a cursor.com sign-in incident looks the same from your side.

A related but distinct case surfaced October 16: a thread (377 views as of October 25) reported local tool execution permanently refused with "Local tools are turned off. The user has set local tool access to 'Never'", even with Execution on Local Computer set to Always allow, and only on one account while other accounts on the same Mac worked normally. The reporter traced it to their X and Grok logins being on one account while Cursor was signed into a different one, and merging the accounts fixed it for them. Several new X Premium subscribers on Mac and Windows then reported the same message without any second account. On October 18 a Cursor staff member (Colin) explained that the message is misleading: for some newer accounts the app doesn't finish linking your computer to your account, and until it does the computer is treated as Never whatever Settings says, so restarting, reinstalling, toggling the setting or signing out and back in don't help. His workaround: sign in at grok.com with the same account you use in Grok Bot, open Settings from the account menu, go to Privacy, click Edit, choose a privacy option and save (saving is what matters, even if you keep the same option), wait about a minute, then ask the Bot again, and if it still refuses, quit Grok Bot completely and reopen it. He said it has also cleared on its own after about a day for some people, that it is a known issue Cursor is tracking, and that checking all your logins point to the same account is still worth doing. One user said the steps worked; two others, on October 19 and 20, said they did not.

The official place to check the setting has also moved. The troubleshooting page, last updated October 22, says to open Settings → Computer → Your computer and find Execution on this computer for the desktop (Execution on Local Computer until the desktop is listed), and to keep local access off unless a task needs files or commands on the computer in front of you.

Documentation: Grok Bot changelog: 0.78.1 (buying a plan during desktop sign-in returns to the approval screen, October 27) ↗ Forum: Windows 0.44.0 authentication error persists ↗ Forum: sent messages but never replies after reset (Windows) ↗ Forum: black window, cannot get in ↗ Grok Bot changelog (blank-window and crash-loop fixes, October 11) ↗ Official troubleshooting ↗ Forum: local tools stuck on Never for some newer accounts (Mac and Windows, staff workaround October 18, 377 views as of October 25) ↗

  • You are on 0.75.2 or later, which changed the sign-in wait, connection message and proxy handling.
  • Legacy Privacy Mode is off, or your admin has changed the data setting.
  • The signed-in account's plan shows Grok Bot access, and a trial has not quietly ended.
  • You are on the latest build from Settings → Updates → Check for Updates.
  • If you look signed in but sending fails, you tried Update Bot's Computer (Settings → Computer, under Bot's computer) before anything destructive.
  • If the phone app works but the desktop does not, you tried the desktop without a VPN or proxy.
  • If your account uses SSO, you signed in through the organization login, not a personal account.
  • You have your version, plan, and timestamp ready to report.
  • If your company filters sign-in traffic, IT has allowed accounts.spacex.ai, accounts.x.ai and the other listed hosts before October 30, 2026.

Bots or plan missing after switching to The X Subscription

A forum thread opened October 21, with about 790 views by October 25, collects reports from people whose Bots vanished, or whose app said their plan does not include Grok Bot, after they bought or switched to The X Subscription or tried to unify their X, Grok and Cursor accounts. Users describe the Mac app refusing to sign in, a Grok Bot app stuck in a sign-in loop, the message That Grok account is already linked to another Cursor account, Cursor session expired, and, for several users, Can't spin up this bot when creating a replacement in Grok.

A Cursor staff member (mohitjain) replied on October 21 that the Bots are not gone: during the switch they can end up on a different account from your plan, so one side shows the plan with no Bots and the other shows the Bots but asks you to subscribe. For one user he said the account-combine step had left the Bots on one account and the plan on the other, that putting them back needs a fix on Cursor's side, and that nothing the user did caused it. On October 20 another staff member (Colin) wrote that switching is opt-in for existing subscribers and permanent once done, and asked anyone with a wrong charge, missing Bots or a plan that didn't carry over to email support@x.ai with their Cursor account email and the X or Grok account they linked. Users were still posting new cases with support ticket numbers on October 25, and no staff reply in the thread had announced a general fix.

Recent releases touch merges but do not claim to fix this split. 0.71.2 shows Your accounts are being merged in Settings while a paid merge is still moving data, with Contact Support if it runs long, and makes merges that move many Bots finish in one go; 0.75.2 says the remaining account keeps its Grok Bot email inbox and connector settings after a merge, and that linking an already unified Grok account offers to merge into it instead of failing; 0.75.5 says you keep managing the Bots you created after a merge.

Documentation: Forum: all my Grok Bots disappeared after the X Subscription switch (788 views, staff replies October 21) ↗ Forum: Introducing The X Subscription (staff reply on opt-in switching and support, October 20) ↗ Grok Bot changelog 0.71.2 (October 14): access notice, account merges, withdrawn updates ↗ Grok Bot changelog 0.75.2 (October 22): sign-in connection message, 20-minute browser sign-in, corporate proxies ↗ Grok Bot changelog 0.75.5 (October 23): Grok Business seat message, Bots kept after a merge ↗

  1. Fully sign out of Grok Bot everywhere, including the apps and grok.com, then sign back in using the same method you used when you created the Bots, as staff advised.
  2. If they are still missing, note which side you land on: a plan with no Bots, or Bots with a subscribe prompt.
  3. Email support@x.ai with the email on your account and the X or Grok account you linked, and keep to one ticket; several users said later tickets were closed as duplicates.
  4. Until it is sorted, do not reset the Bot's computer, delete anything or buy a second subscription; staff said that can make recovery harder. Several users also said support told them not to retry the unify flow.

Quick answers

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

SpaceXSI's X Subscription docs (the sign-in page was last updated October 5, 2026, and reread by us October 25) say Grok Bot now uses the shared xAI sign-in path, with no separate Grok Bot login, and the page may show Grok or xAI branding. Signing in only authenticates you: it does not link or combine your X, Grok and Cursor accounts or switch your plan. If you have more than one account, check you picked the one that holds your plan.

What changes on October 30, 2026?

SpaceXSI's sign-in domains page, reread October 25 and still dated October 5, says Cursor sign-in moves from authenticator.cursor.sh to accounts.spacex.ai and accounts.x.ai on October 30, 2026. Until then authenticator.cursor.sh remains the sign-in page. Existing sessions stay signed in, it is not a forced logout, and SSO identity-provider settings such as Okta tiles and ACS URLs do not need to change. If your company uses a firewall or proxy allowlist such as Zscaler, IT should add the new hosts before October 30, or sign-in will fail after it: preferably the wildcards *.spacex.ai, *.x.ai, *.grok.com, *.grokusercontent.com and *.grokipedia.com, or at least accounts.x.ai, accounts.spacex.ai, auth.x.ai, auth.grok.com, auth.grokusercontent.com, auth.grokipedia.com and grok.com, while keeping *.cursor.sh, *.cursor-cdn.com, *.cursorapi.com and *.cursorvm.com allowed. Update bookmarks that point to authenticator.cursor.sh.

My Bots disappeared, or the app says my plan doesn't include Grok Bot, after I switched to The X Subscription. Are they gone?

Cursor staff say no. On October 21 a staff member wrote that during the switch Bots can end up on a different account from the plan, so one side shows the plan with no Bots and the other shows the Bots with a subscribe prompt. Fully sign out of Grok Bot everywhere, including grok.com, and sign back in with the same method you used to create the Bots. If that does not bring them back, email support@x.ai with your account email; do not reset the Bot's computer, delete anything or buy a second subscription meanwhile. For accounts where the combine step split Bots and plan, staff said putting them back needs a fix on Cursor's side that they are tracking. Users in that thread were still waiting on October 25.

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 choose Sign in on the welcome screen again, or Sign In with Cursor from Settings if you are already in the app. If your organization uses SSO, complete that organization login rather than a personal account. 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. Cursor staff said that for most people there the app stayed signed in and only sending failed, and updating Grok Bot's Computer (now Settings → Computer → Update Bot's Computer) fixed it while keeping Bots and data. When the login itself never completes, staff checked accounts on the backend; in one case the session was declined because Cursor is not available in every region. Check Legacy Privacy Mode and your plan first, then add your version and timestamp to that thread.

Sources & next steps

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

Build your own workflow brief →