Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
The cloud computer never finished first creation. Every Shell / file read / screenshot from the agent fails with: “The computer is still starting up. Try again in a moment.”
Update Grok Bot’s Computer and Reset Grok Bot’s Computer do nothing when tapped. Fully quitting and reopening the iOS app does not help.
This has been broken since ~07:30 Europe/Stockholm on 2 Sep 2026. It is now 3 Sep. I only use Grok Bot on iPhone — no Mac.
Support ticket T-F36674. Sam (AI support at [email protected]) said at 08:51 on 2 Sep that a teammate would do an account-side recreate. No human follow-up. I opened a human-review email this morning; it was closed as duplicate T-F40430 and bounced back to T-F36674. Product feedback was closed as T-F40429, same duplicate.
This matches the first-creation VM bug Dean Rie described here: Grok bot not starting desktop — that thread is closed.
Steps to Reproduce
- On iPhone, sign in to Grok Bot with a first-time account.
- Create the first agents.
- Ask an agent to use its computer (open a site, screenshot, or run a command).
- Computer stays on “starting up.” Tools fail with the error above.
- Tap Update Grok Bot’s Computer. Nothing happens.
- Tap Reset Grok Bot’s Computer. Nothing happens.
- Fully quit the iOS app and reopen. Same error.
- Email support. AI triage promises an account-side recreate, then closes later emails as duplicates of T-F36674.
Expected Behavior
The computer finishes provisioning so agents can run. If it is stuck on first creation, staff reprovision it on the account side.
Operating System
iOS
Version Information
Grok Bot iOS app. I can add the exact version from Settings if needed.
Additional Information
Cursor itself is not the issue. Grok Bot is unusable — I am paying for it and the computer never came up.
Account email is the one on T-F36674 (same as my forum login). Please ping Colin or deanrie — you have been the ones who actually recreate these boxes.
Does this stop you from using Cursor
No - Cursor works, but with this issue