Grok Bot computer frozen since Nov 1 — 840 s shell timeout on echo ok, file reads hang too (T-I85456 / T-I90006)

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

My shared Grok Bot Agent Computer has been continuously frozen since about 7:28 PM ET on Nov 1. Every Shell call times out at 840 seconds, even echo ok. Today (Nov 4, ~1:35 PM ET) a simple file Read of /home/box/.bashrc also hung for over 150 seconds before I stopped it, so it isn’t only the shell. All my bots share this computer, so every scheduled routine and script that needs it has been failing since then. Before this, I logged 31 separate freezes totalling about 23 hours.
I’ve already tried both fixes. Update Bot’s Computer doesn’t help, and a full Reset a few days ago didn’t fix it either; the freezes came back on the fresh computer.
I’ve seen similar 840 s freezes fixed in this thread: Grok Bot computer frozen for 26+ hours, all bots down (ticket T-I8096) (a startup file holding the shell open), and in others caused by a full disk. Since a Reset didn’t help, could you check whether my machine is unreachable or failing on your side, and tell me safe recovery steps that won’t lose my files?
Tickets: T-I85456 and T-I90006 ([email protected]). So far I’ve only had automated replies.
@Colin, would you be able to take a look? Thank you.

Steps to Reproduce

Run any Shell command on my Grok Bot computer, even echo ok. It times out after 840 seconds. A file Read of /home/box/.bashrc also hangs for over 150 seconds. This has happened continuously since about 7:28 PM ET on Nov 1, and Update and Reset don’t fix it.

Expected Behavior

echo ok returns instantly and scheduled routines run normally.

Screenshots / Screen Recordings

Operating System

MacOS
iOS

Version Information

Grok Bot web (browser) + iOS app, latest as of Nov 4 2026

For AI issues: which model did you use?

N/A, computer issue

Additional Information

All bots on my account share this computer, so the whole setup is down. Happy to share timestamps or ticket emails.

Does this stop you from using Cursor

Yes - Cursor is unusable

@Colin @mohitjain Could you please do a server-side teardown and give me a fresh computer?

Since Nov 1 at about 7:28 PM ET, both Shell and file reads hang until the 840-second timeout, even echo ok and reading /home/box/.bashrc. I’ve already run Update Bot’s Computer and Reset, and neither helped. Because file reads hang too, I can’t use the startup-file fix (copying .bashrc and .profile off the computer).

jaharoni’s explanation above fits what I’m seeing: Update reattaches the same stuck storage, so restarting doesn’t clear it. That’s why I’m asking for a fresh computer instead of another restart.

I’ll hold off on any more Resets until you tell me to. My support tickets are T-I85456 and T-I90006. My whole multi-bot desk has been down for four days while I’m paying, so a quick look would really help. Thank you!

Hi there,

The hang is a line in one of its startup files (~/.bashrc or ~/.profile), almost certainly added by one of your bots, that starts a background program and never lets the shell finish, so every command and file read times out at 840s. Resets haven’t helped because they restore that same line. You don’t need to read the stuck file to fix it, you just overwrite it with the clean default. You’ll need the Grok Bot desktop app for the copy steps https://x.ai/bot, same account):

  1. In a new chat, tell one bot “Don’t run any commands,” then test the copy path: ask it to copy a small file from your computer to the box and back. If it returns in a few seconds, continue; if it hangs, stop and reply here and we’ll take it from our side.
  2. Ask the bot to copy the box’s default files over the stuck ones: CopyFromBox /etc/skel/.bashrc, then CopyToBox it to /home/box/.bashrc; same for /etc/skel/.profile to /home/box/.profile.
  3. Wait a minute, then Reset once (your files and logins stay; you’ll just reinstall any packages).
  4. Ask a bot to run echo ok to confirm.

If you’d rather we handle it, or the copy test hangs, reply here and we’ll sort it out on our side, just please hold off on more Resets until then. To keep it from coming back, have your bots start background programs from a routine, not a startup file.