The GROK BOT IS NOT WORKING

Support Bug Reports
1

Screenshot 2026-09-08 at 4.43.24 PM
Screenshot 2026-09-08 at 4.43.24 PM1214×1126 59.5 KB

2

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!

  1. …
  2. …
  3. …

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 about in 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!

6

Hey, thanks for the report. I can see the screenshot with the cover “Can’t Reach Grok Bot’s Computer” and the mention of firewall/proxy and *.cursorvm.com.

First, the good news. Your Grok Bot computer on our side is fully healthy, and your bots and data are not affected. The only thing failing is the DNS lookup on your current network. The app can reach our servers, but your network can’t resolve your computer address (a *.cursorvm.com host), so the connection never gets established. This lookup happens on your Mac and your internet connection. That’s why Retry, Reset, and Recover don’t help.

Important: please don’t click Reset, Recover, or Update Computer for now. Each time it rebuilds a computer that is already working fine, and it won’t fix a DNS issue.

Try these 2 steps:

  1. Switch your Mac to a public DNS resolver and fully restart Grok Bot. System Settings → Wi-Fi (or Network) → Details next to your connection → DNS tab → click +, add 1.1.1.1, then click + again and add 8.8.8.8, remove the other entries, OK. After that, quit Grok Bot with Cmd+Q and open it again.

  2. For a quick check, connect your Mac to a phone hotspot (ideally from a different carrier) and open Grok Bot. If it connects there, it means it’s a DNS issue on your regular network.

If you want to verify it yourself, open Terminal and run nslookup test.us9.cursorvm.com and nslookup test.us10.cursorvm.com. If on your regular network you get “can’t find” or NXDOMAIN, but via hotspot or with 1.1.1.1 in DNS it resolves, that’s the cause.

Let me know how it goes. If neither step helps, tell me which nslookup command failed and we’ll dig deeper.