My Grok Bot shared computer (box) has been completely unusable since 2026-10-05. Every Shell command hangs and times out (even echo times out after 840s). The desktop renders but the terminal stays black and the execution layer never comes up.
“Update Grok Bot’s Computer” shows “already up to date” and won’t reinstall.
“Reset Grok Bot’s Computer” stalls mid-reset and never finishes.
“Recover” is not offered on either desktop or iPhone.
Fully quitting (Cmd+Q) and reopening on every device didn’t help.
I’ve stopped pressing Update/Reset to avoid making the partial state worse. This matches several other forum reports that were resolved by a staff-side reprovision/rebuild, with Bots, files, and logins preserved. I suspect the shared machine ran out of memory (multiple bots with browsers open at once).
Could someone please server-side reprovision / recover this computer? Almost none of my bots can work without Shell.
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Where does the bug appear? Something else — Grok Bot shared Agent Computer (box) / Terminal & commands
Describe the Bug The Grok Bot shared computer (box) has been fully wedged since 2026-10-05. Every Shell command hangs and times out (even echo times out after 840s). The desktop renders but the terminal stays black and the execution layer never comes up. Almost none of my bots can work without Shell.
Steps to Reproduce
Open Grok Bot (stable 0.66.0), box already unreachable for Shell.
“Update Grok Bot’s Computer” → shows “already up to date”, won’t reinstall.
“Reset Grok Bot’s Computer” → stalls mid-reset, never finishes.
“Recover” → not offered on desktop or iPhone.
Fully quit (Cmd+Q) and reopen on every device → no change.
Expected Behavior Shell/box should come back after Update or Reset, or a Recover option should be available. Instead all three fail and there’s no self-serve recovery left.
Operating System: MacOS
Version Information: Grok Bot desktop app, stable 0.66.0
Additional Information
I have already followed the troubleshooting steps suggested by the AI support assistant at [email protected] (fully quit and reopen, check for Recover, don’t re-run Reset), and none of them worked. Matches several other forum reports resolved by a staff-side server-side reprovision/rebuild (Bots, files, logins preserved). Suspected cause: shared machine out of memory (multiple bots with browsers open). Support ticket: T-G71979. Conversation ID: 2cd41e79-dfa3-4cf7-8b86-9beb3acea115. Please server-side reprovision.
Does this stop you from using Cursor? Yes — unusable.
My Grok Bot shared computer (box) has been fully wedged since 2026-10-05. Every Shell command hangs and times out (even echo times out after ~840s at spawn). The desktop can render, but the terminal stays black and the execution layer never comes up. File Read sometimes works; Shell never does. Almost none of my bots can work (nightly backups, research jobs, health checks all blocked). Desktop app is stable 0.68.1.
Steps to Reproduce
Open Grok Bot desktop (stable 0.66.0) on Mac, same account also tested on iPhone.
Ask any bot to run a Shell command (e.g. echo ok / date).
Observe: Shell tool call hangs and times out (~840s); no stdout.
Open Settings → Updates → Grok Bot’s Computer:
Update shows “already up to date” and will not reinstall.
Recover is not offered on desktop or iPhone.
Reset stalls mid-reset and never finishes.
Fully quit (Cmd+Q) and reopen on every device → no change.
Followed all steps from AI support on ticket T-G71979 (quit/reopen, prefer Recover, stop pressing Reset/Update) → still broken.
Expected Behavior
Shell should start, or Recover/Update should restore a usable computer. When self-serve fails, the computer should be recoverable server-side without leaving it in a partial state.
Account: [email protected] . Support ticket: T-G71979. Conversation ID: 2cd41e79-dfa3-4cf7-8b86-9beb3acea115. Self-serve path is exhausted per [email protected] AI support. Similar forum cases were fixed by staff server-side reprovision/rebuild (Bots/files/logins preserved). Suspected cause: shared machine OOM (many bots / browsers). Please do not ask me to press Reset/Update again. Request: server-side reprovision of this computer for this account.
My Grok Bot shared computer has been broken since Oct 5. Pretty much every Shell call just hangs. Shared computer’s desktop can show a black terminal window, but nothing actually runs. Almost all my bots are stuck because of this.
Steps to Reproduce
Ask a bot to do any task that needs shell, the bot keep showing working but response nothing
Hey @karlarso_Z@karlarso, your follow-up posts got caught by our spam filter coz of repeated postings. That’s why they disappeared and why you couldn’t post from your first account. That’s sorted now, and I’ve merged all your posts into this thread so everything is in one place.
Your Bots, files, and logins are still there. The trouble is that anything on the computer that needs to start a new process, like Shell or the terminal, gets stuck, and it comes back on each fresh computer. That’s why Update and Reset haven’t cleared it. Please hold off on Reset, Recover, and Update for now.
I’m working on getting this fixed on our side, and two things would help:
Around Oct 5 or 6, did you or any of your Bots change the computer’s shell startup files (~/.bashrc, ~/.bash_profile, or ~/.profile), or set up something that runs whenever a terminal opens, like a backup or health-check script?
If you’re not sure, ask one of your Bots to open those three files directly with its file tools (not through Shell, which will hang) and tell you whether anything looks recently added. You can describe what you find here, no need to paste the full contents.
Here’s what I found by reading the files directly (no Shell):
~/.bash_profile — missing (doesn’t exist).
~/.profile — mostly stock Debian login setup. It sources ~/.bashrc, then adds ~/bin and ~/.local/bin to PATH, and loads nvm (~/.nvm/nvm.sh). Nothing that looks like a backup or health-check loop.
~/.bashrc — mostly stock, plus a few custom bits at the bottom:
Grok CLI path + completions
~/bin on PATH
nvm again
This line is the standout: it runs /home/box/bin/ts-up.sh on every interactive bash start (stdout/stderr discarded)
That script tries to keep Tailscale up: it runs sudo … tailscale status, and if that fails it starts tailscaled with sudo, sleep 2, then sudo … tailscale up. If sudo or Tailscale stalls, an interactive shell would sit there forever. (Non-interactive bash should exit .bashrc early before that line; login shells still load nvm from .profile after sourcing .bashrc.)
I can’t see file dates without Shell, so I can’t confirm whether this was added around Oct 5–6, but the Tailscale auto-start on shell open is the only non-stock “runs whenever a terminal opens” hook I found.
I might have asked the bot to set up tailscale autostart during Oct 5-6. Also I have a daily backup script
Hi @mohitjain , update from my side. Shell is working again. The root cause was the Tailscale autostart line in ~/.bashrc: Tailscale on the box had lost its login, so every new shell hung on sudo tailscale up waiting for auth. I’ve made that script non-blocking and re-authenticated Tailscale, and everything works now.
One last request: could you please make sure Reset and Update work normally on this computer and won’t wedge it again? Reset previously got stuck halfway, and Update didn’t recover it.
Thanks a lot for the pointer about shell startup files, that was the key.
