Grok Bot Private Networks for Enterprise

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. computers run in Cursor's cloud and reach the internet through shared static egress IP addresses. A service that lives only on a private network therefore needs a deliberate route, and there are two: send traffic through a member's desktop, or install your organization's networking client on every team computer with Team Setup Scripts.

The first is a setting each member controls for their own desktop. The second runs a script on every team computer, and you own the client and its upkeep.

Two Enterprise-only items sit around all of this. Team Setup Scripts does not appear on other plans. Network Controls is also Enterprise only, and that network policy is a separate layer that still applies, so private network reach does not replace your destination allowlist.

The route is a single setting in 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. Once it is on, Bots can reach services available from that device, and destinations see the device's IP address.

1. 1In 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, open Settings, then Computer.
2. 2Under Your computer, turn on Route traffic through this computer.
3. 3To stop the route, turn the setting off.

The route uses the current device's network and IP address. It stops when the setting is turned off or when an Enterprise admin disables Allow Local Egress Routing, whichever comes first.

Each member controls their own desktop route, and admins can remove the option for the whole team from 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. in the Cursor dashboard. Cursor's table positions it for the case where one member needs access through a network already available from their device.

Team Setup Scripts runs install scripts you write on every team computer, and that hook is everything Cursor provides. You own installing the client, configuring it, authenticating computers, maintaining access rules and keeping up with your vendor's changes. Cursor installs nothing by default, does not operate or monitor your network client, and the dashboard shows no client status.

The prerequisites follow from the way the scripts run.

• You are a team admin on the Enterprise plan.
• Your client runs on Debian-based Linux and can be installed and started from a shell script. Team computers run Linux, and scripts run as the computer user with sudo available.
• Your network has a way in for that client: a gateway, exit node or tunnel connector inside the VPC or intranet you want to reach.
• You have decided how computers authenticate. Credentials stay out of the script and live in a Team Secret.

Team Setup Scripts lives under Bot Computers on 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 of the Cursor dashboard. Each manifest holds one or more script entries, and each entry has an ID, a Setup Script and an optional Check Script. If the Check Script exits 0, the Setup Script is skipped, and after a setup runs the check runs again to confirm it worked.

1. 1Open 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. in the Cursor dashboard and find Team Setup Scripts under Bot Computers.
2. 2Next to Manifests, select + to create a New Manifest and enter a Manifest ID, for example private-network.
3. 3In the script entry, set the ID (for example install-network-client) and write the Setup Script: install your client following your provider's Linux install documentation, then start it and connect it to your network.
4. 4Optionally add a Check Script, for example command -v <your-client>, so computers that already have the client skip the install.
5. 5Select Save.

Prefer editing JSON? Toggle from Form to JSON at the top of the editor. The manifest has this structure.

{
  "manifestId": "private-network",
  "entries": [
    {
      "id": "install-network-client",
      "setup": "#!/usr/bin/env bash\nset -euo pipefail\n# 1) Install your networking client per your provider's Linux install docs\n# 2) Start the client and connect it to your network per your configuration",
      "check": "command -v <your-client>"
    }
  ]
}

Entries run one at a time, in order, each with a 30-minute timeout. Scripts run when a computer starts and on a periodic refresh, roughly daily. A script that fails does not block the computer and is retried on a later refresh. Cursor notes there is no fleet view of script results today.

No secret value belongs in the script text. Manifests are plain text applied to your whole fleet, and scripts run as the computer user on every team computer. If a script needs an auth key or token, store it as a Team Secret and read it from the environment, for example "$MY_AUTH_KEY". Team Secrets are Enterprise only, they are present only while the script runs, and script output is redacted before it is logged. A computer whose setup comes from more than one team receives no secrets.

To run a manifest on one cohort's computers only, add it under the group's 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. tab instead. Group manifests follow the same rules as the ones above.

Either can work, because Team Setup only needs a client that installs and runs on Debian-based Linux from a shell script. The docs treat them differently, though. Tailscale with an exit node is the configuration the pattern has been exercised with, while Cloudflare Tunnel has not been exercised on team computers in the same way and needs a pilot computer first.

With a Tailscale auth key, every team computer joins under the same key and tags rather than under the member's identity, so scope the key's ACLs accordingly. Browser login keeps your identity provider's policies in play, and with browser login the authentication step is manual.

Cloudflare Tunnel splits by protocol. Private HTTP services are reached at the hostname you routed through the tunnel, with Cloudflare Access enforcing your policy. For private TCP services such as databases or SSH, run cloudflared access tcp on the computer to open a local listener and point the tool at it. A Bot can start the listener in its shell when it needs the service, and listeners do not persist across sessions.

Whichever you pick, the last mile is the same. Start with one or two pilot computers, authenticate them, confirm the connection in your vendor's console, then ask a Bot to reach an internal hostname it could not reach before. The docs list these failure causes.

• The client installed but nobody authenticated. With an auth key, check that the Team Secret exists, its name matches what the script reads, and the key has not expired.
• An allowlist-only network policy blocks your vendor's coordination servers, relays or tunnel hostname. Allow the endpoints from the vendor's docs.
• The Tailscale exit node is not advertised or approved. Check route settings in the admin console.
• The Cloudflare connector inside your network is down. Check tunnel health in your Cloudflare dashboard.
• Cloudflare Access denies the request. Check Access logs and confirm the member has authenticated.
• A service token was embedded in the setup script. Use identity-based Access, or store the token as a Team Secret.
• The computer was recreated and the session did not survive. Authenticate again.

New computers apply manifests when they start, and running computers pick up changes on a periodic refresh, roughly daily. To apply a manifest change immediately, recreate the computer or have the member reset it from the desktop app. Organization admins can recreate or terminate a member's computer from the dashboard, and the durable disk is kept.

Image updates recreate computers automatically and your scripts re-apply. Sign-in sessions, including your network client's login, may need to be re-established afterward.

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. network policy is a separate layer that controls which destinations team computers may reach. If your team uses Team allowlist only, add the destinations your client needs, such as coordination servers, relays and gateways, from your vendor's documentation. Running computers apply policy changes within about a minute, sleeping computers when they next wake, and you do not need to recreate the computer.

Cursor lists four limitations.

• This is a pattern you operate, not a Cursor-managed network mode. Cursor does not install, operate or monitor your networking client, and support for the client comes from your vendor.
• Regular internet traffic still egresses through Cursor's shared static IP ranges unless you route it through your own network. Dedicated per-customer egress IPs are not available.
• There is no fleet view of script results today. Verify a pilot computer before rolling out team-wide.
• This is not the Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition. setup. Cloud Agents have their own Tailscale and Cloudflare Tunnel recipes, and if 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. delegates work to Cloud Agents, those agents run under Cloud Agent network settings, not your computer's network client.