Grok Bot Behind a TLS-Inspecting Proxy: Domains and Fixes

The Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. desktop app talks to two different places from each member's device, and a gateway that handles one of them well can still break the other. This section covers what those two places are and why the failure is so easy to misread as a general network problem.

The first destination is Cursor's API at *.cursor.sh, which carries chat, sign-in and approvals. The second is the member's hosted computer, reached at a nested *.*.cursorvm.com hostname, which carries computer setup, the screen and the shell. Secure web gateways that inspect TLS often let the first through and break the second. The desktop app then hangs or errors during computer setup, and in some setups chat keeps working while the computer never connects.

Cursor's docs use Zscaler for specifics because it is the most common example, and they say the same steps apply to any gateway that re-signs TLS or buffers responses. The page is written for the IT team that runs the gateway, not for the member staring at a spinner. It also states what it is not: this is the path from a member's device to Cursor, and it does not change where the hosted computer itself may connect.

Four symptoms point at this problem. Computer setup hangs or fails while chat may keep working, because chat reaches api2.cursor.sh and the computer link needs cursorvm.com. The app works on a hotspot or a personal device and fails on the corporate network or with the gateway client running. It works in the office and fails at home, which means the exceptions were applied to the office location only. And sign-in or chat stall too, which means TLS inspection or response buffering is still active on cursor.sh.

The allow list is short, and the docs prefer wildcards over enumerated hostnames because computer hostnames are generated per computer. The table below is the full set to add on the gateway and in any DNS filtering.

The row people miss is the nested one. Computer hostnames have two labels below cursorvm.com, in the form <computer>.<cluster>.cursorvm.com, and a single-level wildcard matches only one label. A gateway configured with *.cursorvm.com alone looks correct and still leaves the computer unreachable, and the docs call this the usual cause of computer setup failing on a network where cursor.sh is already allowed.

Because the patterns are wildcards, the list also covers computers whose hostnames are generated later, since the docs say hostnames are generated per computer. The cost is that DNS filtering needs the same nested pattern as the gateway does, which is why one of the verification checks later in this article tests name resolution separately from the TLS issuer.

Allowing traffic does not make it work, because two gateway behaviors break Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. even on allowed domains. This section names both, and the fallback if your policy refuses to exempt anything.

• Bypass TLS (SSL) inspection on every domain in the table. When the gateway re-signs the connection with its own certificate, the computer setup handshake fails even though the hostname is allowed. Cursor's docs note the connections are already encrypted end to end.
• Turn off response buffering on the same domains. Chat and the computer link stream, and a gateway that holds responses until they complete leaves the app waiting on output that never arrives.

If your policy requires inspecting all traffic, the gateway has to meet the requirements in Cursor's SSL inspection and DLP section of the enterprise network configuration docs: HTTP/2 or Cursor's HTTP/1.1 fallback, Server-Sent Events passthrough without buffering, and long-lived connections without forced timeouts. The Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. page still calls exempting Cursor's domains the reliable path, so treat full inspection as the harder road, not an equal alternative.

There is a trap on the profile side. Zscaler Client Connector keeps running when a device leaves the office and applies an off-network profile of its own, so exceptions added to the office location or to one policy do not follow the device home. Apply the allow rules, the inspection exemption and any DNS exception to every location, profile and policy group that Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. members fall under, including roaming and off-network. Other gateways with separate on- and off-network policies need the same treatment. The tell is a laptop where Grok Bot works from the office and fails from home with the gateway client still running.

Run the checks below on a member's device with the gateway client running, after IT has applied the changes. Each one isolates a different failure, so the order matters less than running all four.

1. 1Check who issues the certificate with curl -v https://api2.cursor.sh |& grep -C1 issuer:. The issuer should be Amazon RSA. If it names Zscaler or your gateway vendor, TLS inspection is still active on cursor.sh for this device's profile.
2. 2Check that computer hostnames resolve with nslookup test.us9.cursorvm.com. You should get addresses back. If the lookup fails, try nslookup test.us9.cursorvm.com 1.1.1.1: if the public resolver answers and your default one does not, the block is the device's DNS or gateway profile, and the nested *.*.cursorvm.com exception is missing there.
3. 3Run the HTTP/1.1 and HTTP/2 streaming tests under Testing proxy connectivity in the enterprise network configuration docs. Output should arrive line by line, not all at once.
4. 4Open the Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. desktop app on the same device and connect to the computer. If it still fails, repeat the checks from that device. A passing hotspot and a failing corporate network confirms the network is the cause.

Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. has several network controls with similar names, and the docs point out that three are easy to confuse. The proxy page covers only the first row, so check the table before changing the wrong setting.

By default the hosted computer's own traffic leaves from Cursor's shared static egress IPs and does not pass through the gateway on member devices. When a member enables Route traffic through this computer, the routed traffic uses that device's network and is subject to its gateway policy. That is why the proxy work above and the private network work are separate projects with separate owners.