Fix problems
Grok Bot sign-in error on Windows: update, privacy setting, SSO
By Tal Slavin · Last checked · Next review 2026-11-06
Grok Bot sign-in error on Windows: update, privacy setting, SSO
Authentication error or a sign-in loop on Windows: update the app and the computer, check Legacy Privacy Mode and SSO, and the October 30 domain move.
◈Key Takeaways (5)
- •Update the app to 0.75.2 or later; browser sign-in now waits up to 20 minutes.
- •Legacy Privacy Mode blocks Grok Bot; change the Cursor data setting or ask your admin.
- •Signed in but sending fails: try Settings, Computer, Update Bot's Computer first.
- •If your organization uses SSO, sign in through it, not a personal account.
- •From October 30, 2026 sign-in moves to accounts.spacex.ai and accounts.x.ai; firewalls must allow them.
☰On this page (4 sections)
An "Authentication error" or a sign-in loop after an update, logout or cache clear is often not purely a sign-in problem. Work through these in order.
- Update the desktop app to the latest version (0.75.2 or later), then quit fully and reopen. From 0.75.2 the browser sign-in waits up to 20 minutes and copes better with corporate proxies.
- Update the Bot's computer: Settings, Computer, Update Bot's Computer (or Recover if offered). This is the fix for "looks signed in, but sending fails with an authentication error", and it keeps Bots and data.
- Check Legacy Privacy Mode. Grok Bot requires data storage and does not support Legacy Privacy Mode. On a team account only an admin can change it.
- Use SSO if your organization has it. Complete the organization login, not a personal one.
- Check the account and plan. Bots that seem missing after switching to The X Subscription are usually on another account, not deleted. An ended trial can also appear as a connection error.
- Try a private browser window for the sign-in. This is our suggestion, not an official step; clear cookies for the sign-in sites only if the window does not help.
Contact support only after these, with your app version, the exact error text and a request ID if one is shown.
The October 30 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 that filter traffic (Zscaler or similar) must allow the new domains.
What not to do#
- Do not Reset the computer first. It restores the last saved snapshot and can lose recent work.
- Do not sign in with a personal account when your company requires SSO.
- Do not delete Bots or buy a second plan because Bots look missing.
Our full Windows sign-in guide includes the Windows 0.44.0 thread and more cases.
Frequently asked questions#
Why does sign-in never complete?#
Keep the app open while the browser sign-in runs, confirm the browser reports success, then return to the app. From 0.75.2 the wait is up to 20 minutes. Use your organization's SSO login if you have one.
Why am I signed in but replies fail with an authentication error?#
The Bot's computer often needs an update. Try Settings, Computer, Update Bot's Computer, which keeps Bots and data, before anything destructive.
Does Legacy Privacy Mode block Grok Bot?#
Yes. Grok Bot requires data storage and does not support Legacy Privacy Mode. Change the Cursor data setting, or ask your admin on a team account.