Something isn’t right? Start with the least destructive step, then find your exact error message below. Each card links to a fix you can follow step by step. Most problems clear with a full restart, so start there. The steps that can lose recent changes come last.
Free prompts: Every prompt on this site is free to copy and paste into Grok Bot. Browse the Free Grok Bot prompts library.
First, try this
- Fully quit Grok Bot. On Mac, choose Quit from the menu bar. Closing the window isn’t enough.
- Reopen it and try again.
- Check if Grok Bot is down. Open status.cursor.com and look at the Grok Bot row. The app doesn’t show service status.
- If there’s an incident, wait for it to be fixed, then send your message again. Don’t Reset the computer or reinstall the app during an incident.
Your Bots keep running in the cloud even when the app on your desktop or phone is disconnected.
Find your error message
Match the words on your screen. Each row links to the fix on this page.
| You see | What it means | Fix |
|---|---|---|
| Reconnecting or Couldn’t Reach Grok Bot’s Computer | The app can’t reach your Bots’ cloud computer. | Computer won’t connect |
| Setting up your Grok Bot…, Updating Grok Bot’s Computer or, on the phone, Starting your computer… | Setup or an update is running. It can take several minutes. | Wait while progress changes. See Computer won’t connect. |
| Update still running or Taking longer than usual | A slow update. | Keep waiting is the safe choice unless it looks stuck. |
| An agent couldn’t pause in time, so the computer was not updated | A Bot was busy. | Let that Bot finish, then choose Update again. |
| Bot failed to respond or Model provider is overloaded | The reply didn’t come through. | Bot stopped replying |
| A message that you hit your usage limit | Your weekly usage is used up. | Bot stopped replying |
| Update required | Your app version is more than 14 days old and a newer one is out. | Update required |
| New update available | An app update is ready. | Choose Install, then Restart to update. |
| Expired on an approval card | Nobody answered a card from background work in time. | Routines didn’t run |
| Needs auth, Disconnected or Disabled by team admin in Connect apps | An app isn’t signed in, or your admin turned it off. | Apps and logins |
| Action needed on the Computer card | A site needs you to sign in. | Apps and logins |
| “Local tools are turned off. The user has set local tool access to Never.” | A known issue on Cursor’s side, even when your setting allows local tools. | Your setting is correct. Restarting, reinstalling or changing it won’t clear the error. |
| An error about Legacy Privacy Mode | Your account’s data mode doesn’t allow Grok Bot’s storage. | Update the Cursor account data setting, or ask your organization admin. |
Automation run rate limit exceeded | A routine ran too often in one hour. | Routines didn’t run |
Decision tree
- Is there an incident on status.cursor.com? Yes: wait, then retry. No: go on.
- Does the computer say Reconnecting, or that it can’t be reached? Yes: Computer won’t connect.
- Is the computer fine, but the Bot isn’t replying? Yes: Bot stopped replying.
- Did a routine not run at its time? Yes: Routines didn’t run.
- Is it an app, a website login or an update? Yes: Apps and logins.
- None of these? Before you contact support.
Computer won’t connect
Your Bots and saved conversations aren’t lost while the computer can’t be reached. Chats are stored separately from the computer. Work through these in order and stop when it’s fixed:
- If you see Reconnecting or Couldn’t Reach Grok Bot’s Computer, wait, then choose Retry. Don’t Reset now.
- Fully quit Grok Bot and reopen it.
- If an update is offered, open Settings → Computer and choose Update Bot’s Computer.
- If it still can’t reconnect, choose Recover computer. The confirmation calls it Recover Grok Bot’s Computer.
- Use Reset only after all of the above. On the phone: Settings → Bot → Bot Computer → Reset Computer. Updating and recovering need the desktop app.
Good to know:
- Recovering usually takes a few minutes. You can choose Continue in Background.
- Don’t start a second Update or Reset while one is running.
- If Recover or Reset fails, choose Retry Recovery or Retry Reset once. Then stop and contact support.
- Recover computer and Reset keep your saved Bots, files and logins. They remove installed apps and packages, interrupt running work, and can lose very recent changes if the computer couldn’t be reached to save them.
- If Bots recently disappeared, contact support before you use Recover or Reset.
Bot stopped replying
- See Bot failed to respond or Model provider is overloaded? Wait a moment and send the message again.
- Still nothing? Fully quit and reopen Grok Bot.
- Is the computer Reconnecting? A Bot can’t finish a reply while the computer can’t be reached. See Computer won’t connect.
- Does it look stuck? Check the status in the sidebar and the chat. Open the computer to see if it’s waiting on a page. Look for a question, approval, login, CAPTCHA or secret request.
- Wrong approach? Send a short message to redirect it, or send “Stop now” if the work should end.
- Did it say you hit your usage limit? It isn’t broken. Your weekly usage is used up and resets each week. To keep going now, add prepaid credit (The X Subscription), turn on on-demand usage (older Cursor plans) or move to a bigger plan. See Grok Bot pricing.
- Same prompt fails on a fresh run with an error? Copy the request ID from the message and report a bug.
Chats or Bots look missing? They’re usually not deleted. Fully quit and reopen. Check the phone app. Open Hidden Bots in the sidebar (Show Hidden Bots on the phone). Make sure you’re in the same account. Don’t use Recover or Reset to look for them.
Routines didn’t run
Open the routine and check:
- It’s on, not Paused.
- When to run shows the schedule and time zone you expect.
- The Bot that owns it still exists.
- The apps it needs are still signed in.
- The computer can reach the site or service it uses.
- Your usage or account access isn’t paused.
Then look at the recent run history for a failure. For an event-triggered routine, check that the channel, repository or matching rule is still right.
- Want to try it once? If the routine shows Test on desktop, use it with safe input only. A test can do real things. If there’s no Test, ask the Bot to do the same work once in chat.
Automation run rate limit exceeded? A routine can run up to 200 times an hour, and all your routines together up to 300. The run isn’t retried for you.- Approval card says Expired? A card from a routine expires after about 30 minutes, and the action doesn’t run. Turn on notifications for Bots that run routines, and ask the Bot to try again.
- Not paused, no error, and no run for 24 hours or more? Report a bug with the Bot name and routine details.
More: scheduled routines and webhook routines.
Apps and logins
An app won’t connect or authenticate
- Open Connect apps from the sidebar. Check the app is listed as installed.
- Open the app and choose Authenticate (Authorize on the phone).
- Finish signing in, with the right account, within about 10 minutes.
- Go back to Grok Bot and try the task again.
On a connect card: Reopen brings the sign-in page back. Retry starts again. If the button changes to Reconnect, choose it. Added means installed, not signed in. If it still fails, choose Remove, add the app again and sign in. See reconnect an app that stopped working.
A website keeps asking you to log in
- Choose Take over and sign in yourself.
- Complete the two-factor code or CAPTCHA.
- Wait for the signed-in page to load, then choose I’m done.
- Tell the Bot to continue.
Never paste a password or code into ordinary chat. Fingerprint, Face ID, Windows Hello and passkeys on your own device don’t work on the Bot’s computer. On Mac and Windows, you can turn on Use hardware security keys in Settings → General, under Security Key.
A website times out or won’t connect
Some sites drop connections from the Bot’s computer. Update, Recover and Reset don’t change this. In Settings → Computer → Your computer, you can turn on Route traffic through this computer or Execution on this computer.
Sign-in to Grok Bot doesn’t finish
- Keep Grok Bot open while you sign in in the browser.
- Go back to the app yourself if it doesn’t come to the front.
- Choose Sign in again, or Sign In with Cursor in Settings.
- Stuck in a loop? Update the app, sign out and in, and clear cookies for cursor.com and x.ai.
- Started recently? Wait 30 to 60 minutes and try again.
<a id=”update-required”></a>Update required
Choose Update, wait for the download, then choose Restart to update. If the download fails, choose Try again or Download the latest version. On Linux, choose Copy command and run it in a terminal:
- Debian or Ubuntu:
sudo apt update && sudo apt install --only-upgrade grok-bot - Fedora or other RPM systems:
sudo dnf upgrade --refresh grok-bot
On the phone, choose Update Grok Bot. To reinstall or update by hand, see reinstall or update the app.
Before you contact support
- Send feedback from the app. Desktop: account menu → Support → Send Feedback. Mac: also Help → Send Feedback in the menu bar. Keep Include current conversation ID on if the problem is in the open chat. Phone: Settings → Send Feedback, and keep Include Bot ID on for a problem with one Bot.
- Or email support@x.ai from the email on your Grok Bot account. Billing and cancelling questions go there too.
- Collect: your account email, Grok Bot version and platform (Support → About → Copy version info), what you were doing and the Bot or routine name, the exact error or a screenshot, the time and time zone, the request ID (Copy request ID) and what you already tried.
- Never include passwords, one-time codes, private keys or secret values.
Every page in this section
How to fix 'Can't reach your computer'
/help/cant-reach-your-computer/How to fix 'Reconnecting to your computer'
/help/reconnecting/How to fix 'Not supported on this Mac'
/help/not-supported-on-this-mac/How to fix the 'Restart to update' loop
/help/restart-to-update-loop/How to fix a Bot that's not responding
/help/not-responding/How to fix 'Limit reached'
/help/limit-reached/How to fix 'Routine sync failed'
/help/routine-sync-failed/How to fix routines that don't run
/help/routines-not-running/How to make Grok Bot faster when it's slow
/help/slow/How to fix computer and login problems
/help/logins-reset/How to set your privacy and training options
/help/privacy/How to fix the Shopify connector when it's not working
/help/shopify-connector/
FAQ
Is Grok Bot down?
Check the Grok Bot row on status.cursor.com. The app doesn’t show service status.
Will Reset delete my Bots or chats?
No. Conversations are stored outside the computer, so they survive even a reset. Recover and Reset keep your saved Bots, files and logins. They remove installed apps and packages, and can lose very recent changes if the computer couldn’t be reached.
What does the usage limit message mean?
Your weekly usage is used up. It resets each week. You can add credit or move to a bigger plan. See Grok Bot pricing.
How do I report a bug?
Use Support → Send Feedback in the app, and include the request ID if the message has one.
Checked against these pages on Nov 4, 2026. Nothing on this page has been tested yet.