My bots can reach there computers

Support Bug Reports
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

My bots can reach there computers none of them

Steps to Reproduce

it ongoing so just needs to check the bots to see the issue

Operating System

MacOS

Version Information

Grok Bot Version 0.75.3

Additional Information

Grok Bot version: please check this in the app on your device.
Operating system and version: your computer’s or phone’s operating system.
Exact error message: “Command failed to spawn: The Shell tool call timed out after 840 seconds and was terminated. The execution environment may be unresponsive.” Reading files also hangs, sometimes with “computer is still starting up”.
Bot or routine name: the bots Olivia Lindqvist, Marcus Lindberg, Nina Holmgren and Axel Sandberg, which all share one computer. The routines “ClickUp watcher keep-alive”, “ClickUp chat mention relay” and “Nightly ClickUp University study” fail the same way.
Approximate time and time zone: it started around 23:00 on Oct 22, 2026 (Europe/Stockholm, UTC+2) and is still happening at 09:08 on Oct 23.
Request or conversation ID: I don’t have one on my side, so include it if the app shows one.
Did retry, restart or updating the bot’s computer help? No. Retries kept failing all night, and after you ran Update Bot’s Computer at about 08:40 on Oct 23, the very next command still timed out.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey there.

We were able to solve this for a user in another thread, could you check the steps we took?

  1. Ask one bot to read /home/box/.profile and /home/box/.bashrc with its file tool (not Shell) and show you the last 15 lines of each.
  2. If one of them has a line that starts something in the background, have the bot copy that file to your PC with CopyFromBox. This needs Execution on Local Computer allowed in Settings > Computer.
  3. On your computer, put a # at the start of that line and save. Keep Unix (LF) line endings: Notepad++ and VS Code show this in the status bar, and Windows (CRLF) endings will break the file.
  4. Have the bot copy the file back to the same path with CopyToBox.
  5. Click Update Bot’s Computer once. It moves to a fresh instance and keeps your files.
  6. Ask a bot to run echo ok.

If reading .bashrc itself hangs, that file is probably damaged. Have the bot copy /etc/skel/.bashrc (the stock version) to your PC with CopyFromBox and then copy it back over /home/box/.bashrc with CopyToBox.

We are working on a better solution that doesn’t require manual intervention.