# Grok Bot not responding or 'failed to respond': fixes in order

> Bots gone silent, one Bot that always fails, a computer shown offline. Live status, the official recovery order, the October incidents, and when not to reset.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-not-responding
- Sources checked: 2026-10-30
- Evidence: Official troubleshooting rechecked October 25, 2026 (last updated by Cursor October 22) · Grok Bot changelog through 0.78.1 (October 27) read October 29, 2026 · status.x.ai incident history checked October 29 · forum staff replies checked October 30, 2026 · fixes are as described in release notes, not tested by us · forum reports attributed, not reproduced. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## First, work out which of three things is wrong

A silent Bot has one of three causes: the Bot is waiting on you, the shared computer is unhealthy, or the service is degraded. The symptoms look identical from the chat, so open the computer view before touching anything. The official docs say to check the sidebar and conversation status, watch the computer, and look for a question, approval, login page, CAPTCHA, or secret request the Bot is stuck behind.

The troubleshooting page also flags a fourth, easy-to-miss cause: a Bot can look stuck simply because weekly usage is exhausted and an on-demand spending limit has been reached. Check usage and billing before assuming the computer is unhealthy. Until recently the app could stay completely silent in that case: a Cursor staff member wrote in a September forum thread that a used-up allowance made every message fail before the Bot could reply, with no usage limit reached notice, and on October 30 posted in the same thread (357 views) that this was fixed, so after updating Grok Bot to the latest version you should see a clear message that the limit has been reached. If Bots go silent again without one, staff asked for your Grok Bot version and the time it happened, with your time zone.

If the Bot is waiting, answer it or send a redirect. If the computer view will not load or shows setting up or unreachable, follow the recovery order below. If several Bots died at once and the forum shows a fresh degradation thread, stop and wait.

The panel at the top of this page shows live Grok Bot status from status.x.ai, where Cursor's status page moved on October 26. Our guide [Is Grok Bot down?](https://www.grokbotwiki.com/guides/is-grok-bot-down) keeps every incident since September with its times, so you can tell an outage from a problem on your account.

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/overview, https://forum.cursor.com/t/grok-bot-all-bots-completely-unresponsive-after-update-agent-computer-recovery-and-reset/172118

## Update the app first (fixes in 0.71.2 to 0.78.1)

Several symptoms in this guide have official fixes in recent releases, so check Settings → Updates → Check for Updates before any recovery step. The troubleshooting page notes that the app and the Bot's computer update separately, and that updating the desktop app does not reset the cloud computer. These are the fixes as the release notes describe them; we have not tested them, and forum reports show some symptoms still turning up for some accounts.

| Symptom | Fixed in | What the release notes say |
| --- | --- | --- |
| "Couldn't refresh" or connection errors while the Bot's computer sleeps | 0.71.2 (October 14) | The app says Your computer is asleep instead |
| A separate Wake button, or waiting behind a full-window Setting up Grok Bot's computer screen | 0.71.2 | Clicking the Computer is asleep preview wakes it in place, and the app opens while the computer is still starting |
| The Bot keeps retrying as if a computer that failed to wake were still starting | 0.71.2 | The Bot says the computer couldn't start |
| A working Bot drops when its computer updates | 0.71.2 | It reconnects to the new computer and keeps going |
| Your own Mac or PC unreachable after a Wi-Fi, VPN or network change | 0.71.2 | Bots can run tasks on it right away; commands also keep going through brief connection stalls |
| Bots slow to notice that your computer went to sleep | 0.71.2 | A sleeping computer counts as disconnected within two minutes, and Bots say so right away |
| Connector calls failing after one minute | 0.71.2 | They wait up to two minutes, longer while the connector reports progress |
| A generic error when a safety check blocks a reply | 0.71.2 | The chat shows Blocked by a safety check and Try a different message |
| A Bot silent after you hand its computer back with I'm done or Skip | 0.71.2 | The Bot posts its answer |
| The desktop app does not load behind a corporate proxy | 0.75.2 (October 22) | The app connects directly unless you have turned on a system proxy |
| Connect Apps shows Couldn't refresh | 0.75.2 | It waits longer for your plugins |
| A message silently fails to save | 0.75.2 | The app says whether your computer is out of disk space; since 0.71.2 a Bot whose computer runs low on disk also tells you once and names the biggest files |
| Errors after resetting a chat whose first message was blocked | 0.75.5 (October 23) | New messages get replies |
| Your own Mac or PC stays disconnected after the Bot's computer wakes, with Route traffic through this computer on | 0.75.8 (October 24) | For most accounts the connection comes back as soon as the Bot's computer wakes |
| A connector shows Connected while the Bot says it is signed out | 0.75.8 (October 24), on 0.71.2 or later | The app shows Authenticate when a connector's sign-in has expired; sign in again instead of resetting |
| No status line after you send, so a quick reply looks like silence | 0.75.8 (October 24) | A Bot's status line shows up right after you send, even for quick replies |
| A Bot in Slack goes quiet when a safety check blocks its reply | 0.75.8 (October 24) | The Bot says so in Slack and suggests trying a different message |
| Turns end on Couldn't Reach Grok Bot's Computer, especially during heavy work | 0.77.0 (October 26) | The Bot's computer stays up when memory runs low and recovers faster after a crash, so fewer turns end that way |
| A command on the Bot's computer hangs because it is waiting for input, such as a package install prompt | 0.77.0 | Such commands finish instead of hanging |
| A message shows Not delivered yet although the server accepted it, or the computer view stays on Waking up | 0.77.0 | An accepted message stays delivered and Resend sends one that is not; the computer view leaves Waking up once the screen is ready |
| An update interrupts a working Bot, or Usage & Billing goes blank when usage cannot load | 0.77.0 | Grok Bot offers Stop and Update when an update is ready while a Bot is working; Usage & Billing keeps the last reading with Try again |
| With Route traffic through this computer on, plain http pages fail, or the Bot does not say your computer went offline | 0.77.0 | Plain http pages load, and the Bot says when your computer goes offline |
| The computer card flips off Asleep during a brief background wake, or does not show Waking up when you wake it | 0.78.1 (October 27) | The card stays on Asleep during brief background wakes and shows Waking up… as soon as you wake it |
| Update installs a different version than the one you clicked, or stays on Restarting… with no explanation when a restart is refused | 0.78.1 | Update installs the version you clicked, an open Update ready dialog switches to the newest finished download, and when a restart is refused every Update button says why |
| Task lists and thread names stay stale after the app reconnects | 0.78.1 | They refresh after the app reconnects |
| With Route traffic through this computer on, Settings does not say the Bot's computer is asleep, or pages fail as soon as one other host on them is refused | 0.78.1 | Settings says when the Bot's computer is asleep and that routing reconnects when it wakes; pages no longer fail right away when only another host on them is refused |
| Approved browser actions fail on some Bot computers when the page has not changed | 0.78.1 | They no longer fail |
| Reset or Recover restores an older backup when the computer has been refusing saves | 0.78.1 | Reset and Recover keep the current disk instead of restoring an older backup |

Sources: https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.75.8, https://x.ai/changelog/bot#v0.77.0, https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/troubleshooting

## Error messages and what they usually mean

These are messages quoted in the official docs, Cursor's billing page, or forum reports where Cursor staff replied. The cause column is the most common explanation in those sources, not a diagnosis of your account.

| What you see | Likely cause | What to do |
| --- | --- | --- |
| "Bot failed to respond" on one or every Bot | The shared computer is stuck, or the service is degraded; it hits every Bot on the account at once. Since 0.63.0, a used-up plan shows the usage limit notice instead | Check the live status first. After the October 3 and 6 incidents, staff said to resend the message rather than reset; otherwise follow the recovery order below and leave Reset until last |
| "Bot failed to respond" on one Bot only, even after a reset, while other Bots reply | Staff traced October cases to the model provider's safety filter refusing that Bot's conversation history, for example security or biology research content; the app shows a generic error | Use another or a new Bot for new work; do not ask other Bots to read or continue that chat, and do not delete the stuck Bot. On 0.71.2 or later a blocked reply reads Blocked by a safety check |
| Your messages show "Failed to send" | Reported during the September 16 to 18 incidents and after long tool waits | Restart the app, send "Stop now" to the stuck Bot, and check status before resetting |
| Can't reach your computer (unreachable-computer state) | The cloud computer is temporarily unreachable; on September 7 Cursor's status page said Recover or Reset could also fail | Retry, restart, then Recover computer; if that is not offered, Settings → Computer → Update Bot's Computer |
| "Starting your computer" or "Updating your computer" does not finish | Initial setup or an image update, which can take several minutes | Wait while progress changes; if it stops, Retry, restart, check for an app update, then Update Bot's Computer under Settings → Computer |
| "Starting desktop" with "Can't reach Grok Bot's screen", or SEND AFTER RECONNECT on mobile | On October 5 Cursor staff said a recent change left some computers without enough storage to finish starting; they fixed the reported accounts the same day | Fully quit and reopen the app on every device; if it persists, post your version and time in the forum rather than resetting |
| Shell or terminal commands hang while the desktop still renders | A server-side fault Cursor staff were fixing account by account in early October; Update and Reset did not clear it. In an October 21 reply staff also pointed to the computer's shell startup files, since every Shell command starts a login shell first | Hold off on Update, Recover and Reset, since a Reset restores the same files; have a Bot open its startup files with its file reading tool, not Shell, then report what it finds in the forum; the section on Shell commands below has the details |
| Mail, database, SSH or FTP connections from the computer time out | Since October 1 some computers can only make outbound HTTPS connections; staff called it unintended, and more accounts reported it after service-side refreshes on October 7 and 8. New reports were still arriving on October 14 with no fix posted | Use HTTPS endpoints, or clone git repositories over HTTPS; resetting does not help. Users report that connecting by a server's real IPv4 address, looked up over DNS-over-HTTPS, works for most ports, which Cursor has not endorsed. Users were still reporting blocked mail ports on October 22, and no staff reply in the thread since October 14 announced a fix (checked October 25) |
| Can't reach the Bot's screen on a new account, and deleting a Bot or Update does nothing | The computer did not finish its very first startup (staff, October 7); chat still works. On October 12 staff said computers in that group were coming back up, and that one similar case was instead the desktop app connecting through a VPN or proxy route Cursor's servers did not accept between October 10 and 12, while the phone app worked | Fully quit and reopen the app. If you use a VPN or proxy on that computer, try without it. Do not keep pressing Update or Reset; post in the forum thread if it persists |
| The app says Your computer is asleep, or, on versions before 0.71.2, Couldn't refresh or a connection error | An idle computer; since the October 11 release (0.69.0 to 0.70.2) switching chats or focusing the window no longer wakes it, while opening a file does. 0.71.2 replaced the misleading errors with the asleep message | Update to 0.71.2 or later and click the Computer is asleep preview, which wakes it in place and replaced the Wake button; do not Recover or Reset. Publishing, sharing or deleting a Bot works while the computer sleeps, and since 0.71.2 a voice call from your phone also wakes it |
| Your Bots are gone, or the app says your plan does not include Grok Bot, after switching to The X Subscription | Cursor staff said on October 21 that the switch can leave your Bots on one account and your plan on another; the Bots are not deleted. Users were still reporting it on October 25 | Do not reset the Bot's computer, delete anything or buy a second subscription; see [the account-switch steps](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows) |
| The app keeps crashing, or the window is blank after an update | Fixed in the October 11 release: a crash loop now offers to reload or quit, and a blank window after an update relaunches | Choose reload; if you are on an older version, install the latest from x.ai/bot |
| A turn stops and says the model is not available in your region | Since the October 11 release the turn stops with an explanation and Bots fall back to Grok | Send the message again; it is not a computer problem, so do not Recover or Reset |
| "Grok Bot is having trouble connecting", and Recover and Reset fail | On October 8 staff found one such case was an ended trial: the account had no Grok Bot access and the app showed it as a connection error. 0.71.2 says accounts without access now finish setup and see just the access notice | Update the app, then check your plan with the same account: on The X Subscription, Cursor's plans help says Premium, Super and Ultra include Grok Bot and Plus and Free do not. Fully quit and reopen the app afterwards |
| "Reset failed" with a partial-state warning | During the October 8 incidents staff said the bots' errors were on Cursor's side and the partial state would clear on its own | Do not retry the reset; check the live status and the forum first |
| A Bot says your Mac or PC is offline or disconnected when it is on | Since recent desktop versions, the app pauses the local connection when the screen locks, the computer sleeps, or the Grok Bot window is not the active window for about 10 minutes, and it does not resume on its own when a Bot needs it (staff, October 5 to 13). On October 13 staff said they could not confirm that 0.70.2 fixes it. 0.71.2 changed related behaviour: a sleeping computer counts as disconnected within two minutes, and after a Wi-Fi, VPN or network change Bots can reach it right away. Two users wrote that the drops stopped for them, one on 0.70.2 and one from just before 0.72.0; Cursor has not said the window-focus pause was removed | Update first. If it still happens, click into the Grok Bot window on that computer; it reconnects within about a minute. Keep the window in front before scheduled jobs; there is no setting to turn this off. Staff also called a user's workaround, running Tailscale on that machine, valid. Drops while the window stays in front are a separate case staff asked to be reported in its own thread |
| Update stuck at 43 percent on "Transferring your data" | Computers failing to fully rehydrate during recreation (Cursor staff, September 20); a second thread shows the stall recurring past September 21 | Do not reset; post your app version and the time you first saw it in the forum thread and staff will clear the account, sometimes within about 20 minutes |
| "Authentication error. If you are logged in, try logging out and back in." | For most users in the Windows thread, the app stayed signed in but the computer needed an update | Settings → Computer → Update Bot's Computer; see [the sign-in guide](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows) if login itself never completes |
| The screen says you have reached your Grok Bot usage limit | Weekly usage is used up and on-demand is off | Wait for the weekly reset, or turn on on-demand with a monthly limit; see [the usage limit guide](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit) |
| An error mentioning Legacy Privacy Mode | The Cursor account uses a data mode that does not allow Grok Bot's required storage | Change the Cursor data setting, or ask your organization's administrator |

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://status.x.ai/history, https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bots-computer-at-43/172401, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bot-s-computer-at-43/172535, https://forum.cursor.com/t/grok-bot-windows-0-44-0-authentication-error-persists-after-update-logout-login-and-cache-clear/171115, https://cursor.com/help/grok-bot/plans, https://cellcog.ai/blog/grok-bot-problems/, https://forum.cursor.com/t/grok-bots-computer-is-stuck-on-starting-desktop-with-cant-reach-grok-bots-screen-attachments-wont-download-and-the-mobile-app-shows-send-after-reconnect-with-no-response/173788, https://forum.cursor.com/t/grok-bot-shared-computer-fully-wedged-since-2026-10-05-shell-dead-update-recover-reset-all-fail-please-reprovision/173881, https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504, https://forum.cursor.com/t/grok-bot-primary-bot-silent-bot-failed-to-respond-since-oct-8-other-bots-ok-restart-this-bots-runner-only-do-not-reset/174138, https://forum.cursor.com/t/grok-bot-restore-existing-agents-that-fail-with-bot-failed-to-respond-since-oct-8-do-not-reset/174246, https://forum.cursor.com/t/grok-bot-bots-error-out-and-stop-responding-whenever-i-ask-for-a-scientific-literature-review-reset-didnt-help/174218, https://forum.cursor.com/t/grok-bot-0-68-1-macos-cant-reach-computer-delete-fails-update-does-nothing/173950, https://forum.cursor.com/t/grok-bot-completely-unusable-recovery-and-reset-both-fail/174022, https://forum.cursor.com/t/grok-bot-0-68-1-reset-failed-computer-stuck-in-partial-state/174099, https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223, https://forum.cursor.com/t/grok-bot-thinks-my-computer-is-offline-or-sleeping-but-it-is-not/174267, https://forum.cursor.com/t/grok-bot-0-68-1-on-mac-mini-local-computer-drops-while-idle-and-does-not-self-heal/174109, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.5, https://forum.cursor.com/t/all-my-grok-bot-disappear/175510

## The official recovery order

These steps are from the official troubleshooting page for a computer that cannot be reached. Do them in order and stop as soon as Bots reply again.

One exception comes from Cursor staff rather than the docs: when the live status shows an open incident, or staff are already handling a server-side fault on your account, they have asked people to hold off on Update, Recover and Reset. In October those actions did not clear server-side problems and could make a half-finished recreate worse.

1. Choose Retry, or reopen the conversation.
2. Restart the Grok Bot app, then check for an app update under Settings → Updates → Check for Updates.
3. Choose Recover computer when the unreachable-computer state offers it (the confirmation dialog calls it Recover Grok Bot's Computer) and wait for it to complete.
4. If recovery is not available, open Settings → Computer and, under Bot's computer, choose Update Bot's Computer, then wait for the replacement to come up. Since the October 11 release, Settings → Computer separates your own computer from the Bot's computer, and Settings → Updates shows only app updates; on iPhone and Android the troubleshooting page names only Reset Computer under Settings → Bot → Bot Computer.
5. Only then use Reset Bot's Computer, in the same section, knowing it restores the last saved snapshot and can lose recent or unsynced work; Recover computer and Update preserve durable files and logins.

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/settings-and-notifications, https://x.ai/changelog/bot, https://forum.cursor.com/t/grok-bot-was-reprovisioned-to-a-new-context-but-recent-data-from-the-previous-computer-was-not-carried-over/173771, https://forum.cursor.com/t/grok-bot-shared-computer-fully-wedged-since-2026-10-05-shell-dead-update-recover-reset-all-fail-please-reprovision/173881

## What the August to October incidents looked like

CellCog's problems tracker, citing a Cursor staff reply, describes an August 20 to 21 incident in which the shared computer behind affected accounts entered a stuck state, so every Bot on the account stopped at once. A larger wave followed in September. Cursor's status page records Grok Bot computers unreachable for some users on September 7, when Recover or Reset could also fail, then service degradations with bots that don't respond on September 16, 17 and 18. A forum thread opened September 16 gathered over 180 replies describing Bots that stopped responding and messages that were sent but never answered.

On September 20 and 21 a different symptom appeared: Updating Grok Bot's Computer hung at 43 percent on Transferring your data. Cursor staff said some computers were failing to fully rehydrate during recreation and most came up on their own, then closed the first thread on September 21 once computers stopped getting stuck.

That was not the end of it. A second thread, opened the same day the first was closed, collected the identical stall through September 23, including one user who said they had not been able to update the bot computer in about two weeks. Staff did not describe a systemic fix in that thread; instead they cleared individual accounts on request, once about 20 minutes after a September 21 screenshot and again for a different user on September 23. Treat the 43 percent stall as a recurring, not fully resolved, issue: post your version and the time in the forum thread rather than resetting, and expect staff to clear your account manually.

October brought a different mix. On October 3 Bots stopped answering in the early hours US Eastern time; a Cursor staff member said the fix landed at about 3:10 AM ET, that messages sent while it lasted were not retried, and that routines due between about 2:00 and 3:10 AM ET did not run. On October 5 an update left some computers stuck on Starting desktop because a recent change gave them too little storage, and the same storage problem left some replacement computers with a 16GB disk that was full on arrival until staff restored full-size disks on October 6. Some accounts got an automatic recreate that did not finish cleanly and came up from an incomplete copy; staff told those users not to press Update, Recover or Reset and replaced the computers individually. On the evening of October 6 (UTC) every Bot on some accounts answered Bot failed to respond until Cursor fixed it on its side; staff said no reset was needed.

October 8 piled several problems together. Early in the day (UTC) every Bot on some accounts answered Bot failed to respond until a fix on Cursor's side; from about 13:30 UTC a capacity limit stopped some Bots reaching their model until about 21:00 UTC; and replies failed for some users in one region, including Hong Kong, where people found a VPN helped, until a fix that evening. In each case staff said Bots and history were safe and a reset would not help. The same week, staff explained a quieter failure: a single Bot that always fails because the model provider's safety filter refuses its conversation history. The October 6 incident also pulled new replies into a five-week-old thread opened back on September 1 under the same error text; staff resolved it the same way, telling the latest posters their Bots should already be replying again and that no reset or other change was needed.

These are attributed community reports and status notices. The pattern they share is that user-side recovery did nothing during the incident window, and resets made things worse by discarding state. If your symptom matches a live status incident or thread, the useful action is to add your app version and timestamp to the thread and wait.

Sources: https://forum.cursor.com/t/grok-bot-failed-to-respond-on-every-bot-after-reset-recover-computer/173919, https://forum.cursor.com/t/grok-bot-0-68-1-bot-failed-to-respond-after-reset-sends-get-requestid-but-no-assistant-reply/174090, https://forum.cursor.com/t/grok-bot-primary-bot-silent-bot-failed-to-respond-since-oct-8-other-bots-ok-restart-this-bots-runner-only-do-not-reset/174138, https://forum.cursor.com/t/grok-bots-failing-to-respond-again/173658, https://forum.cursor.com/t/grok-bots-computer-is-stuck-on-starting-desktop-with-cant-reach-grok-bots-screen-attachments-wont-download-and-the-mobile-app-shows-send-after-reconnect-with-no-response/173788, https://forum.cursor.com/t/grok-bot-computer-reprovisioned-from-126gb-to-16gb-and-immediately-100-full-ticket-t-g55930/173656, https://forum.cursor.com/t/grok-bot-was-reprovisioned-to-a-new-context-but-recent-data-from-the-previous-computer-was-not-carried-over/173771, https://forum.cursor.com/t/grok-bot-failed-to-respond/170235, https://status.x.ai/history, https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bots-computer-at-43/172401, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bot-s-computer-at-43/172535, https://cellcog.ai/blog/grok-bot-problems/

## A Bot that goes quiet after a long tool wait

One report describes a Bot becoming unresponsive after a long-running tool call, with a recreated Bot showing 'Failed to send' until the app was restarted. If one Bot is silent while others work, the computer is probably fine. Send a 'Stop now' message, restart the app, and give the Bot a smaller bounded task before retrying the long one. If it is a routine that went quiet, [the routines guide](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running) has its own checklist.

Recent versions handle this better, so update first. The changelog says 0.66.0 (October 2) makes a Bot that hangs on an unresponsive command or computer stop itself with a note, and your next message picks up where it left off. 0.68.1 (October 7) makes Stop or a new message end a Bot stuck on an unresponsive step within about 30 seconds, and the Bot's browser now gives up on a stuck page after 25 seconds. The October 11 release (0.69.0 to 0.70.2) adds two more: Bots acknowledge your message before longer work, and a Bot can wait for a background command to finish, shown as Waiting on results, so a quiet Bot is not necessarily a stuck one. 0.71.2 (October 14) goes further: Stop also ends a Bot's background subagents and expires their pending approval cards, connector calls wait up to two minutes instead of timing out after one, and a Bot posts its answer when you hand its computer back with I'm done or Skip instead of sometimes staying silent. Since 0.75.2 (October 22) the Bot also tells you before a browser or desktop task that will take a few minutes.

- [ ] You opened the computer view and looked for a login, CAPTCHA, or approval before resetting.
- [ ] You checked the status page (status.x.ai, formerly status.cursor.com) and the forum tag for an incident with a matching timestamp.
- [ ] You followed Retry, restart, Recover, Update before Reset.
- [ ] You noted the app version and time in case you need to report it.
- [ ] You are on the latest app version (Settings → Updates), since 0.66.0, 0.68.1 and 0.70.2 fixed hung-Bot, crash-loop and sleeping-computer handling, and 0.71.2 to 0.75.5 fixed the asleep, reconnect, safety-check and proxy cases in the table above.

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2

## Your own Mac or PC looks connected, but a file copy drops it

A forum thread opened August 29, past 690 views by October 29, describes Settings → Computer showing your own Mac as connected while the Bot cannot use it: one Shell command works, the next fails as disconnected, and copying a file to or from the Mac fails with the computer unavailable. A Cursor staff member (deanrie) explained on August 29 that when a command or a file copy hits a timeout, the machine is removed from the Bot's machine list for about a minute even though Settings still shows connected, and that the set of available machines is fixed when a turn starts, so No registered machines were available when this turn started means the machine reconnected mid-turn and a new message will pick it up. They confirmed the same cause for a large archive copy on September 3 and for a Windows report, and still had no ETA on September 17.

The staff workaround, repeated in each reply: split large copies into smaller pieces instead of one big archive; if the machine drops, wait about a minute before retrying rather than retrying at once; and if it stays stuck, fully quit Grok Bot (Cmd+Q on a Mac), end any stuck local-exec-daemon process (pkill -f local-exec-daemon in Terminal, or Task Manager on Windows), and reopen the app. A Windows user added a workaround of their own on September 16: delete the local-exec-daemon log files under the .grokbot folder in your user profile, restart the computer, open Grok Bot, wait a full minute, then start a new chat. On October 29 a user on Grok Bot 0.78.1 reported copies over about 100 KB still failing with temporarily unreachable on an M1 MacBook Air, so treat this as open. It is a community report with a staff reply, not a fix we tested, and the release notes through 0.78.1 do not name it.

Sources: https://forum.cursor.com/t/grok-bot-local-computer-execution-looks-connected-in-settings-but-is-not-actually-usable-for-file-i-o/169877, https://x.ai/changelog/bot#v0.78.1

## Every Shell command hangs, but Bots can still read files

A forum thread opened on October 20 describes a Bot's computer where every Shell command, even echo ok, failed with "The Shell tool call timed out after 840 seconds" for all 11 Bots on the account, while connectors such as Gmail and Calendar kept working. Update and Reset did not help.

A Cursor staff member replied on October 21 that the Reset had moved the computer onto a fresh machine with the files restored, so the stall pointed to something in the saved files rather than the machine. Every Shell command first starts a login shell, which runs the computer's shell startup files; if one of them waits on something, such as a line that starts a service, runs sudo or calls a script, every command hangs. Their recovery step: ask a Bot to open /home/box/.bashrc, /home/box/.profile and /home/box/.bash_profile (or the same names under ~/) with its file reading tool, not Shell, look for anything recently added near the end, and hold off on another Reset or Update, since a Reset restores the same files.

In that thread the poster's Bots found an autostart line for a relay script near the end of .bashrc, which they suspected. The computer started working again on October 25 without a further staff reply, and the poster said they did not know whether it recovered on its own or was fixed. On October 26 another user reported the same symptom for two to three days, with file reads also timing out, so the file check does not work once the computer stops answering entirely. If you add startup commands to a Bot's computer, keep them out of shell startup files, or make sure they return immediately. This is a community report with a staff reply, not a fix we tested.

More accounts hit the same symptom in the last week of October, and staff replies point to two different causes. In a 204-view thread opened October 23, the poster's computer had been frozen since the afternoon of October 22: every command stalled for about 14 minutes and failed, Update Bot's Computer did not help, and the app showed disk space unknown. A Cursor staff member replied on October 24 that the computer was running but every command stalled before it started, that a move to a fresh machine, Update Bot's Computer and Reset all bring the saved files along, so a stalling startup file comes back each time, and asked users not to Reset, since it can lose recent work that has not been saved yet. Their recovery step: from the desktop app on your Mac, ask a Bot that uses its computer to copy /home/box/.profile and /home/box/.bashrc to your Mac with its file copy action, not a terminal command, and look for lines near the end that start a program, connect to something or run a script. The fix is usually to copy the corrected files back the same way and run Update Bot's Computer once, which keeps saved files. Staff added that a stalled command uses no usage while it waits, but each failure costs a short follow-up step and routines that need the computer keep retrying, so pause those routines meanwhile.

In that thread the cause was a watchdog line in .bashrc written as pgrep ... || nohup ... &. Staff explained on October 26 that the trailing & sends the whole line to the background, which keeps terminal startup from finishing whenever the watchdog is not already running, as on a fresh computer after a move or update. Their advice: keep the line commented out and start the program from a routine instead, or wrap only the launch part in braces, { nohup ... & }, so only that part runs in the background.

The second cause needed Cursor's side. In a 213-view thread opened October 25, a computer that froze again right after a Reset on October 23 hung every command and file read for about 14 minutes, and Update and Reset both failed, while chat, memory and connectors still worked. A Cursor staff member wrote on October 26 that some users had two computers started, and on October 27 that the team had run manual cleanup for accounts stuck with two; the poster's computer came back that day, froze again, and was working by October 29. Another user, whose startup files were clean and whose computer view never got past Starting desktop…, reported on October 29 that theirs had come back too after staff said they were investigating. If your startup files are clean and Update and Reset fail, this is not something you can fix yourself: contact support with your ticket number instead of resetting again. These are community reports with staff replies, not fixes we tested.

One related cause now has a release-note fix: the 0.77.0 changelog (October 26) says commands on the Bot's computer that wait for input, such as package install prompts, finish instead of hanging. That covers a single command stuck on a prompt, not a startup file that stalls every login shell, so if every command still times out after updating, the file check above is still the step to take.

Sources: https://forum.cursor.com/t/grok-bot-box-unresponsive/175485, https://forum.cursor.com/t/grok-bot-computer-frozen-since-oct-22-1-45-pm-et-all-commands-time-out/175846, https://forum.cursor.com/t/grok-bot-shared-computer-frozen-since-10-23-after-reset-shell-and-file-reads-hang-about-14-min-and-update-and-reset-both-fail-t-i28766/176129, https://x.ai/changelog/bot#v0.77.0

## A Bot that keeps trying the same thing

Sometimes a Bot is not silent but stuck in a loop: retrying a page, re-running a search, or repeating an approach without new evidence. Before sending the whole request again, find out whether the first attempt already wrote anything. A retry can create a second draft, ticket or message if the earlier attempt succeeded just before it lost its way.

Ask for the last action it confirmed, the first step that failed, and any changes it already made outside the chat. If a source failed, test one small read before rerunning the full task. This brief is our editorial template; it moved here from a separate triage guide that now redirects to this page.

One common loop has an official fix. The October 11 changelog says that when a connector is rate-limited, Bots now wait for its retry delay instead of looping, and Slack, Gmail and Outlook drafts retry through temporary rate limits and say if they still could not send. Connector calls should also fail less often. If a Bot on an older version keeps hammering one connector, update the app first.

Editorial template (replace placeholders and review access before running):

```text
Pause the current approach and diagnose the blocker. State the last action confirmed successful, the first failing step, the exact visible error if any, and whether any external changes already occurred. Do not repeat writes or reset the computer. Suggest one small, non-destructive check that distinguishes missing access from unavailable data or a changed interface. If you need my input, identify the precise action I should take. Preserve partial results and link them here.
```

Sources: https://x.ai/changelog/bot

## Quick answers

### Which Grok Bot version fixed which symptom?

Going by the release notes: 0.71.2 (October 14) shows Your computer is asleep instead of Couldn't refresh or connection errors, lets you wake an asleep computer in place by clicking its preview, says a computer couldn't start instead of retrying as if it were still starting, reconnects a working Bot when its computer updates, treats a sleeping Mac or PC as disconnected within two minutes, keeps your computer reachable after a Wi-Fi, VPN or other network change, gives connector calls up to two minutes instead of timing out after one, and shows Blocked by a safety check instead of a generic error. 0.75.2 (October 22) fixes loading behind some corporate proxies and says when a message could not be saved because the disk is full. 0.75.5 (October 23) makes new messages get replies after you reset a chat whose first message was blocked. Update first; the notes describe fixes, not a guarantee for every account.

### Why did all my Bots stop responding at the same time?

Every Bot in an account shares one cloud computer. When that computer is stuck, unreachable, or mid-update, all Bots fail together. That is why 'Bot failed to respond' tends to hit the whole account, and why the fix is on the computer, not the Bot.

### Should I reset the Agent Computer?

Only as the last step. The official order is Retry, restart the app, Recover computer, Update Agent Computer, and then Reset. Reset can lose unsynced work, and forum users report resets that stall at 50 percent during service incidents. In October, Cursor staff repeatedly asked people whose problem was on Cursor's side to hold off on Update, Recover and Reset altogether; after the October 3 and October 6 incidents the fix was simply to send the message again.

### How do I know if it is an outage and not me?

Look at the live status panel at the top of this page, which reads status.x.ai (Cursor's status page redirects there since its October 26 move), then the Cursor forum's grok-bot tag, and compare timestamps. Cursor's status page recorded 21 incidents involving Grok Bot on 14 different days between September 3 and October 9; the main forum thread from September 16 passed 180 replies while nothing on the user side helped. If many people report the same symptom in the same hour, wait rather than reset.

### Why does one Bot always say Bot failed to respond while my other Bots work?

Often its conversation, not the computer. In October, Cursor staff explained several such cases: the AI model provider's safety filter had flagged something in that Bot's history, such as security or biology research material, and because every new message is sent with that history, every reply was refused and shown as a generic error. Resetting does not help. Staff advise using another or a new Bot for new work, not asking other Bots to read or continue the stuck Bot's chat, and not deleting it while they look for a recovery option. Since 0.71.2 the release notes say a reply blocked by a safety check shows Blocked by a safety check and Try a different message instead of a generic error, and 0.75.5 says that after you reset a chat whose first message was blocked, new messages get replies instead of an error.

## Sources

- [Official troubleshooting](https://docs.x.ai/grok-bot/troubleshooting)
- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Status history (Cursor's incidents, on status.x.ai since October 26)](https://status.x.ai/history)
- [Forum: Grok bot failed to respond (15 replies, resurfaced during the October 6 incident)](https://forum.cursor.com/t/grok-bot-failed-to-respond/170235)
- [Forum: some Bots became unresponsive (September 16, 186 replies)](https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858)
- [Forum: computer update hung at 43 percent (staff update)](https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bots-computer-at-43/172401)
- [Forum: computer update hung at 43 percent, second thread (12 replies, reports into a second week)](https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bot-s-computer-at-43/172535)
- [Forum: Windows authentication error (staff fix)](https://forum.cursor.com/t/grok-bot-windows-0-44-0-authentication-error-persists-after-update-logout-login-and-cache-clear/171115)
- [Cursor plans and billing (usage-limit screen)](https://cursor.com/help/grok-bot/plans)
- [CellCog problems tracker](https://cellcog.ai/blog/grok-bot-problems/)
- [Grok Bot changelog (versions 0.63.0 to 0.70.2)](https://x.ai/changelog/bot)
- [Settings: update or reset Bot's computer](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Forum: Grok Bots failing to respond again (staff reply on the October 3 fix)](https://forum.cursor.com/t/grok-bots-failing-to-respond-again/173658)
- [Forum: Starting desktop and Can't reach Grok Bot's screen (staff fix, October 5)](https://forum.cursor.com/t/grok-bots-computer-is-stuck-on-starting-desktop-with-cant-reach-grok-bots-screen-attachments-wont-download-and-the-mobile-app-shows-send-after-reconnect-with-no-response/173788)
- [Forum: computers reprovisioned with a 16GB disk (staff fix, October 6)](https://forum.cursor.com/t/grok-bot-computer-reprovisioned-from-126gb-to-16gb-and-immediately-100-full-ticket-t-g55930/173656)
- [Forum: an automatic recreate that did not finish cleanly (staff reply, October 5)](https://forum.cursor.com/t/grok-bot-was-reprovisioned-to-a-new-context-but-recent-data-from-the-previous-computer-was-not-carried-over/173771)
- [Forum: shell dead, Update, Recover and Reset all fail (staff reply, October 7)](https://forum.cursor.com/t/grok-bot-shared-computer-fully-wedged-since-2026-10-05-shell-dead-update-recover-reset-all-fail-please-reprovision/173881)
- [Forum: every Shell command times out, check shell startup files (staff reply, October 21)](https://forum.cursor.com/t/grok-bot-box-unresponsive/175485)
- [Forum: computer frozen, every command times out after 14 minutes; startup-file check and watchdog fix (staff replies, October 24 and 26)](https://forum.cursor.com/t/grok-bot-computer-frozen-since-oct-22-1-45-pm-et-all-commands-time-out/175846)
- [Forum: computer frozen after Reset, Update and Reset fail; two computers started, manual cleanup (staff replies, October 26 and 27)](https://forum.cursor.com/t/grok-bot-shared-computer-frozen-since-10-23-after-reset-shell-and-file-reads-hang-about-14-min-and-update-and-reset-both-fail-t-i28766/176129)
- [Forum: all Bots silent with no usage limit message, fixed (staff update, October 30)](https://forum.cursor.com/t/grok-bot-all-bots-completely-unresponsive-after-update-agent-computer-recovery-and-reset/172118)
- [Forum: Bot failed to respond on every Bot (staff reply, October 6)](https://forum.cursor.com/t/grok-bot-failed-to-respond-on-every-bot-after-reset-recover-computer/173919)
- [Forum: outbound non-HTTPS traffic blocked since October 1 (staff reply)](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504)
- [Forum: one Bot fails while others reply, blocked by the model provider's safety filter (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-primary-bot-silent-bot-failed-to-respond-since-oct-8-other-bots-ok-restart-this-bots-runner-only-do-not-reset/174138)
- [Forum: existing Bots fail since October 8, safety filter on biology content (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-restore-existing-agents-that-fail-with-bot-failed-to-respond-since-oct-8-do-not-reset/174246)
- [Forum: Bots stop responding after a literature review request (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-bots-error-out-and-stop-responding-whenever-i-ask-for-a-scientific-literature-review-reset-didnt-help/174218)
- [Forum: trouble connecting and Reset fails after a trial ended (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-completely-unusable-recovery-and-reset-both-fail/174022)
- [Forum: Reset failed, computer stuck in a partial state (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-0-68-1-reset-failed-computer-stuck-in-partial-state/174099)
- [Forum: Can't reach the Bot's screen after the computer's first startup failed (staff replies, October 7 and 12)](https://forum.cursor.com/t/grok-bot-0-68-1-macos-cant-reach-computer-delete-fails-update-does-nothing/173950)
- [Forum: Mac shows disconnected until the app is focused (staff replies, October 9 to 13)](https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223)
- [Forum: Bot thinks my computer is offline or sleeping (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-thinks-my-computer-is-offline-or-sleeping-but-it-is-not/174267)
- [Forum: your own computer looks connected but a file copy drops it (staff workaround, August 29 to September 17; still reported on 0.78.1, October 29)](https://forum.cursor.com/t/grok-bot-local-computer-execution-looks-connected-in-settings-but-is-not-actually-usable-for-file-i-o/169877)
- [Grok Bot changelog: 0.75.8 (October 24): reconnect after the Bot's computer wakes, Authenticate state, status line, Slack safety-check notice](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog: 0.77.0 (October 26): computer stays up on low memory, commands waiting for input, Not delivered yet, Stop and Update](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot changelog: 0.78.1 (computer card, Update dialog, Route traffic and Reset fixes, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Forum: Mac mini local computer drops while idle (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-0-68-1-on-mac-mini-local-computer-drops-while-idle-and-does-not-self-heal/174109)
- [Forum: replies failing for some users in one region (staff fix, October 9)](https://forum.cursor.com/t/grok-bot-0-68-1-bot-failed-to-respond-after-reset-sends-get-requestid-but-no-assistant-reply/174090)
- [Grok Bot changelog 0.71.2 (October 14): asleep computer, reconnects, safety-check message, connector timeouts](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog 0.75.2 (October 22): corporate proxy loading, disk-space message, Couldn't refresh in Connect Apps](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog 0.75.5 (October 23): replies after resetting a blocked chat](https://x.ai/changelog/bot#v0.75.5)
- [Forum: all my Grok Bots disappeared after the X Subscription switch (staff replies, October 21)](https://forum.cursor.com/t/all-my-grok-bot-disappear/175510)