Grok Bot cloud computer stuck starting; please check account merge/linking

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

My Grok Bot cloud computer is stuck starting and I cannot get it to restart successfully. The Bot can still reply in chat, but cannot access its own computer.

I asked it to inspect its shell startup files using the file-reading tool (not Shell). It reported that both attempts returned “还在启动中” (“still starting up”). None of the files were read and nothing was modified. It stopped retrying.

Possible account-linking context, NOT a confirmed cause: I recently went through Cursor/Grok account linking/merge attempts. Different sign-in methods with the same email previously showed different plans. A merge attempt displayed “Accounts couldn’t be merged. Review the selected accounts and try again.” Access/usage later became available after signing in through Grok. I do not know whether the merge completed correctly or whether the current cloud computer is attached to the intended identity. Please investigate rather than assume this is the cause.

Steps to Reproduce

  1. Open my existing Grok Bot conversation.
  2. Ask the Bot to read files on its own cloud computer.
  3. It reports that the computer is still starting up; two attempts failed.
  4. The restart attempt has not restored access. Exact onset and restart duration are not yet confirmed.

Expected Behavior

The existing cloud computer should finish starting and allow file reads and normal tasks. Please check the backend startup/execution state and the account-to-computer association. Prioritize preserving existing Bots, conversations, files and logins. Please explain any risk of data loss and obtain my approval before wiping or rebuilding in a way that loses data.

Operating System

Windows 10/11

Version Information

Grok Bot desktop on Windows. Exact app version not yet collected; I can provide it if needed.

Additional Information

Issue still present on October 24, 2026 (Asia/Shanghai). I cannot confirm a Tailscale or shell startup-file issue because the files could not be read. Please advise a safe recovery path and whether staff-side intervention is required. I am keeping private account identifiers out of this public post and can provide them through official support.

Does this stop you from using Cursor

No - Cursor works, but with this issue

10

Hey @wangxiaohan,

Good news on the stuck computer: it was paused by the account merge that started shortly before you posted, and that merge has now finished. While a merge moves Grok Bot between accounts, it pauses the bot’s computer and copies its files over. During that window the bot can still chat, but anything that needs the computer is refused, which is why it kept saying it was still starting up and a restart didn’t help.

The merge completed a few minutes after you posted. Your bots, conversations and computer files were copied to the account you merged into, not wiped, and the bot’s computer on that account has been running normally since then. The earlier “Accounts couldn’t be merged” message came from a separate, earlier attempt, and everything now sits on the one merged account.