Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Grok Bot’s shared computer (the box) has been unusable since about 1:45 AM America/New_York on Oct 28, 2026. Bots can still reply in chat, but the computer does not run commands and stays stuck starting up.
Steps to Reproduce
Open Grok Bot on macOS, signed in.
Ask a bot to run a command on its computer.
The command does not run, and the computer screen stays incomplete.
Open Settings, then Computer, then Reset. It fails with the partial-state error above and does not finish.
Expected Behavior
The computer should come back with my bots, files, and logins, and commands should run. Please rebuild this Agent Computer on the backend.
Operating System
Windows 10/11
Version Information
Version: 0.78.1
Built: 2026-10-28T02:34:48.381Z
Release Track: stable
OS: win32
Additional Information
Symptoms observed overnight into the morning of Oct 28:
-
Shell / file tools hang and are killed after ~840 seconds, or return: “The computer is still starting up”
-
Attempting recovery is blocked or unsafe: the UI often shows the bot as active / working, which prevented a clean Update Bot’s Computer / Reset
-
I saw a post that suggested a possible bad background line in
/home/box/.profileor/home/box/.bashrc, but Read of those files also hung (same partial-state / unresponsive computer), so that fix could not be
before the reset the bot told me the shell hung and was unresponsive
Does this stop you from using Cursor
Yes - Cursor is unusable