# Bot failed and does not respond **URL:** \ **Category:** Bug Reports\ **Tags:** grok-bot\ **Created:** [September 23, 2026, 12:20am UTC](https://forum.cursor.com/t/bot-failed-and-does-not-respond/172716 "2026-09-23T00:20:50Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Bernie\_Ladoucur](https://avatars.discourse-cdn.com/v4/letter/b/8e8cbc/32.png) [@Bernie\_Ladoucur](https://forum.cursor.com/u/Bernie_Ladoucur)\ **Post date:** [September 23, 2026, 12:20am UTC](https://forum.cursor.com/t/bot-failed-and-does-not-respond/172716/1 "2026-09-23T00:20:51Z")
Bot fails when asking anything in the pronp. This is the message I recive. ![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/5/757199c552d8cb7762bb409d955629387798441a.png) ## Please recover / reprovision the Agent Computer on the backend. Do not ask me to Reset again. ## Please keep bots, chats, files, and logins. ## Every bot (including Bambi) fails with “Bot failed to respond / Something went wrong while generating the reply.” Duration: ~2 days. Same on every device I tried. Already done: full quit/reopen, Check for Updates, Reset Grok Bot’s Computer, new chat, logout/login. Please recover / reprovision the Agent Computer on the backend. Do not ask me to Reset again. Please keep bots, chats, files, and logins. Account email: [bernieladouceur41@gmail.com](mailto:bernieladouceur41@gmail.com) App version + OS: [e.g. 0.xx Windows / iOS / Android] Usage: [percent remaining, used 7%, left is 93% ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [September 23, 2026, 12:20am UTC](https://forum.cursor.com/t/bot-failed-and-does-not-respond/172716/2 "2026-09-23T00:20:58Z")
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](http://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 > > ```auto > 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! ---
**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\ **Post date:** [September 23, 2026, 12:31am UTC](https://forum.cursor.com/t/bot-failed-and-does-not-respond/172716/6 "2026-09-23T00:31:11Z")
Hi @Bernie_Ladoucur I’ve reset your Grok bot box from our side. Please restart the Grok Bot app, update the app if there’s an update available, and let us know if the issue persists. Cheers! ---
**Author:** ![Bernie\_Ladoucur](https://avatars.discourse-cdn.com/v4/letter/b/8e8cbc/32.png) [@Bernie\_Ladoucur](https://forum.cursor.com/u/Bernie_Ladoucur)\ **Post date:** [September 23, 2026, 12:35am UTC](https://forum.cursor.com/t/bot-failed-and-does-not-respond/172716/8 "2026-09-23T00:35:26Z")
Same thing. I logged out and logged back in, I checked for updates. I have the latest update. This is the message i still get. ![image](https://us1.discourse-cdn.com/cursor1/original/3X/d/7/d704cd60ff693cbe68e3d02b7ecc04710816bd3b.png) ---
**Author:** ![Bernie\_Ladoucur](https://avatars.discourse-cdn.com/v4/letter/b/8e8cbc/32.png) [@Bernie\_Ladoucur](https://forum.cursor.com/u/Bernie_Ladoucur)\ **Post date:** [September 23, 2026, 1:38am UTC](https://forum.cursor.com/t/bot-failed-and-does-not-respond/172716/9 "2026-09-23T01:38:17Z")
> [@Bernie\_Ladoucur](#): > > Same thing. I logged out and logged back in, I checked for updates. I have the latest update. This is the message i still get. > > ![image](https://us1.discourse-cdn.com/cursor1/original/3X/d/7/d704cd60ff693cbe68e3d02b7ecc04710816bd3b.png) Same thing. I logged out and logged back in, I checked for updates. I have the latest update. This is the message i still get. ![image](https://us1.discourse-cdn.com/cursor1/original/3X/d/7/d704cd60ff693cbe68e3d02b7ecc04710816bd3b.png) ---
**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\ **Post date:** [October 20, 2026, 10:25pm UTC](https://forum.cursor.com/t/bot-failed-and-does-not-respond/172716/10 "2026-10-20T22:25:25Z")
Hi @Bernie_Ladoucur, sorry we dropped this I’m just following up on old threads. From our side, it looks like your bot has been replying normally since early October. Can you confirm everything is working for you now? If you see the “Bot failed to respond” message again, reply here, and we’ll take another look.