Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Grok Bot Agent Computer stuck “still starting up” / unreachable for ~48–72 hours (since ~2026-09-20). Agents cannot use Shell, files, screenshots, or chat attachments. Update Agent Computer and Reset Agent Computer both failed. Same failure on phone, desktop PC, and laptop with the same account — not a single-device network/AV issue. Please server-side reprovision / recreate the Agent Computer for this account; I will not click Reset again unless asked.
Steps to Reproduce
Sign in to Grok Bot as [email protected] (Cursor Pro+ / SuperGrok Heavy linked).
Open any Bot chat and try a computer action (Shell, screenshot, or attach a file).
Observe computer stuck “still starting up” / no connection; attachments fail with no connection to the computer.
Try Update Agent Computer → fails.
Try Reset Agent Computer → fails (reset couldn’t finish / partial state).
Fully quit and reopen on phone, desktop, and laptop → same error on all devices.
Expected Behavior
Agent Computer becomes reachable again (or support reprovisions it server-side), preserving Bots, chats, files, and logins. Update/Reset should complete or staff should recover the box without requiring more client resets.
Operating System
Windows 10/11
Version Information
Grok Bot apps on phone + desktop + laptop (please tell me if you need exact build numbers from Settings → About; issue is account Agent Computer, not one IDE build). Cursor IDE itself is not the broken surface.
For AI issues: which model did you use?
N/A — infrastructure / Agent Computer connectivity, not a model reply quality issue.
For AI issues: add Request ID with privacy disabled
N/A — sends/attachments fail before a normal Bot turn with Request ID; happy to add any ID you specify after recovery tools are available
Additional Information
Account: [email protected]. Timezone: America/Bogota (UTC-5). Duration ~48–72h. Workarounds in use: text-only chat + Gmail/Drive/ClickUp/Calendar connectors. Please do not ask for another Reset; requesting account-side recovery like other “starting up” cases on this forum.
Does this stop you from using Cursor
No - Cursor works, but with this issue