# Grok Bot: Takeoff App + Chief of Staff silent / Failed to respond — restart these bots’ runners only, do NOT Reset

**URL:** <https://forum.cursor.com/t/grok-bot-takeoff-app-chief-of-staff-silent-failed-to-respond-restart-these-bots-runners-only-do-not-reset/172354>\
**Category:** Bug Reports\
**Tags:** grok-bot\
**Created:** [September 19, 2026, 3:26pm UTC](https://forum.cursor.com/t/grok-bot-takeoff-app-chief-of-staff-silent-failed-to-respond-restart-these-bots-runners-only-do-not-reset/172354 "2026-09-19T15:26:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Justin\_Breiner](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Justin\_Breiner](https://forum.cursor.com/u/Justin_Breiner)\
**Post date:** [September 19, 2026, 3:26pm UTC](https://forum.cursor.com/t/grok-bot-takeoff-app-chief-of-staff-silent-failed-to-respond-restart-these-bots-runners-only-do-not-reset/172354/1 "2026-09-19T15:26:13Z")

</div>

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

Grok Bot

### Describe the Bug

Product: Grok Bot

Several Grok Bot agents on my multi-bot account are silent and not taking wakes. Please restart ONLY these bots’ runners. Do NOT Reset / Recover / Update the Agent Computer. Do NOT delete the bots. Keep conversation history.

Stalled bots (agent UUIDs):

1. Takeoff App — fae70738-ed6c-4471-b64d-c3e4bf3863a9
2. Chief of Staff — 10657a37-98b5-4703-9350-caef0f93c613

### Steps to Reproduce

Send user chat messages or priority agent-to-agent health pings to either of the two stalled bots listed above. They remain silent and do not respond.

### Expected Behavior

Please restart ONLY the runners for the two agent IDs above. Do NOT Reset / Recover / Update the Agent Computer, delete the bots, or remove conversation history.

### Operating System

Other

### Version Information

Grok Bot version: not provided; agent runner issue.

### For AI issues: which model did you use?

Not applicable — bot runner issue

### Additional Information

Other bots on the same account still reply (e.g. Genesis — 041ce7b4-607c-4017-95af-160ef61bf4a0), so this is a per-bot runner issue, not the whole shared VM.

Computer view is fine / not stuck on login. Shared computer was Updated earlier and box-doctor is healthy; these agents still do not respond to user chat or priority agent-to-agent health pings. Usage not exhausted.

Please restart ONLY the runners for the two agent IDs above.

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<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 20, 2026, 8:35am UTC](https://forum.cursor.com/t/grok-bot-takeoff-app-chief-of-staff-silent-failed-to-respond-restart-these-bots-runners-only-do-not-reset/172354/5 "2026-09-20T08:35:31Z")

</div>

Hi @Justin_Breiner

This issue should now be resolved. Can you check?

---

<div class="post-metadata">

**Author:** ![Justin\_Breiner](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Justin\_Breiner](https://forum.cursor.com/u/Justin_Breiner)\
**Post date:** [September 20, 2026, 2:12pm UTC](https://forum.cursor.com/t/grok-bot-takeoff-app-chief-of-staff-silent-failed-to-respond-restart-these-bots-runners-only-do-not-reset/172354/7 "2026-09-20T14:12:05Z")

</div>

All good now! Thanks!