# Chief agent Grok bot failing to respond

**URL:** <https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915>\
**Category:** Bug Reports\
**Tags:** grok-bot\
**Created:** [September 7, 2026, 2:59pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915 "2026-09-07T14:59:50Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Diazb123](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@Diazb123](https://forum.cursor.com/u/Diazb123)\
**Post date:** [September 7, 2026, 2:59pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/1 "2026-09-07T14:59:51Z")

</div>

### Where does the bug appear (feature/product)?

Grok Bot

### Describe the Bug

Subject: Grok Bot — All Bots Failing on Mac & iOS

Grok Bot is currently unusable for our account. Our primary Bot and other Bots are returning “Bot failed to respond”, including on both macOS and iOS.

Before this, the Mac desktop was also unable to load conversations while iOS still worked. We have already tried restarting the app, Retry, a separate iPhone hotspot, and confirming Privacy Mode.

Because similar reports appear to involve a stuck shared Agent Computer, could you please check our Agent Computer/backend state and manually recover or reattach it if necessary?

Please do not reset or replace our Agent Computer without our approval. We have significant Bot configurations, files, routines, credentials, and workflows that we need to preserve.

### Steps to Reproduce

Issue is ongoing - failing to respond

### Operating System

MacOS  
iOS

### Version Information

For grok bot

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [September 7, 2026, 5:13pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/5 "2026-09-07T17:13:20Z")

</div>

Hey, thanks for the detailed report. Main point first: this isn’t anything on your Mac, iPhone, or network. Some Grok Bot Agent Computers, including yours, currently have an issue on our side where every message fails with “Bot failed to respond” on all devices, even though the Agent Computer is still visible. We’re tracking it. The earlier situation where Mac wouldn’t load conversations but iOS worked was a separate issue and it’s already fixed.

For now, please don’t click Reset or Update, don’t log out, and don’t reinstall the app. Your bots, files, routines, credentials, and workflows on the Agent Computer are safe, and we want to keep them that way. The recovery is handled on our side and your data will be preserved. I’ve added your account to the recovery list, so you don’t need to do anything.

Once it’s restored, just close and reopen the Grok Bot app and resend your last message.

---

<div class="post-metadata">

**Author:** ![Bradley\_Street](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bradley_street/32/120126_2.png) [@Bradley\_Street](https://forum.cursor.com/u/Bradley_Street)\
**Post date:** [September 7, 2026, 9:15pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/7 "2026-09-07T21:15:40Z")

</div>

Also having this issue.

---

<div class="post-metadata">

**Author:** ![au6ust](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/au6ust/32/120212_2.png) [@au6ust](https://forum.cursor.com/u/au6ust)\
**Post date:** [September 8, 2026, 3:52am UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/8 "2026-09-08T03:52:56Z")

</div>

Also impacted by this.

---

<div class="post-metadata">

**Author:** ![yuzamesan3](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuzamesan3/32/120217_2.png) [@yuzamesan3](https://forum.cursor.com/u/yuzamesan3)\
**Post date:** [September 8, 2026, 4:54am UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/9 "2026-09-08T04:54:27Z")

</div>

Also having this issue.

---

<div class="post-metadata">

**Author:** ![au6ust](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/au6ust/32/120212_2.png) [@au6ust](https://forum.cursor.com/u/au6ust)\
**Post date:** [September 8, 2026, 7:26pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/11 "2026-09-08T19:26:32Z")

</div>

@deanrie is there any update on this? Grok Bot is completely down for me due to this, and I was in the middle of some big projects with it!

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [September 11, 2026, 6:26am UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/12 "2026-09-11T06:26:16Z")

</div>

@au6ust @Diazb123 @yuzamesan3 your computers are back online with your bots, files, and routines intact. Please fully quit the Grok Bot app (Cmd+Q on Mac, force-close on iOS, not just closing the window) and reopen it, then resend your last message. It should go through now.

@Bradley_Street yours needs a fresh reopen to come back. Fully quit and reopen the app, and if your bots and history don’t reappear, reply here and I’ll check your account directly.

Sorry for the disruption. If anything still fails after a full restart, let me know.

---

<div class="post-metadata">

**Author:** ![Mario\_Murgado\_Jr](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mario_murgado_jr/32/120684_2.png) [@Mario\_Murgado\_Jr](https://forum.cursor.com/u/Mario_Murgado_Jr)\
**Post date:** [September 12, 2026, 7:03pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/13 "2026-09-12T19:03:49Z")

</div>

Also impacted. Started today around 9:30am ET, all bots, Grok Bot 0.47.0 on Windows. Same error on desktop and mobile.

Haven’t touched Reset, Update, logout, or reinstall per the guidance above. Could I be added to the recovery list?

One detail in case it’s useful: Settings \> Updates shows “Backup not ready” in the status bar, and the Network Debugger passes every check including to the Agent Computer.

---

<div class="post-metadata">

**Author:** ![Mario\_Murgado\_Jr](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mario_murgado_jr/32/120684_2.png) [@Mario\_Murgado\_Jr](https://forum.cursor.com/u/Mario_Murgado_Jr)\
**Post date:** [September 12, 2026, 7:34pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/14 "2026-09-12T19:34:12Z")

</div>

@mohitjain could you kindly at your convenience assist me with the same reported error in this thread? Thank you!

---

<div class="post-metadata">

**Author:** ![Diazb123](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@Diazb123](https://forum.cursor.com/u/Diazb123)\
**Post date:** [September 15, 2026, 9:10pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/15 "2026-09-15T21:10:29Z")

</div>

@mohitjain @deanrie — this problem has returned for me on September 15  
after the recovery confirmed here on September 11.

On the Mac desktop app, messages to Chief of Staff appear in the  
conversation but receive no response, including a simple greeting. The  
app reports that the bot stopped without replying. This is  
interrupting my work again. I have not yet verified the current impact  
on other bots or mobile.

Could you please check my account again and escalate this recurrence  
to the team that handled the previous recovery? Please preserve the  
existing bots, files, routines, and history during any recovery. I  
have also emailed support today. Please confirm that this recurrence  
is being investigated and let me know the next step.

Thank you,  
Diaz

---

<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 16, 2026, 11:45am UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/16 "2026-09-16T11:45:12Z")

</div>

Split this topic on September 16, 2026, 11:45am UTC

6 posts were merged into an existing topic: [Some of the bots became unresponsive (failed to send on my messages to them)](https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858/42)

---

<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:** [October 16, 2026, 12:34pm UTC](https://forum.cursor.com/t/chief-agent-grok-bot-failing-to-respond/170915/18 "2026-10-16T12:34:44Z")

</div>

Closed on October 16, 2026, 12:34pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
