Grok Bot: all projects blocked for days — Shell, file reads and computer tools fail

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

I am using Grok Bot on Windows. All of my projects that depend on the shared cloud computer have been blocked for several days.

Chat replies still work, but Shell commands, file reads, and computer operations hang or fail. Tool calls often time out after approximately 840 seconds. This affects multiple projects, not just one conversation.

I have already tried:

  • Update Bot’s Computer.
  • Reset Bot’s Computer.
  • Retrying the affected tasks and workflows.
  • Pausing scheduled tasks.

These steps have not restored normal execution.

I have contacted support several times in the email thread titled “All projects execution failure.” The issue remains unresolved, and I still do not have a concrete recovery plan or restoration estimate.

Please escalate my existing support ticket to a human engineer who can investigate the shared cloud computer and its tool-execution services.

Please confirm:

  1. Which team is handling the investigation.
  2. The next diagnostic or recovery step.
  3. How my existing project files and configuration will be preserved.
  4. When I can expect the next substantive update.
  5. Whether there is a safe workaround or a way to export my project data while recovery is pending.

Please obtain my approval before any destructive action or deletion of project data.

There is a similar report on the official forum. Please compare it with my case and verify whether the underlying issue is related:

The ticket number in that linked report belongs to another user. I can provide my own existing support-ticket details privately.

This is preventing me from using Grok Bot for my ongoing work. Please help restore the service.

Steps to Reproduce

  1. Open an existing Grok Bot conversation.
  2. Ask the Bot to run a simple command on its cloud computer, such as echo ok.
  3. Ask it to read an existing non-sensitive file.
  4. Observe that the tool calls hang or fail instead of returning the expected results.
  5. The same problem occurs across multiple projects that use the shared cloud computer.

Expected Behavior

The shared cloud computer should respond normally. Simple commands, file reads, and computer operations should complete successfully, allowing my existing projects and scheduled workflows to run again.

Operating System

Windows 10/11

Version Information

Not yet collected

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi @zhou_liya,

Your bots’ computer is starting normally and your saved files look intact; the stored files held steady through your resets. What’s stuck is the step that prepares each command before it runs. This looks like a known issue the team is tracking. It’s a different problem from the report you linked, where the computer itself stopped responding.

The likely cause is a line in .profile or .bashrc that starts a program in the background. Update and Reset restore that file, so the hang keeps coming back. Your PC is linked, so you can fix it yourself:

  1. In a new chat, tell one bot: “Don’t run any commands. Use CopyFromBox to copy .profile and .bashrc from your home folder to my computer.”
  2. On your PC, find the line that starts a script in the background (ending in &, or using nohup, setsid or a supervisor script). Add >/dev/null 2>&1 to the end of it, or put # at the start.
  3. Ask the bot to copy the edited file back to the same path with CopyToBox.
  4. Run Update Bot’s Computer once. If it says it’s already up to date, use Reset once instead. Then ask a bot to run echo ok.

In the meantime, CopyFromBox also works for copying any project folder to your PC as a backup. If you don’t find a line like that, reply here before resetting again.