Grok Bot 0.68.1 - "Bot failed to respond" loop (Persistent across new bots)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

App Version: Grok Bot 0.68.1 Desktop App
Latest Affected Request ID: cbe002e9-e68a-47e2-ae0b-ac3d756b4ad1

Issue Description:
I am experiencing a persistent “Something went wrong while generating the reply. Try again” error in the standalone Grok Bot desktop application. The app successfully assigns a Request ID for each prompt, but completely fails to stream or print any text response.

Troubleshooting Steps Already Attempted:

  • Performed a full “Reset Grok Bot’s Computer” hardware wipe.
  • Disconnected from my corporate/work VPN and tested on a standard local connection.
  • Created a completely new bot from the sidebar. The new bot instantly throws the exact same “failed to respond” error on its very first prompt (“hello”).
  • Checked the main Cursor IDE application, which is working perfectly fine (isolated solely to the Grok Bot runner/container framework).

It looks like my account container is caught in a “Ghost Boot” state where the global reset changes the hardware code but retains a locked/corrupted authentication token on the backend.

Steps to Reproduce

  1. open grokbot app
  2. enter chat with any bot
  3. type a message

Expected Behavior

it should reply :slight_smile:

Operating System

MacOS

Version Information

Version: 0.70.2
Built: 2026-10-11T05:25:19.548Z
Release Track: stable
OS: darwin

For AI issues: add Request ID with privacy disabled

cbe002e9-e68a-47e2-ae0b-ac3d756b4ad1

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @Chris_Doyle, thanks for the report and for trying all of those steps.

We looked into this, and the failures aren’t coming from your computer or your login. Grok Bot replies are being stopped because your team’s trial usage limit has been reached. Grok Bot currently shows that as the generic “Something went wrong” message instead of a clear notice, which is why the Reset and the new bot didn’t help. The Cursor IDE keeps working because it can still use Cursor’s own models after the limit.

I’ve passed both the blocked replies and the unclear message on to the team. To get Grok Bot replying again in the meantime, please reach out to your team admin or your account contact about extending or converting the trial.

9

Ah i see! Thank you for checking so quickly - I appreciate that!