Grok Bot offline since Nov 7, Reset unresolved — T-J51832: recovery ETA / next update

[LLK (李朗琨)]

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

My Grok Bot computer became inaccessible on November 7, 2026. I initiated a Reset, but access has still not been restored as of November 10. The computer currently shows Offline.

Symptoms:

• Simple Shell commands hang and time out after approximately 840 seconds (14 minutes).
• Desktop screenshots fail.
• Chat remains available, and some file reads have worked, but I cannot use the computer to carry out tasks.

My existing support ticket is T-J51832. Support said it had been escalated, but I am still waiting for an actionable recovery update. Since support instructed me to stop, I have not initiated another Reset, Recover, or Update.

Please have a staff member check the actual server-side state of my computer and the incomplete reset/recovery, and coordinate the response with the existing ticket.

Steps to Reproduce

With the affected bot computer in its current state, ask the bot to run a simple Shell command or capture a desktop screenshot. The command hangs until timeout and the screenshot fails. A Reset initiated after the November 7 outage did not restore access.

Expected Behavior

Please reply with:

1. The current reset/recovery status and which team is handling the case.
2. An estimated date and time, including the time zone, when I can use the bot computer again. If a restoration ETA is not yet available, please commit to a specific date and time for the next status update, even if the issue is still unresolved.
3. Whether a data-preserving server-side restart or startup-file repair is appropriate for this instance. Preserving my existing files and logins is a priority; please explain any potential data loss and obtain my approval before taking destructive recovery steps.

After recovery, I will verify that a simple Shell command completes, a desktop screenshot succeeds, and the computer is accessible again.

Operating System

Windows 10/11

Version Information

Grok Bot desktop for Windows
Installed application version: 0.79.3 (ProductVersion 0.79.3.0)
Affected service: bot computer / server-side reset and recovery

Additional Information

Related cases:

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

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 wit…

Staff described a stuck startup file and a data-preserving server-side restart. Could you check whether this also applies to my instance?

Grok Bot Computer Non Responsive

Hi @Bowtiedwave, swapping in the stock .bashrc was the right move. The computer just needs one restart afterward, because commands stay stuck until it restarts, and both of your Resets happened before you replaced the file. This should be done now. Can you check?

In that case, staff performed a restart and the user subsequently confirmed recovery.

Please track this request under existing ticket T-J51832. Thank you.

Does this stop you from using Cursor

Yes - Cursor is unusable

[Colin]

Hi @Kartik1

This is likely the same issue as reported here. Can you try following the same steps?

Grok Bot shell dead since Oct 22 – every command stalls 840s; .bashrc unreadable + .profile autostart loop; Update/Reset don't help

Hey @beartester, You’re right about line 30 of .profile! We ran it in the same login shell your bots use: the shell finishes, but the background copy it starts keeps the command’s output open, so the command never registers as started and times out at 840 seconds. Every bot command goes through that startup, so they all stall. That line isn’t part of the standard setup. By default .profile ends at line 27, and nothing on our side adds to it. Since it starts your ledger-api folder, most likely …

[LLK (李朗琨)]

Thanks @Colin — my bot computer is working again after fixing the startup files. I appreciate your help!

How can I prevent this kind of freeze from happening again during normal use? What should I do, or what instructions should I give my bots, so they can install software and run timed tasks without causing another lockout?

A few simple guidelines, or a short instruction I can copy directly to my bots, would be very helpful. Thank you!

[Colin]

The issue is on our side and a fix should be pushed soon.