- OS: Windows 11 Pro 26200
- Grok Bot version: 0.30.0 (installed 2026-08-28)
- Symptom: Black window after setup, only title-bar buttons render
- Auth: Completed — Google OAuth account slot persisted (
google-oauth2|user_01JZK5...) - Crashes: None. Zero Crashpad dumps; Sentry session
status: ok,errors: 0 - Network: Verified working —
api2.cursor.shreturns HTTP 200 over valid TLS; system DNS matches independent resolver, so the client’s own DNS divergence probe passes - Key detail:
sand-client-persistence/contains only the account slot, no VM or cluster identifier — no sandbox appears to have been provisioned - Ask: Rebuild / reset the Agent Computer for this account
Hi there!
We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.
To help us investigate and fix this faster, could you edit your original post to include the details from the template below?
Bug Report Template - Click to expand
Where does the bug appear (feature/product)?
- Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
- Terminal & commands
- Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
- MCP & tools
- Cloud Agents & Automations (cursor.com/agents, scheduled/event)
- BugBot & Code Review
- Cursor CLI
- Cursor Mobile
- Remote (SSH / Dev Containers / WSL)
- Account, billing & login
- Something else…
Describe the Bug
A clear and concise description of what the bug is.
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
- …
- …
- …
Expected Behavior
What is meant to happen here that isn’t working correctly?
Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)
Operating System
- Windows 10/11
- MacOS
- Linux
Version Information
- For Cursor IDE: Menu → About Cursor → Copy
- For Cursor CLI: Run
agent aboutin your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......
CLI:
CLI Version 2026.01.17-d239e66
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
- Yes - Cursor is unusable
- Sometimes - I can sometimes use Cursor
- No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey @Dan_Baker
Your Cursor account is set up as an Unpaid Admin, which is an admin role without a paid seat. Grok Bot needs a paid team seat (Standard or Premium), and without one the app cannot connect to a Grok Bot computer. Right now the app shows that as a connection failure instead of telling you what is missing, which is on us and something we are fixing.
To get going:
- Go to cursor.com/dashboard and open the Members page
- Find your own row and change your role from Unpaid Admin to a paid seat (Admin or Member).
- Fully quit Grok Bot (right-click the menu bar icon and choose Quit, or use the osascript command you posted).
- Reopen Grok Bot, and press Try again if you land on the setup screen.
It should connect within a minute or two.
One other thing worth checking: it’s possible you already have a paid seat on a different Cursor account and Grok Bot is signed in with the wrong one. If your Members page already shows you on a paid seat, sign out of Grok Bot and sign back in with the account that holds that seat, and confirm the email shown in the app matches it.
My actual Grok.com account is a SuperGrok account… So, perhaps I just need to sign in differently? But since its stuck here I don’t see what I can do?
