# Grokbot failing to respond

**URL:** <https://forum.cursor.com/t/grokbot-failing-to-respond/171698>\
**Category:** Bug Reports\
**Tags:** remote-control, grok-bot\
**Created:** [September 15, 2026, 4:46am UTC](https://forum.cursor.com/t/grokbot-failing-to-respond/171698 "2026-09-15T04:46:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stoplion123](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/stoplion123/32/3160_2.png) [@stoplion123](https://forum.cursor.com/u/stoplion123)\
**Post date:** [September 15, 2026, 4:46am UTC](https://forum.cursor.com/t/grokbot-failing-to-respond/171698/1 "2026-09-15T04:46:37Z")

</div>

![image](https://us1.discourse-cdn.com/cursor1/original/3X/4/a/4afdea8f6b35cba0134c33a4336d9e822c507671.png)

first the mobile app said it can’t reach my computer then i started to outright fail. what is going on?

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/c/5/c53f8ee0ff54e72cb17a8256785f51766c7ec8ea.png)

---

<div class="post-metadata">

**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 15, 2026, 4:46am UTC](https://forum.cursor.com/t/grokbot-failing-to-respond/171698/2 "2026-09-15T04:46:45Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [September 15, 2026, 8:06am UTC](https://forum.cursor.com/t/grokbot-failing-to-respond/171698/6 "2026-09-15T08:06:50Z")

</div>

Hey @stoplion123, thanks for the report, and sorry about that.

Both messages came from the same thing: the cloud computer that runs your Bots got stuck on our side. It kept telling our servers it was healthy, so it was never replaced automatically, but every real request to it was failing. That is why the phone said it couldn’t reach your computer and why Crombo stopped answering.

The Reset you ran from the desktop app a couple of minutes after posting did the right thing. A fresh computer came up with your Bots and files preserved, and Crombo replied successfully about five minutes later, so it should be working now.

On the phone, if it still shows “Can’t reach your computer”, swipe the Grok Bot app closed and reopen it once so it picks up the new computer.

Let us know if it’s working again!