Grok Bot: Reset failed / computer stuck in partial state — can't connect

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot version: 0.36.0
OS: macOS, Apple Silicon (M1)
Plan: Cursor Pro (Grok Bot access confirmed via the Pro rollout email; Usage & Billing shows weekly usage active at 0%)

Symptom:
Grok Bot has never successfully connected. Stuck on “Reconnecting to your computer… Retrying” since first setup, then progressed to “Can’t reach your computer” with a Retry button.

Troubleshooting completed:

  • Fully quit and reopened the app (Cmd+Q, not just closing window)
  • Confirmed no VPN interference — had NordVPN installed, uninstalled it entirely, issue persists
  • Confirmed Privacy Mode is set (not Legacy Privacy Mode / Share Data)
  • Tried Settings → Updates → Reset Grok Bot’s Computer → failed with: “Reset couldn’t finish. Grok Bot’s computer may be in a partial state — retry to run the reset again.”
  • Tried Retry Reset → same failure

This looks like a backend compute provisioning issue on my account rather than a local network/config problem. Would appreciate a manual reset/repair from your side.

Steps to Reproduce

  1. Install Grok Bot 0.36.0 on macOS (Apple Silicon, M1) via Sign in
  2. Sign in with Cursor account (Pro plan)
  3. App shows “Reconnecting to your computer… Retrying” indefinitely
  4. Retry from error state → shows “Can’t reach your computer”
  5. Go to Settings → Updates → Reset Grok Bot’s Computer
  6. Reset fails with: “Reset couldn’t finish. Grok Bot’s computer may be in a partial state — retry to run the reset again.”
  7. Retry Reset → same failure

Expected Behavior

Grok Bot’s computer should provision successfully and connect, allowing me to create and run a Bot.

Operating System

MacOS

Version Information

Grok Bot 0.36.0 (macOS, Apple Silicon M1)

Additional Information

This is a first-time setup — Grok Bot has never successfully connected since installation, so there’s no prior working state that regressed. Account is Pro plan, eligibility confirmed via the Cursor Pro rollout email for Grok Bot (Aug 26, 2026). Happy to provide a diagnostic/request ID if there’s a way to generate one despite the connection never completing — let me know what’s useful.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hi @shubham_chaturvedi

This looks like the same issue reported over here: