Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Agent Computer has been unusable for some time. Recovering hangs at “Getting ready” (0%) and never advances. Update Grok Bot’s Computer fails with:
The update couldn’t finish. Agent Computer is still on its previous image. Your files and logins are kept; installed apps and packages are not. Any agent turn that cannot pause is discarded.
Without a working computer, Grok Bot is effectively useless (no computer use / takeovers).
Reset Grok Bot’s Computer also failed (just tried).
This is not a Cursor Models quota issue: Spending shows Grok Bot weekly usage ~9%; Cursor Models is at 99% separately.
Steps to Reproduce
- Open Grok Bot 0.44.0 on Ubuntu, signed in with Cursor Ultra.
- Computer is unreachable / recovery needed.
- Try Recover computer → stuck on Recovering → Getting ready @ 0% (Continue in Background does not help).
- Fully quit all Grok Bot processes and relaunch → same.
- Settings → Updates → Update Grok Bot’s Computer → Update failed (“still on its previous image”).
- Repeat on phone hotspot (different network) → same Update failure / no fix.
- Settings → Updates → Reset Grok Bot’s Computer → also failed.
Expected Behavior
Recover, Update, or Reset should finish and reconnect to a usable Agent Computer (or fail with a clear, actionable error). Prefer backend rebuild/reattach if the VM is stuck in a partial / previous-image state.
Operating System
Linux
Version Information
Grok Bot 0.44.0 (official .deb, amd64), Stable track
Additional Information
Network checks (already done)
*.us8.cursorvm.com wildcard DNS resolves on home Wi‑Fi and matches public DNS (1.1.1.1)
HTTPS to test.us8.cursorvm.com returns expected ELB 404
Same failure on phone hotspot → unlikely local ISP DNS filter
Cursor IDE / api2.cursor.sh work normally on the same machine
Account
Cursor Ultra; Grok Bot weekly allowance available (~9% used)
Ask
Please check the Agent Computer for this account on the backend and rebuild/reattach if it’s stuck on a previous image or partial state. Client Update, Recover, and Reset have all failed. Happy to provide request IDs / timestamps if you tell me where to find them.
Does this stop you from using Cursor
No - Cursor works, but with this issue