# Grok Bot computer unresponsive since Nov 6 — ticket T-J53687 unanswered, cannot reset without data loss

**URL:** <https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924>\
**Category:** Bug Reports\
**Tags:** crashes, grok-bot\
**Created:** [November 10, 2026, 9:34am UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924 "2026-11-10T09:34:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Desh](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@Desh](https://forum.cursor.com/u/Desh)\
**Post date:** [November 10, 2026, 9:34am UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924/1 "2026-11-10T09:34:26Z")

</div>

### Describe the Bug

My Grok Bot computer (shared by all my bots) has been unresponsive since November 6, 2026.

What is broken:

- Commands, file reads, and screenshots on the bot computer time out after about 14 minutes
- Settings → Update Bot’s Computer shows it is already up to date and does not offer an update
- Reset Computer would wipe data I need (Proton Mail Bridge, browser logins, and files), so I cannot use Reset

As a result, Grok Bot is completely unusable.

What I have already tried with support:

- Opened ticket T-J53687 with [support@x.ai]
- On November 7, automated agent replied with no resolution
- I followed up to this ticket. The last three emails have had no response
- I also submitted this through the in-app feedback form on November 9

What I need:  
A data-preserving restart of the bot computer, the same kind of fix described here: [forum.cursor.com/grok-bot-computer-non-responsive](https://forum.cursor.com/t/grok-bot-computer-non-responsive/177289)

Ticket: T-J53687

### Steps to Reproduce

The computer is fully not responsive since Nov 6

### Expected Behavior

Computer needs an urgent reboot without loss of data on it, and the root cause of the issue identified

### Operating System

Other

### Version Information

Grok Bot 0.79.3  
Grok Bot Computer shows “Up to date” (no version is indicated)

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [November 10, 2026, 10:06am UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924/6 "2026-11-10T10:06:03Z")

</div>

Hey @Desh

This is a known issue we’re tracking, not anything on your end. Quick heads‑up: don’t Reset - Update, Recover, and Reset all rebuild the computer from saved data, so it comes back stuck and you’d lose installed apps like your Proton Mail Bridge. The real fix is to clear one stuck startup file and restart, and we can do that on our side without resetting your data - your files and logins stay put. I’ve put your report in front of the team handling this and I’ll follow up right here with an update.

---

<div class="post-metadata">

**Author:** ![Desh](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@Desh](https://forum.cursor.com/u/Desh)\
**Post date:** [November 10, 2026, 11:17am UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924/8 "2026-11-10T11:17:37Z")

</div>

Thank you. If anything needs to be removed from startup, please do so, and let me know so I would implement a change to the process for the future.

---

<div class="post-metadata">

**Author:** ![Desh](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@Desh](https://forum.cursor.com/u/Desh)\
**Post date:** [November 10, 2026, 8:02pm UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924/10 "2026-11-10T20:02:35Z")

</div>

I was reached by support over email, saying that my computer is up and running well. I tested, and the computer is still fully frozen and unresponsive, same as before.

---

<div class="post-metadata">

**Author:** ![Desh](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@Desh](https://forum.cursor.com/u/Desh)\
**Post date:** [November 10, 2026, 10:08pm UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924/11 "2026-11-10T22:08:07Z")

</div>

And another response from support in email, asking me to comment (#) startup scripts, which was already done two days ago, and there are no scripts in startup already for two days.

Apparently, nobody has checked anything.

I am unable to use Grok Bot for 5 days already, and counting.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [November 11, 2026, 3:20pm UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924/12 "2026-11-11T15:20:25Z")

</div>

@Desh You computer should now be on the latest image without this issue, are you still encountering the issue?

---

<div class="post-metadata">

**Author:** ![Desh](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@Desh](https://forum.cursor.com/u/Desh)\
**Post date:** [November 11, 2026, 7:56pm UTC](https://forum.cursor.com/t/grok-bot-computer-unresponsive-since-nov-6-ticket-t-j53687-unanswered-cannot-reset-without-data-loss/177924/13 "2026-11-11T19:56:39Z")

</div>

Hi Colin, thanks for following up. Yes, my computer is responding again as of today, November 11. Commands return instantly and the desktop renders normally, and it has been up about 4 hours. Could you also confirm that this is a permanent fix and not a one-time restart, and let the support team on ticket T-J53687 know? They haven’t acknowledged the issue, and I’d like them to close it with the right context.
