Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Since about 16:45 CET (15:45 UTC) on Sunday, Oct 25, 2026, the computer that all of my Grok Bot assistants share has been stuck while booting. Every Shell command, file read and screenshot fails instantly with:
“Command failed to spawn: The computer is still starting up. Try again in a moment.”
This is different from the 840-second timeout reports in this tag. Nothing hangs here. Every call is refused right away, as if the computer never finishes starting. It has stayed this way for more than 19 hours.
Chat and connectors still work, but every bot that needs the computer is down. That includes all my scheduled routines: posting, interaction rounds and weekly analytics have been failing since Sunday afternoon.
What I’ve tried
“Update Bot’s Computer” is greyed out, and only “Reset Bot’s Computer” can be selected.
I have NOT used Reset, because support (ticket T-I37547) confirmed it’s a known issue and advised against it, since it could lose recent files and browser logins.
I waited and retried repeatedly over 19+ hours. My bots checked every 15–30 minutes with no change.
Steps to Reproduce
Open any of my Grok Bot assistants that use the shared computer.
Ask it to run echo ok or read any file.
It fails immediately with “The computer is still starting up.”
Expected Behavior
The computer finishes starting up and the bots can run commands again, without a Reset that loses data or browser logins.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
Grok Bot: Version 0.75.8
For AI issues: add Request ID with privacy disabled
Not a model issue – Grok Bot computer/infrastructure
Additional Information
Support ticket: T-I37547 (support confirmed a known issue but gave no ETA)
Multiple bots share this one computer, and all of them are affected
A simple “Restart Bot’s Computer” option (a reboot without Reset) would really help in cases like this. I’ve already suggested it to support.
Does this stop you from using Cursor
Yes - Cursor is unusable

