Some of the bots became unresponsive (failed to send on my messages to them)

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

i have one master bot, i asked him to create a new bot. A couple messages in with the new bot, he became unresponsive. Messages to him failed to sync with my other devices and on reopening the app they show “failed to send”
I asked the master bot about the unresponsive bot, he thought a little then became unresponsive, also failed to send. I checked all the other bots and one other did the same, thought a little then became unresponsive.

I tried closing app on all devices and updating grokbot computer but those three bots still unresponsive.

I can still connect to the computer of each of those bots and it appears to be live.

Grok tells me you may be able to recover them.

Thanks!

Steps to Reproduce

i asked him to create a new bot. A couple messages in with the new bot, he became unresponsive. Messages to him failed to sync with my other devices and on reopening the app they show “failed to send”
I asked the master bot about the unresponsive bot, he thought a little then became unresponsive, also failed to send. I checked all the other bots and one other did the same, thought a little then became unresponsive.

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 0.44.0
Release Track: stable
OS: linux

Does this stop you from using Cursor

No - Cursor works, but with this issue

same

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

My Grok bot suddenly stopped responding.

Some bots are fine, but the Chief of Staff bot simply died and isn’t responsive at all. I tried resetting Grok bot’s computer, updated it to the latest version, updated the bot’s computer version but nothing seems to work.

Steps to Reproduce

No idea how to reproduce it, unfortunately. It simply just stopped working.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Grok Bot 0.53.0

For AI issues: add Request ID with privacy disabled

Last conversation ID: 69e632a3-8a5a-4abb-a65e-7a55621f996a

Does this stop you from using Cursor

No - Cursor works, but with this issue

I’m experiencing the same this morning.

Same :smiling_face_with_tear:

same…

same..

Same on my side as well.

Same here, I had already reset computer to fix. My bad, hoping for a quick solve.

me too, I can confirm its just the chief of staff that isnt responding

its a big issue on my account as well same issue and its stopped all work

Same here. CoS is not responding, other bots are responding fine. It’s been about an hour with this bot stuck in chat.
Stuck bot id: c7d07460-4072-44b9-bb00-7c173e2634d6

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot is failing to respond, the built in computer seems to be running fine, also it is processing an update which has been stuck on 43% for nearly an hour. Then it asks if I want to recover computer, if I choose yes the computer completes recovery however there is still no response from the agents

Steps to Reproduce

I have tried closing Grokbot but it is still stuck on updating. I have also chosen the recover computer option, It does this and completes fine but still no response from any agents

Expected Behavior

It should update, stuck on 43%, even after recovery no response from agents

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Grok bot version 0.53.0
Mac OS Tahoe 2.67

For AI issues: which model did you use?

Grok Bot

Does this stop you from using Cursor

No - Cursor works, but with this issue

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Chat is stuck on Connecting on Windows Grok Bot 0.53.0 and the iPad app (same account). Messages fail to send; Retry does nothing.

Computer view still works. I can use the remote desktop and terminal on grok-bot-vm-307022897 (us11.cursorvm.com). ls still shows files written at 17:46 CST on 2026-09-16.

Desktop client heartbeat: signedIn true, crashSeen false. Local TLS to api2.cursor.sh and us11.cursorvm.com succeeds.

Started about 17:56 CST 2026-09-16 mid-session (pennbot). Already tried full quit, relaunch, sign-out/in, Windows reboot.

Please repair the chat/session channel on the backend. Do not Reset the Agent Computer. The VM and files are healthy.

Weekly usage is 24 percent (not exhausted). On-demand 0 of 20 USD.

Steps to Reproduce

Open Grok Bot 0.53.0 on Windows, signed in.

Chat with an existing bot (pennbot) until the reply stops (here: ~17:56 CST 2026-09-16).

Send a short message (e.g. “hello”). It shows Send failed; Retry does nothing.

Fully quit (tray → Quit), reopen. UI stays on Connecting and chat never loads.

Open the same account on iPad. Same: no chat response.

Open Computer view: remote desktop and terminal work (box@grok-bot-vm-307022897:/workspaces). Files from 17:46 are still there.

This is account-side. Reboot / reinstall / Reset on the client does not recover chat.

Expected Behavior

After the Computer is reachable, chat should leave “Connecting”, load existing bots, and accept new messages. iPad should work on the same account.

Computer view working should mean chat works too. Failed sends should retry or show a real error, not hang.

No Reset should be required when the VM is already healthy.

Operating System

Windows 10/11

Version Information

Grok Bot 0.53.0 (stable)
OS: Windows 10.0.26340
Also: iPad Grok Bot app, same account
Agent Computer: grok-bot-vm-307022897

版本:0.53.0
发布通道:stable
操作系统:win32

For AI issues: which model did you use?

Grok Bot (pennbot). Not Cursor IDE / Sonnet.

For AI issues: add Request ID with privacy disabled

No requestId: failed sends never reached the backend (Send failed / Retry no-op).
Conversation ID (desktop sentry): d3d308df-8152-4f85-875a-ff27b35bd408

Additional Information

Please do NOT Reset or Recover the Agent Computer. VM is healthy; only chat is stuck on Connecting.

Windows plus iPad, same account.
Computer view: box at grok-bot-vm-307022897, path /workspaces
Files from 17:46 CST 2026-09-16 still present (PNGs, md, write_plan.py).
Need backend repair of the chat/session channel.

Does this stop you from using Cursor

No - Cursor works, but with this issue

I encounter the same issue.

seems like it is widespread

Same silent-bot issue here (Cursor Ultra / Grok Bot).

Two assistants froze in one day: one left usage_limit / resource_exhausted in automation logs (“included Grok Bot usage limit has been reached”); another hung after a long browser session waiting on WeChat QR / hand-back and never replied again. Poking did nothing — had to recreate the agent and migrate memory.

Desktop still gives almost no clear “weekly usage exhausted” banner, so it looks like a dead chat/computer and people reach for Reset. Please surface the limit loudly before bots go mute, and don’t accept messages that will never run.

Field note: 天智(TianMind) on X: "Cursor 里 Grok Bot 突然不说话,像死机? 我们实测至少两类: ① 撞上 included usage/周额度后助手不跑,桌面端几乎不提示 ② 长浏览器会话/等人扫码交还后像挂死 Cursor 论坛已有多人报,官方也确认:额度用尽后消息照收、助手不跑,缺醒目警告。别急着 Reset 电脑。 先自救:Settings → Usage;可开 On-Demand;少开高频空转的 routine。 https://t.co/Hu27hwYVU8" / X

i found a workaround. I created a new bot and asked him to check the unresponsive bot memory and tasks and become him. New substitute bots appear to be working fine

Hey everyone.

Thank you for the reports – we are investigating the issue and will update this thread.

4 Likes

i will not delete the unresponsive bots in case you need them for anything. Now they have the tag “unresponsive”
Thanks!!

Hello Dean, attaching the IDs and time stamps from my stuck bots:

  • Bot “Stalk Bot”, ID 93bfc8e5-2a5e-4459-abb2-efedc599e82d, Wednesday September 16, 12:23 PM Spain time.
  • Bot “SEO & AEO Desk”, ID 346aa49e-cb80-4147-a915-ea8b35bd84e8, time of last succesful message, Tuesday September 15, 15:09 Spain time.