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