Grok Bot: one bot silent after image_gen — restart this bot's runner only, do NOT Reset

Support Bug Reports
, ,
1

Describe the Bug

One specific Grok Bot stopped responding after an image_gen / drawing tool call. Other bots on the same Agent Computer still work. This bot’s desktop is operable when I take over.

Messages in this bot’s original conversation do not get a reply on desktop and mobile. “Stop now” also gets no reply. Sending in this conversation currently fails.

This is NOT a weekly usage-limit case. SuperGrok Plus usage is still available.

Please restart ONLY this bot’s runner.
Do NOT Reset / rebuild / Update the Agent Computer.
Do NOT delete the bot.
Conversation history is extremely important and MUST remain on the original bot.

Steps to Reproduce

  1. Open Grok Bot (desktop and mobile), SuperGrok Plus.
  2. Open bot: 世界でいっちばんかわいい愛ちゃん
  3. Conversation / Agent ID: e62dac71-7430-4632-aa38-122a861711f8
  4. Bot was asked to draw a picture (image_gen / command, not a webpage).
  5. After that tool call, the bot never replied.
  6. Send “Stop now”, “hello”, or any short message in the same conversation.
  7. Result: no bot reply. On both desktop and mobile, messages in this conversation fail to send / never get a response.
  8. Take over this bot’s Agent Computer desktop: it is operable.
  9. Other bots on the same computer still reply normally.
  10. Duplicate of this bot can talk, but has no conversation history (expected). Original bot must be kept.

Expected Behavior

The original bot should reply again in the same conversation after the hung image_gen turn is cleared.

Please restart only this bot’s runner so the original chat continues.
Do not Reset / rebuild the Agent Computer.
Do not delete the bot.
Do not create a replacement computer.
History must stay on the original bot.

Operating System

Windows 10/11

Version Information

Grok Bot desktop
Version：0.53.0

For AI issues: which model did you use?

Grok Bot default (not Cursor Sonnet). Bot used image_gen / drawing tool, then went silent.

For AI issues: add Request ID with privacy disabled

Conversation / Agent ID: e62dac71-7430-4632-aa38-122a861711f8
No requestId on failed sends (messages do not complete).

Additional Information

Plan: SuperGrok Plus.
Usage remaining: yes (checked in Grok Bot Settings → Usage). Not a quota issue.

Bot name: 世界でいっちばんかわいい愛ちゃん
Conversation / Agent ID: e62dac71-7430-4632-aa38-122a861711f8

Hard requirements:

  • Restart this bot’s runner only
  • Do NOT Reset / rebuild / Update the Agent Computer
  • Do NOT delete the bot
  • Conversation history MUST remain on the original bot

Already tried with no fix:

  • Stop now
  • Short messages (hello)
  • Take over computer (desktop works)
  • Update Agent Computer (other bots still fine)
  • New chat / group with this bot
  • Duplicate bot (copy works but history is missing; original must be restored)

Same failure on desktop and mobile.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Thanks for restoring the account and the topic.

Quick recap in case this got buried while the post was hidden:

One bot stopped after an image_gen / drawing call. Other bots on the same computer still work, and I can take over this bot’s desktop. Usage is still available, so this doesn’t look like a weekly limit.

Could you restart only this bot’s runner?

Please don’t Reset or rebuild the Agent Computer, and please don’t delete the bot — the original conversation history needs to stay on it.

Bot: 世界でいっちばんかわいい愛ちゃん
ID: e62dac71-7430-4632-aa38-122a861711f8

8

Update: the original bot is responding again in the same conversation. History is still there.

No further action needed — please don’t Reset or rebuild the Agent Computer.

Thanks for restoring the topic earlier.

9

Hey, glad the bot is replying again and the history is still there. You don’t need to do anything else, and you were right not to run Reset since it really wasn’t needed in this case.

Quick reason: the part that processes this bot’s replies runs on our side, not on the Agent Computer. That’s why the computer looked fine and other bots kept responding. Only the background step for this specific bot got stuck, and any messages after it got queued behind it. The chat history is stored on our side, so it never went anywhere.

We’re tracking this issue. If this bot goes quiet again after a tool call, send the time of the last message and the bot ID here and I’ll take a look.