Grok Bot Agent Computer unreachable after bot installed a VPN — all bots fail to reconnect

Support Help
, ,
1

Where does the bug appear (feature/product)?
Grok Bot

Describe the Bug

Grok Bot lost connection to its Agent Computer immediately after one of my bots tried to set up a VPN on that computer. Every bot on the account now fails to reconnect, including on phone. The main assistant no longer appears in the phone app roster.

I understand now that a VPN inside the Agent Computer is unsupported because it breaks the always-on path back to Cursor’s servers. I cannot ask a bot to uninstall the VPN, because no bot can reach the machine.

Steps to Reproduce

  1. Bot on the shared Agent Computer started setting up a VPN / changing network settings.
  2. Connection dropped right after that.
  3. Desktop and phone both show reconnect / “can’t reach Grok Bot’s computer.”
  4. Other bots on the same account also cannot reach the computer.
  5. Main bot is missing from the phone roster.

What I already tried

  • Retry reconnect
  • Fully quit / relaunch Grok Bot
  • Checked from phone as well as desktop

Environment

  • OS: MacOS
  • VPN that caused this: installed inside the Agent Computer by the bot

Additional Information

Please repair or reattach the existing Agent Computer from the backend. Reinstall the VPN.

  1. Uninstall the VPN and restore default routing/DNS
  2. Delete any routine/script that installs a VPN
  3. Add a standing rule: never install VPN/proxy or change DNS/network settings

Does this stop you from using Cursor / Grok Bot?

Yes — Grok Bot is unusable until the Agent Computer is reachable again.

3

The problem was fixed. Thank you

5

Hey, glad it’s working now.

For the future, to avoid this happening again: changing network settings inside the Agent Computer VPN, proxy, or DNS routing breaks the always-on connection to the servers. After that, no bot can reach the machine to roll the changes back. It’s worth adding a permanent rule for bots not to set up a VPN or proxy and not to change DNS or other network settings on the Agent Computer, and also removing any routine or script that does this.

If you run into “can’t reach your computer” again, post in the thread and we’ll take a look.