My Grok Bot cloud computer has been unable to wake up or connect since I restarted and reset it on November 2. Responses are also slow. The issue affects the Windows client (version 0.78.1) and my phone.
Steps to Reproduce
On November 2, I restarted and reset the Grok Bot cloud computer. Since then, attempts to wake it or connect have failed. The issue persists on both the Windows client and my phone.
Expected Behavior
The cloud computer should wake up and connect normally, and Grok Bot should respond normally. Please preserve my files.
Operating System
Windows 10/11
Version Information
Grok Bot Windows client: 0.78.1. The issue also affects my phone.
Additional Information
@Colin@mohitjain — could you please ask the team to check the backend state of my cloud computer?
Existing support ticket: T-J4764. I requested a human engineer on November 3 and am still waiting.
Please protect and preserve my files. Before any repair that could affect data, please explain the timestamp of the latest available backup and the risk of data loss. This post does not authorize a rollback, deletion, or another reset. Please obtain my explicit approval before any such action. Thank you.
Hi @Mark9, your computer is running and your saved files are still attached to it, and your bots are still answering. What’s stuck is the step that prepares the shell before each command, so anything that needs the computer (commands, the screen) waits until it times out. That’s also why replies are slow.
This matches a known issue the team is aware of: a line in /home/box/.bashrc or /home/box/.profile, usually added by a bot, starts a background program and the shell never finishes starting. Reset and Update bring back the same file, which is why the Nov 2 reset didn’t help.
You can switch that line off from the Windows app without a Reset:
In Grok Bot Settings, set Execution on Local Computer to anything except Never.
In a new chat, ask a bot: “Use Read, not Shell, to show me the last 15 lines of /home/box/.bashrc and /home/box/.profile.” Look for a line that starts a program in the background (it often contains nohup, setsid or flock, or ends with &).
Ask the bot: “Without using Shell, copy that file to my computer.”
On your PC, open the copy, put a # at the start of that line, and save it.
Ask the bot to copy the edited file back to the same path on its computer.
In Settings, click Update Bot’s Computer (not Reset). Your files and logins stay.
Ask the bot to run echo ok.
This needs the desktop app, since the phone app can’t copy files. I can’t see backup timestamps from here. If echo ok still times out, please reply here and skip Reset.
I tried your suggested troubleshooting steps, but I got stuck at the file-reading step. I asked the bot to use Read, not Shell, to show the last 15 lines of /home/box/.bashrc and /home/box/.profile. The bot said it could not read the files because it could not connect to the cloud computer, so I cannot continue with the proposed fix.
Could you please provide an alternative solution that does not require me to access the cloud computer, or have an engineer resolve the issue from your side?
I have already backed up my data. If no other solution is available, you may reset my cloud computer directly from the backend. My priority is to restore access and normal functionality as soon as possible.
Thank you for your help! I just tried connecting from the mobile app, but I still can’t connect to the cloud computer, and the issue is the same as before. I also tried signing out and signing back in, but I still couldn’t connect.
Could you please take another look and let me know if there are any other solutions I can try? Thank you very much!