Since about 13:25 on 1 Nov 2026 (UTC+8), my Grok Bot cloud computer can’t run anything. Chat still works, but every Shell command (even echo ok or hostname) never starts and times out after 14 minutes. Screenshots time out the same way. About 60 bots share this computer, and every one of them is blocked. The last successful startup health check was 1 Nov at 17:41 (UTC+8). It started right after an X Subscription account merge that combined two accounts, each with a primary bot named GaGa.
What I’ve tried:
Update Bot’s Computer. It finished, but nothing changed.
Fully quitting and reopening the app.
Check for Updates. The app was already up to date.
I have not used Reset or Recover, because support said not to.
Timeline with support (ticket T-I94184, times UTC+8):
1 Nov 19:30: Reported the issue with links to the existing forum threads on merges leaving the computer paused (175957 and 175510).
1 Nov 19:39: Support couldn’t see or restore the computer. They asked me to confirm the signed-in account and whether other bots are affected. I confirmed: right account, all bots affected.
2 Nov 10:02: Support called it a “known issue”, caused by a line in the startup files that starts a program in the background. Their fix: read .profile and .bashrc without Shell, comment out that line, run Update Bot’s Computer, then test echo ok.
My bots read .bashrc fine. Line 20 starts the persistent-services watchdog in the background, with its output already sent to /dev/null. Reading .profile hangs for the full 14 minutes every time.
2 Nov 17:09: Support took back the “known issue” diagnosis, said not to touch the .bashrc line, and asked me to read .profile again.
I asked them to just move the bot to a fresh computer, since my data is backed up. At 20:46 support said they can’t move it, said again not to use Reset, and suggested an app update and another .profile read. They added: “If that file read also hangs, I don’t have another step I can take from this chat.”
The .profile read hung again (the second 14-minute timeout), while .bashrc read instantly in the same session. I asked for escalation to engineering.
21:14: Support had no fix and could give no timeline. They only asked what Update Bot’s Computer showed (it finished) and whether the app had an update (it didn’t).
21:38, the latest reply: “I don’t have another fix I can take from this chat, and I can’t move your Bots to a new computer or confirm that anyone is working on this.”
Where it stands: support can’t fix it, can’t move it, won’t confirm escalation, and tells me not to use Reset. That leaves no path to recovery from my side. Has anyone had a merged-account computer actually restored? Can staff please pick up T-I94184?
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!
Hey @Anudorannador, I’ve picked this up. Thanks for holding off on Reset and Recover. This needs a fix on our side, because Update, Recover and Reset all bring back the same stuck startup file.
The quickest fix is for us to give your bots a fresh, empty computer. That removes everything saved on the computer itself, including files, browser logins and installed apps. Your bots and chats stay.
Since your data is backed up, reply here to confirm and I’ll go ahead. When you copy your backup back, leave out .profile and .bashrc, since a line in one of those is what got stuck. If you’d rather keep the computer’s files, tell me and we’ll ask the team to look at a fix that keeps them, though that will take longer and I can’t give you a timeline.
I’m having the same problem with my Grok Bot cloud computer. It has been stuck on “The computer is still starting up. Try again in a moment.” since 08:00 UK time (GMT) on Wednesday 28 Oct, so it’s been offline for over 5 days now (about 130 hours).
Here are my details in case they help staff find a pattern:
What fails: every command, file read and screenshot gives “Command failed to spawn: The computer is still starting up.” Chat and connectors still work, but anything that needs the computer is down, for all my bots.
Where: it happens on both the PC and phone apps, with no other error shown.
What I’ve tried: one Reset before contacting support. Recover and Update both stall and never finish. I have no Privacy Mode option in settings, and the app is up to date.
Support: ticket T-I59185, opened 28 Oct at 10:16. Support asked me not to Reset or Update again and passed it to the team. I’ve had no reply since 28 Oct at 10:44, despite follow-ups on 28, 29 and 30 Oct and 1 Nov. I’ve also said I’m happy to lose all my bots and data if a full reset fixes it.
From other threads here, it looks like staff have had to fix this on the backend, followed by a full quit and reopen of the app. Hopefully they can sort both of ours soon.