# Grok Bot teammate unresponsive after long tool waits; recreated agent shows “Failed to send” until app restart + recreate **URL:** \ **Category:** Bug Reports\ **Tags:** terminal, chat, grok-bot\ **Created:** [September 17, 2026, 1:38pm UTC](https://forum.cursor.com/t/grok-bot-teammate-unresponsive-after-long-tool-waits-recreated-agent-shows-failed-to-send-until-app-restart-recreate/172032 "2026-09-17T13:38:44Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Wes\_Anderson](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@Wes\_Anderson](https://forum.cursor.com/u/Wes_Anderson)\ **Post date:** [September 17, 2026, 1:38pm UTC](https://forum.cursor.com/t/grok-bot-teammate-unresponsive-after-long-tool-waits-recreated-agent-shows-failed-to-send-until-app-restart-recreate/172032/1 "2026-09-17T13:38:44Z")
### Where does the bug appear (feature/product)? Grok Bot ### Describe the Bug While testing a custom teammate (“Scout”) that watched a background process and reported updates in chat, two problems showed up: The teammate stopped answering chat (looked hung) while parked on long AwaitShell-style waits. After deleting and recreating that teammate, the UI accepted typed messages but showed Failed to send, and the agent transcript stayed empty. Another existing teammate (e.g. Annie) still worked. Quitting/reopening the app and recreating the agent again fixed delivery. Environment Grok Bot desktop 0.55.0 Windows 11 Home Version 10.0.26200 Build 26200 Multiple teammates on one shared Grok Bot computer New teammate created via another bot / CreateAgent flow ### Steps to Reproduce A — Hung / no replies while “working” Create a teammate whose job is to watch a long-running shell/background stream and post short updates to chat. Have it wait for the next event with a long await (on the order of minutes, e.g. ~180s), then post, then wait again in the same turn chain. While it is waiting, send normal chat messages (“hi”, “stop”). Observe: delayed or missing replies; agent appears stuck until the wait ends or processes are killed externally. B — Failed to send after delete + recreate Delete the hung teammate from the sidebar (right-click → Delete). Recreate a teammate with the same name via another agent. Open the new teammate chat and send messages. Observe: bubbles appear with Failed to send (Resend / Delete). Confirm: agent-side transcript has no entries (messages never arrived). Confirm: other teammates still send/receive normally. Fully quit and reopen Grok Bot; delete the broken teammate; create again. Observe: messaging works again. ### Expected Behavior Expected Behavior User chat should interrupt or queue ahead of long background waits so the teammate stays responsive. A newly created teammate should accept messages immediately (no Failed to send). If create is incomplete, the UI should not pretend the message was composed successfully without delivery. ### Operating System Windows 10/11 ### Version Information Grok Bot desktop 0.55.0 ### For AI issues: which model did you use? Grok Bot ### Additional Information Actual Behavior Long wait loops made the teammate look dead in chat. Post-recreate instance: UI showed Failed to send; no agent transcript; other bots fine. Workaround: app restart + delete/recreate restored messaging (~2–3s replies in our follow-up test). Root cause (our read — for engineering) Hang: Agent turn stayed blocked on long shell awaits chained with chat posts. Platform may not surface/prioritize new user messages until that tool call finishes, so the chat looks broken even though the agent “exists.” Failed to send: Recreation produced a sidebar agent whose message pipeline was not fully wired (client send failed; empty transcript). Points to a race/incomplete provision after CreateAgent + delete, not user error. App restart + fresh create cleared it. Workaround / fix that worked for us Stop leftover background listener processes on the shared computer. Prefer delete + recreate over “Update Grok Bot’s Computer” for a single hung agent (Update affects all bots’ machine, reinstalls tools, can jostle secrets). If recreate shows Failed to send: fully quit Grok Bot → reopen → delete that agent → create again. For watchers: keep awaits short (seconds, not minutes), end turns cleanly, and always answer user/stop before restarting a watch. Ask Can new user messages preempt or cancel long AwaitShell waits? Can CreateAgent / post-delete create guarantee the chat send path is ready before the teammate appears in the sidebar? Better client error when send fails (and avoid showing a “sent-looking” bubble that only fails after)? Happy to provide timestamps or more logs if useful. ### Does this stop you from using Cursor Sometimes - I can sometimes use Cursor ---
**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 17, 2026, 9:15pm UTC](https://forum.cursor.com/t/grok-bot-teammate-unresponsive-after-long-tool-waits-recreated-agent-shows-failed-to-send-until-app-restart-recreate/172032/7 "2026-09-17T21:15:16Z")
Hi @Wes_Anderson Thanks for the post. What you saw isn’t how this is supposed to work, and it wasn’t caused by anything in your setup. It lines up with the Grok Bot service degradation on [status.cursor.com](http://status.cursor.com) earlier today, which is resolved now. Scout was not stuck on the shell wait, and the recreated bot was not mis-wired. Your messages reached us and were accepted, but the turn behind them never ran, so the app stopped waiting and showed “Failed to send”. The third Scout started answering because the service had recovered by then, not because of the restart. On your questions: 1. A new message from you is meant to interrupt whatever the bot is doing, including a long wait on a shell command, and start on your message right away. That happened three times in that same Scout chat this morning. Each “hi” or “stop” cancelled the running step within about a second. The one that did not was when this service issue kicked in. 2. A newly created bot should be ready to chat immediately. The recreated Scout hit the same stall on its very first turn, which is why it never answered. 3. “Failed to send” was misleading here, since the message did reach us. We’ve let the team know. If something like this happens again, check [status.cursor.com](http://status.cursor.com) first, and hold off on deleting and recreating the bot. The history stays with the original, and a new bot can hit the same stall. If a bot is still silent well after the status page is clear, reply here with the bot name and the time of your last message and I’ll take a look. ---
**Author:** ![Wes\_Anderson](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@Wes\_Anderson](https://forum.cursor.com/u/Wes_Anderson)\ **Post date:** [September 17, 2026, 9:56pm UTC](https://forum.cursor.com/t/grok-bot-teammate-unresponsive-after-long-tool-waits-recreated-agent-shows-failed-to-send-until-app-restart-recreate/172032/8 "2026-09-17T21:56:18Z")
Kevin, Thanks for the quick reply. My bots have this locked in should it happen again. Watching the Grok Bot workshop and learning a lot. Thanks Wes ---
**Author:** ![Landon\_Taylor](https://avatars.discourse-cdn.com/v4/letter/l/ed655f/32.png) [@Landon\_Taylor](https://forum.cursor.com/u/Landon_Taylor)\ **Post date:** [September 17, 2026, 10:14pm UTC](https://forum.cursor.com/t/grok-bot-teammate-unresponsive-after-long-tool-waits-recreated-agent-shows-failed-to-send-until-app-restart-recreate/172032/9 "2026-09-17T22:14:12Z")
> [@kevinn](#): > > [status.cursor.com](http://status.cursor.com) Kevin, my bots are still unresponsive ---
**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 17, 2026, 10:29pm UTC](https://forum.cursor.com/t/grok-bot-teammate-unresponsive-after-long-tool-waits-recreated-agent-shows-failed-to-send-until-app-restart-recreate/172032/10 "2026-09-17T22:29:18Z")
Dm’ed