Grok Bot 0.44.0 — Bot failed to respond on Mac + iPhone (no requestId); please recover Agent Computer

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Every message to any Grok Bot on this account fails with:

Bot failed to respond / Something went wrong while generating the reply. Try again.

Chinese UI (exact): 「Bot 未能回复 / 生成回复时出错了。请重试。」

This is not one bad chat. It hits every bot on the account, including a short “?” / “1” / “在吗？” with no tools, connectors, search, or computer-use. The same account also fails on iPhone. Desktop and phone share the same dead Agent Computer.

Failed user messages stay local only: they have a clientNonce but no requestId / sendAcceptance ack. Last successful replies were 2026-09-06 19:47 CST. First failure 2026-09-07 16:28 CST. Desktop app was already on 0.44.0 (updated ~02:13 CST that morning). Account still shows signed in; the Agent Computer host still answers TLS (GET / → ALB 404 The request could not be routed, which is normal). Cursor status page shows Grok Bot operational.

This matches today’s thread Grokbot | can not send msgs; agents' virtual machine is still visible and the earlier staff-confirmed “shared cloud computer stuck” reports (170661, 170731, 170235).

Please recover / rebuild the Agent Computer on the backend for this account. I have not clicked Reset / Recover / Update, per staff guidance that a stuck computer cannot be fixed from the client and Reset can leave a partial state.

Steps to Reproduce

  1. Open Grok Bot 0.44.0 on macOS (or the iOS app, same account).
  2. Open an existing bot or any bot on the account.
  3. Send a short message such as “?” or “hello” with no tools.
  4. Within a few seconds the red banner appears.
  5. Fully quit (Cmd+Q) and reopen — same failure.
  6. Repeat on iPhone with the same account — same failure.

Expected Behavior

Short messages should get a reply on both Mac and iPhone. If the shared Agent Computer is stuck, please recover it server-side.

Operating System

MacOS

Version Information

  • Grok Bot desktop: 0.44.0 (stable), bundle com.anysphere.sand
  • iOS Grok Bot: same account, also fails
  • Timezone: Asia/Shanghai (CST)

For AI issues: add Request ID with privacy disabled

Failed sends have no requestId. Conversation IDs:

  • 0f4399d5-b29a-4e1b-bf80-765abba2043a
  • 24542bc8-480d-447a-802a-dddf6cfc18e9

Additional Information

Tried (did not fix): fully quit/reopen desktop, retry short messages, confirmed iPhone also dead.

Did not try: Reset / Recover / Update Agent Computer, sign out, reinstall.

Please do not ask me to keep hitting Reset.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

@deanrie follow-up: still broken as of 2026-09-08 CST.

The official incident “Grok Bot computers unreachable for some users” is marked resolved, but this account still cannot get any bot reply on Mac 0.44.0 or iPhone. Short messages (“?”, “hello”) still show “Bot failed to respond / Something went wrong while generating the reply.” Failed sends still have no requestId.

I have not clicked Reset / Recover / Update.

Please recover the Agent Computer on the backend.

Conversation IDs:

  • 0f4399d5-b29a-4e1b-bf80-765abba2043a
  • 24542bc8-480d-447a-802a-dddf6cfc18e9
8

Hey @Alex_Such,

You’ve read this right: it’s on our side, not the 0.44.0 update and not your network. Late Saturday evening UTC (early Sunday morning your time), a group of Grok Bot computers lost their connection to our servers, and yours is one of them. That’s why every bot fails on both Mac and iPhone, and why the failed sends never get a request ID. The reply never starts.

The broader incident being marked resolved doesn’t mean every affected computer is back yet, and yours is still in that set, so you’re right it isn’t fixed for you. Please keep not pressing Reset / Recover / Update, and don’t sign out or reinstall. We’re working to get the affected computers back on our side, and yours is on that list. I’ll update this thread as soon as there’s more. No need to keep retrying in the meantime, and once yours is back please let me know how everything looks.