My Grok Bot’s cloud computer has been down for 10 days. Chat with the bot still works, but the computer screen cannot be opened, and the bot cannot read/write files or run any commands.
Steps to Reproduce
Open Grok Bot screen
Open the Computer tab → “Can’t reach screen” (Retry does not help)
Ask the bot to do anything needing file access or shell → fails or hangs
This is something we’ve seen before: a line in the computer’s startup files that starts a program in the background blocks every command, and Update, Reset, and a rebuild on our side all restore that same file. You can switch it off from the Grok Bot desktop app:
Ask a Bot: “Without using Shell, read /home/box/.profile, /home/box/.bash_profile and /home/box/.bashrc and show me any line that starts a program in the background.”
Ask it to copy that file to your computer, put a # at the start of that line, then ask it to copy the file back. If it can’t reach your computer, set Execution on Local Computer in Settings to anything except Never.
In Settings, click Update Bot’s Computer. Your files and logins stay.
Ask the Bot to run echo ok to confirm commands work.
Please skip Reset for this, and have your Bots start programs from a routine instead of those files so it doesn’t come back. If Update says you’re already up to date, a file won’t open, or the Computer tab still says “Can’t reach the screen” once commands work, reply here and we’ll take it from there.
I ran this same check last night (Nov 3), and nothing I could read starts a program in the background.
/home/box/.bashrc: no background starts (no &, nohup or setsid). The only non-standard lines are lines 1–2, a comment followed by unset GITHUB_TOKEN, which just clears a variable.
/home/box/.bash_profile: this file doesn’t exist.
/home/box/.profile: I still haven’t seen its contents. Reading it hung for 14 minutes and timed out, and you asked me not to try again. Since then, a plain stat on it also failed because the shell itself wouldn’t start.
Hi @Jams, thanks for checking those. With .bashrc clean and no .bash_profile, .profile is the file left, and the fact that even reading it hangs fits that. You don’t need to read it to fix it, though. You can overwrite it with the computer’s clean default instead.
From the Grok Bot desktop app:
In a new chat, tell a Bot “Don’t run any commands,” then ask it to copy a small file from your computer to the Bot’s computer and back.
If that comes back within a few seconds, ask the Bot to copy /etc/skel/.profile from its computer to yours, then copy that file back to /home/box/.profile.
In Settings, click Update Bot’s Computer.
Ask a Bot to run echo ok to confirm commands work.
Thanks Colin, I just checked and the Grok Bot computer is up again. Shell and file read/write both work. Appreciate you looking into this and getting it running.