Getting-started troubleshooting: login loops, install failures, won't open
If you're searching "Grok Bot won't log in," you're most likely stuck in one of three places: the browser shows login succeeded but the app doesn't respond; it installed, but on opening you're blocked by a full-screen "Update required"; or the app simply won't open. This lesson tackles each pitfall you'll hit in the getting-started phase one by one — first locate the issue with a 60-second quick check, then find the fix by your error message, all in 10 minutes. Every fix comes from x.ai's official troubleshooting docs and the official login-domain announcement.
First, remember one fact that can save you half an hour: reinstalling the app usually doesn't fix login problems (the official wording). So don't rush to delete the software — read on.
What you'll be able to do after this lesson
- Use the 60-second quick check to tell apart: a service outage, an outdated version, or a login-session problem
- Match "Grok Bot won't log in" to your case: the official 5-step self-check for a stuck sign-in, clearing cookies + incognito window + waiting 30–60 minutes for login loops, and domain allowlisting on corporate networks
- Know why the "Update required" full screen appears and what to click when you see it; on Linux, update with the
apt/dnfcommands - Tell apart "just wait" (Setting up your Grok Bot…) from "needs fixing" (startup freeze)
- Contact support with your version number, the exact error text, and the request ID, and explain everything in one go
Where you're stuck right now
- The browser clearly shows Cursor login succeeded, but the app sits on the welcome screen and repeated clicks do nothing
- It installed, but on opening the whole window is covered by "Update required," and clicking update fails to download
- The app spins and freezes on open, and you can't tell whether it's your computer or the service is down
When to use this approach
When you need to:
- Unstick the step where you're blocked in 1.3 Install or 1.3b alternative installation methods
- Go through the official fixes before reinstalling the app — the docs explicitly say reinstalling usually doesn't fix login problems
And you don't want to:
- Reinstall or Reset at the first error — neither usually fixes login problems, neither fixes service problems, and Reset may also lose the latest unsaved changes on your cloud computer
- Waste half a day because you can't tell "just wait it out" from "you must fix it"
🎒 Preparation before you start
- Have gone through the 1.3 Install flow — it doesn't matter which step you're stuck on, that's exactly what this lesson unblocks
- Know your account situation: direct Cursor account login, corporate SSO, a Grok Business seat, or SuperGrok / X Premium+ that needs linking
- Linux users: first tell whether you're on the deb family (Debian / Ubuntu) or the rpm family (Fedora, etc.)
- Corporate network users: know who manages the firewall / proxy (you may need IT to allowlist domains)
Core idea
Layer first, then match your case. Getting-started problems fall into one of three layers, and the first response differs for each:
| Layer | Typical symptom | First response |
|---|---|---|
| Service | Status page shows an incident; Bot suddenly stops replying | Wait for the official fix; don't reinstall or Reset |
| Account / login | Login loops, Legacy Privacy Mode errors, allowlist blocks | Follow the official login troubleshooting steps |
| Local app | Startup freeze, outdated version, failed update | Fully quit and reopen → update the version |
Two facts to remember first:
- A full restart fixes most issues: Official guidance says to start with the least destructive step—use Quit from the menu bar on Mac to fully quit the app (not just closing the window), then reopen and try again.
- Reinstalling usually does not fix sign-in issues: For some session and account-linking failures (including sign-in loops), as well as access blocks caused by failed phone verification, the official guidance states clearly that these cannot be fixed on the user side—you can only contact support with evidence.
First-pass troubleshooting: a 60-second quick check
Go through these four things in order, and you can usually pinpoint which layer the problem is in:
# 1. 完整退出再重开——官方:大多数问题这样就好了
# macOS 用菜单栏的 Quit,不是只关窗口
# 2. 服务有没有故障?浏览器打开状态页,找 Grok Bot 一行
# https://status.cursor.com
# 3. 版本是不是太旧(超过 14 天且已有新版会被强制更新)?查官方发布源当前版本
curl -s https://api2.cursor.sh/updates/api/download/stable/darwin-arm64/sand
# {platform} 换成你的平台:darwin-x64 / win32-x64-user / win32-arm64-user /
# linux-x64 / linux-arm64,再对照 app 内 Support → About 的版本号
# 4. 登录卡住:浏览器里确认显示 Cursor 登录成功,app 保持打开,手动切回去What you should see: on the status page, the Grok Bot row shows no ongoing incidents; curl returns JSON containing version; the app can fully quit and reopen. Whichever step breaks, go to the corresponding section below.
Common issues troubleshooting
Can't sign in: sign-in hangs and account issues
Sign-in hangs and never completes: the browser shows success but the app does nothing
Cause: Sign-in authentication completes in the browser, and the app has to wait for the result—if the app is closed midway, the browser didn't actually sign in successfully, or the account doesn't have Grok Bot access, it will hang at this step.
Fix (official 5 steps, in order):
- While authentication is running in the browser, keep the Grok Bot open—don't minimize or close it.
- Confirm the browser shows Cursor sign-in successful.
- If the app doesn't automatically come back to the foreground, switch back to it manually.
- Still not working: on the welcome screen, click Sign in again; if you've already been in the app, use Sign In with Cursor in Settings.
- Confirm your account has Grok Bot access—to see which plans include Grok Bot, check 1.2 Subscriptions and Pricing.
Two account types—don't go through the wrong door:
| Your situation | Pitfalls to avoid |
|---|---|
| Company uses SSO | Complete the organization's sign-in flow, and don't switch to a different personal account to sign in |
| Self-serve Grok Business seat | In the browser choose Sign in with Grok, using the Grok account that holds the seat |
What you should see: after the browser shows Cursor sign-in successful, the app returns to the foreground and enters the intro and the first Bot screen.
Sign-in loop: the browser keeps opening, but you just can't get into the app
Cause: Something went wrong with the session or account linking—stale cookies and cache, an outdated desktop app version, or a freshly refreshed session that hasn't taken effect yet. The official guidance states clearly: reinstalling the app usually doesn't help.
Fix (official 4 moves, from fastest to slowest):
- Update the desktop app to the latest version, then sign out and sign back in.
- Clear browser cache and cookies for cursor.com and x.ai, then sign in again in an incognito / private window.
- On the desktop, sign in once more to x.ai/bot with the same Cursor account; if the loop is happening on your phone, sign in successfully on the desktop first.
- If the error just appeared: wait 30–60 minutes and try again—some authentication errors go away on their own as the session refreshes.
⚠️ Two situations you can't fix yourself—go straight to support
Some session and account-linking failures (including sign-in loops), as well as access blocks caused by failed phone verification, officially cannot be fixed on the user side. Email support@x.ai and include: the exact error text, the steps you've already tried, and whether the issue occurred during the SuperGrok / X Premium+ linking process; for phone-verification blocks, attach a screenshot of the blocked screen.
What you should see: after clearing cookies + using an incognito window, the browser signs in successfully on the first try and the app enters normally.
The error mentions Legacy Privacy Mode
Cause: It's not a broken installation—your Cursor account is using a data mode that does not allow Grok Bot's required cloud data storage. Grok Bot needs cloud data storage, and Legacy Privacy Mode is not supported.
Fix:
- Switch your Cursor account's data setting to Privacy Mode. Official wording: Legacy accounts will be prompted to switch before starting—just follow the prompt.
- If you can't change it yourself, ask your organization admin to update the account's data setting; for team accounts, the team admin changes the team's privacy setting.
What you should see: after switching, reopen the Grok Bot—the error no longer appears and you enter the first Bot normally.
Can't sign in on a corporate network: the allowlist doesn't include the new sign-in domains
Cause: Starting 2026-10-30, the Cursor sign-in page migrated from authenticator.cursor.sh to accounts.spacex.ai and accounts.x.ai. If the corporate firewall / proxy (e.g., Zscaler) allowlist wasn't updated, these two domains get blocked and the sign-in page won't load.
Fix:
- Have IT add the following domains to the allowlist (official advice: use wildcards where possible, so you don't have to change it again later):
*.spacex.ai # covers accounts.spacex.ai and related auth hosts
*.x.ai # covers accounts.x.ai, auth.x.ai, and related auth hosts
*.grok.com # covers auth.grok.com and grok.com
*.grokusercontent.com
*.grokipedia.com- If policy doesn't allow wildcards, at minimum allow these hosts:
accounts.x.ai,accounts.spacex.ai,auth.x.ai,auth.grok.com,auth.grokusercontent.com,auth.grokipedia.com,grok.com. - Cursor's own domains still need to be allowed as before:
*.cursor.sh,*.cursor-cdn.com,*.cursorapi.com,*.cursorvm.com. - After adding them, retry sign-in from
accounts.spacex.ai,accounts.x.ai, or your existing IdP.
What you should see: the browser can open the new sign-in page and complete authentication, and the app enters normally.
💡 Also check internal bookmarks
Update any links pointing to authenticator.cursor.sh in team favorites or internal docs to accounts.spacex.ai and accounts.x.ai. Existing login sessions are unaffected—this is not a forced logout.
Installation failures and failed updates
"Update required"
Cause: Grok Bot's forced update policy—if the version is more than 14 days old and a newer version exists, the app covers the window with a full-screen "Update required" notice saying your version is no longer supported. Auto-update is on by default, but it only installs automatically when "the screen is locked or the screensaver is on + the computer has been idle for at least 10 minutes + Grok Bot is not busy"—if these conditions are never met, the update never gets installed, until the 14-day forced update kicks in.
Fix:
- Click Update, wait for the download to finish, then click Restart to update——Bots keep running in the cloud during the update, so they won't go offline.
- Download failed: click Try again, or Download the latest version to download and install it yourself.
Linux users: the full screen may show a command to run—click Copy command, run it in a terminal, then restart Grok Bot:
# Debian / Ubuntu(deb 安装)
sudo apt update && sudo apt install --only-upgrade grok-bot
# Fedora 或其他 RPM 系统
sudo dnf upgrade --refresh grok-botIf the screen tells you to instead download and install the latest package, do so, then restart Grok Bot after installation. On mobile, tap Update Grok Bot to get the new version from the App Store / Google Play.
You should see: after the update installs and the app restarts, the full screen disappears; the version number in the account menu Support → About shows the new version.
Update finished but still on the old version
Cause: the app closed for the update, but the new version was never actually installed—the update didn't complete, or the downloaded installer didn't overwrite the old version.
Fix (official order):
- Check the current version number in the account menu Support → About.
- Fully quit Grok Bot (on Mac, use Quit in the menu bar), then reopen it.
- Settings → Updates → Check for Updates; if there's an update, click Restart to Update.
- Version still unchanged: download the latest version from cursor.com/dashboard/bot and install it directly over the current app. Bots and chats are tied to your account, so reinstalling won't lose them.
- On Linux, run the two
apt/dnfupdate commands above. - If the old version keeps coming back: contact support with your version number and platform.
You should see: Support → About shows the new version number, and "Update required" no longer appears.
Installer doesn't match: format, architecture, and official sources
Cause: the download came from the wrong place (third-party "installers" of unknown origin), or the format doesn't match your system—for example, your company's management tool requires MSI / PKG, but the official release doesn't ship those formats at all.
Fix:
- Download only from the three official sources: the cursor.com/dashboard/bot's Download Grok Bot row, x.ai/bot, or a link from your administrator.
- Verify the format and architecture:
| Platform | Architecture | Official installer |
|---|---|---|
| macOS | Apple silicon、Intel | .dmg |
| Windows | x64、Arm64 | Setup .exe |
| Linux | x64、Arm64 | .deb、.rpm、AppImage |
- Management tool absolutely requires MSI / PKG? Official guidance: wrap the
.dmgor.exepackage in the format your management tool requires. - For pinning a version, silent installation on Windows, or installing via a Linux package manager—see 1.3b Alternative installation methods.
You should see: the installer downloads normally, the format matches your system, and Grok Bot appears in the Start menu / launcher after installation.
Won't open and stuck at startup
The app freezes at launch with no response at all
Cause: the app process didn't fully exit before launching again, or a local process is stuck.
Fix:
- Fully quit and reopen—on Mac, use Quit in the menu bar; don't just close the window.
- If it freezes on every launch: contact support, and include yourplatform and Grok Bot version (Support → About → Copy version info copies it in one click).
You should see: after fully quitting and reopening, the app shows the welcome screen or main interface normally.
"Setting up your Grok Bot…"
Cause: it's not a malfunction—first-time setup and cloud computer updates naturally take a few minutes, and a slow update may be downloading a large image or transferring data. As long as the progress is still moving, it isn't stuck.
Fix:
- Keep the app open and wait for the progress to finish; on mobile, the home screen shows Starting your computer…—wait there too.
- During a slow update you may see Update still running or Taking longer than usual—the official advice is to choose Keep waiting, unless it truly looks frozen.
- If the progress is still changing: keep waiting. If it fails or the progress stops: follow the recovery order for "can't connect to the cloud computer," see Cloud computer maintenance.
- Only if the update truly looks frozen and the app offers Recover computer should you use Recover; if it's not offered, keep waiting.
You should see: after a few minutes the progress completes and you enter the chat window with your first Bot.
Suspect the service is down: check the status page first
Cause: the appdoes not show service status—when there's a server-side incident, every anomaly you see in the app looks like "something broke on my end."
Fix:
- Open status.cursor.com in your browser and look for the Grok Bot line; you can subscribe to updates there.
- There is an incident: wait for the official fix, then resend your message. Do not reset the cloud computer or reinstall the app — the officials have explicitly said neither fixes service problems, and resetting may also lose your latest unsaved changes.
You should see: the Grok Bot line shows normal (no ongoing incident); if there is an incident, once it is resolved your messages will receive replies normally.
Still not working?
**Gather evidence first, then ask. ** A feedback report with complete evidence can save several rounds of back-and-forth:
| What to collect | How to get it |
|---|---|
| Account email | The email on your Grok Bot account |
| Version + platform | Account menu Support → About → Copy version info (version, release channel, and OS copied in one go) |
| What you were trying to do, Bot / routine name | Which Bot or routine the issue involves and what you were doing at the time |
| Exact error text / screenshot | Copy it verbatim, or screenshot the error and the plan view |
| request ID / conversation ID | Right-click the message → Copy request ID; if it is not in the menu, that message has no request ID — include the error text and screenshots instead |
| Approximate time and time zone | When the error occurred |
| What you have tried | Retrying, restarting the app, updating the cloud computer… list them all |
Do not include: passwords, one-time verification codes, private keys, or any secret values.
Where to send feedback:
| Channel | Entry point |
|---|---|
| Inside the desktop app | Account menu Support → Send Feedback (if the issue is in the current conversation, check Include current conversation ID; on Mac you can also use the menu bar Help → Send Feedback) |
| Mobile app | Settings → Send Feedback (if the issue involves a Bot, select it and keep Include Bot ID enabled) |
| support@x.ai, sent from the email on your Grok Bot account; billing and cancellation issues also go here |
For login-related issues, include the materials required by the tip box in the "Login loop" section; for phone verification blocks, you must attach a screenshot of the blocked screen.
For errors after getting started (Bot failed to respond, Model provider is overloaded, Couldn't Reach Grok Bot's Computer…), look them up quickly by exact error text: Error Quick Reference.
Checkpoint ✅
- 60-second quick check in four steps: I passed it and know which layer the problem is in
- Login stuck: I followed the official 5 steps; for the login loop I tried clearing cookies + incognito window + waiting 30–60 minutes, and did not waste time reinstalling
- "Update required": I know to click Update → Restart to update; on Linux I will use the
apt/dnfcommands - "Setting up your Grok Bot…": I know this is normal waiting, and Keep waiting is the safest option
- Before seeking support I will bring: version + platform + exact error text + request ID + steps already tried
Lesson Summary
✅ Triage getting-started issues by layer first: server-side (check the status page, wait), account / login (official troubleshooting steps), local app (fully quit and reopen → update).
✅ Core fixes for failing to log in to Grok Bot: if sign-in is stuck, follow the 5-step self-check; for the login loop, clear cookies for cursor.com and x.ai, switch to an incognito window, sign in to x.ai/bot on the desktop, and wait 30–60 minutes — reinstalling usually does not help.
✅ "Update required" = your version is more than 14 days old and a newer version exists; Update → Restart to update, Bots keep running in the cloud as usual; on Linux use apt / dnf.
✅ Bring complete evidence when seeking support: version + platform + exact error text + request ID + steps already tried; do not include passwords or verification codes.
Key information recap:
| Symptom | First response |
|---|---|
| Browser login succeeds but the app does nothing | Keep the app open, switch back to it manually, then click Sign in again |
| Login loop | Clear cookies + incognito window → sign in to x.ai/bot on the desktop → wait 30–60 minutes |
| Error mentions Legacy Privacy Mode | Switch to Privacy Mode; for teams, contact the admin |
| Cannot log in on a corporate network | Have IT allow *.spacex.ai and *.x.ai, the new sign-in domains |
| "Update required" full screen | Update → Restart to update (Linux: apt / dnf) |
| Startup hangs | Fully quit and reopen (Mac menu bar Quit) |
| "Setting up your Grok Bot…" | Wait for the progress to finish, Keep waiting |
| Suspect the service is down | Check the Grok Bot line on status.cursor.com |
Next Lesson Preview
The getting-started pitfalls are cleared. The next lesson starts the real work: Your First Bot: Create It, Assign Work, and Watch It Work on the Cloud Computer.
You will learn:
- How to use the first Bot automatically created after login
- How to assign your Bot its first task and watch it work in the computer preview
- When you should create another Bot with a more focused responsibility