Grok Bot
When a VPN inside Agent Computer breaks Grok Bot reconnect
When a VPN inside Agent Computer breaks Grok Bot reconnect
If Grok Bot sticks on Reconnecting to your computer (sometimes with a malformed listAgents gateway response) after a Bot installed or ran a personal VPN on the shared Agent Computer, treat that VPN as the cause. Cursor staff (Colin, Sep 9, 2026) on forum thread 170736: personal VPN on the box is unsupported; it steals routing and DNS so the server link dies.
Fix path
- Remove the VPN from the Agent Computer (uninstall the client, delete tunnel configs, stop any VPN daemon the Bot started).
- Delete or rewrite any routine, standing instruction, or skill that tells a Bot to set up a VPN on the cloud box — otherwise Reset only helps briefly and the Bot reinstalls it.
- Use Recover or Reset Agent Computer from Settings → Beta only after the VPN instruction is gone (see Use the computer and apps).
- If you still need corporate-only hosts, use Execution on Local Computer while your Mac/PC is on the corp VPN, or wait for Enterprise private-network support — do not spoof region via a personal VPN on the box.
Related how-tos
- Corporate VPN / SSO / YubiKey limits: Reach VPN-only work apps from Grok Bot
- Generic “Can’t reach your computer”: Fix Grok Bot “Can’t reach your computer”
- System proxy / TUN interference on your machine: Fix Grok Bot when a system proxy or TUN VPN blocks the app
Pitfalls
- Treating Reset as the whole fix while a routine still says “install WireGuard / OpenVPN on the Agent Computer.”
- Expecting a personal VPN on the cloud box for region spoofing — staff marked that unsupported.
- Confusing this with corporate VPN on your laptop (local-execution path) — that is a different surface.