Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
My Grok Bot Agent Computer is unreachable on both iPhone and desktop. All bots on the account are dead, including Chief of Staff.
The iOS app shows: “Couldn’t refresh — showing the last loaded messages.” Messages I send appear as black bubbles and never get a reply.
Overnight the bots stopped working. I reset the Agent Computer. It came back for about 45 minutes, then died again. I fully quit the app, signed out, and signed back in. The computer would not restart. Reset Grok Bot’s Computer now fails with an error that it cannot be reset / the computer is in a partial or incomplete state.
I then signed into Grok Bot on my computer with the same account. Same issue: computer won’t start, reset fails.
This is not one bad chat. The shared cloud computer is stuck. Please recover/rebuild the existing Agent Computer on the backend and keep my bots, chats, files, and logins. Do not have me keep hitting Reset. Client-side Reset and Recover cannot finish.
Steps to Reproduce
- Use Grok Bot normally on iPhone. Overnight the bots stop responding.
- Open a conversation (Chief of Staff). The app shows “Couldn’t refresh — showing the last loaded messages.” Sent messages appear as black bubbles and get no reply.
- Reset Grok Bot’s Computer. It comes back for about 45 minutes, then dies again.
- Fully quit the Grok Bot app and reopen it.
- Sign out and sign back in on iOS.
- Try to restart/reconnect the Agent Computer. It does not start.
- Try Reset Grok Bot’s Computer again. Reset fails with an error that it cannot be reset / the computer is in a partial or incomplete state.
- Sign in on desktop with the same account.
- The desktop app hits the same state: computer will not start, reset fails.
I cannot get past this from the client. It now happens every time I open Grok Bot on either device.
Expected Behavior
I’d like to be able to communicate with my bots
Screenshots / Screen Recordings
Operating System
MacOS
iOS
Version Information
Grok Bot 1.0
Does this stop you from using Cursor
No - Cursor works, but with this issue


