Grok Bot fails to generate replies; Agent Computer screen is still visible

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Every message to Grok Bot fails with an error that it cannot generate a reply
(Bot failed to respond / Something went wrong while generating the reply).

This happens on simple messages such as “hello”, not only tool/computer-use tasks.
It affects existing conversations and a newly created bot as well.

The Agent Computer / VM screen is still visible.
I can see the desktop (and the box looks reachable), but the bot never generates a reply.
So this does not look like a local app crash or a “can’t reach computer” issue.

Steps to Reproduce

  1. Open Grok Bot.
  2. Open an existing bot (or create a new one).
  3. Send a short message with no tools/connectors/memory, e.g. “hello”.
  4. The error appears within a few seconds.
  5. Open Agent Computer — the VM screen is still visible.

Expected Behavior

The bot should generate a reply. A simple “hello” should work even if computer-use is not needed.

What I already tried

  • Fully quit and reopen Grok Bot (not just closing the window)
  • Sent a short test message in a new chat
  • Created a new bot — same failure
  • Agent Computer screen remains visible

I have not repeatedly reset the computer, to avoid putting the box into a partial state.

Additional context

This matches previous reports where the account’s shared cloud computer was stuck on the generation side while the desktop view still loaded. All bots share one computer, which would explain why a new bot fails the same way.

Please recover/rebuild the Agent Computer on the account side if needed.

Environment

  • Product: Grok Bot
  • OS: [macOS / Windows / Android / iOS]
  • Grok Bot version: [e.g. 0.43.0]
  • Account email: [your Cursor account email]
  • Conversation ID (if available): [paste ID]
  • Approximate time the issue started: [timezone, e.g. 2026-09-07 09:10 KST]
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

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!

9

Hey @Eric_Han, good news: your Agent Computer was restored on our side early this morning (around 05:20 UTC), and from what I can see your bots have been replying normally since then. Restart Grok Bot and let us know if you see differently!