Repository Public
1<!-- source: https://docs.x.ai/grok-bot/private-networks (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Connect to private networks56Grok Bot computers run in Cursor's cloud and reach the internet through7[shared static egress IP addresses](/grok-bot/security#static-egress-ips).8If the systems your Bots need, such as internal APIs, source control, databases,9or staging environments, live on a private network, route traffic through a10member's desktop or install your organization's networking client on every team11computer through **Team Setup**. Tailscale and Cloudflare Tunnel are common12client choices, and this page has a worked example for each. Other VPN,13zero-trust, or mesh clients that run on Linux follow the same pattern. Your14services stay off the public internet, and access is governed by the access15controls and identity provider you already use.1617> Team Setup is Enterprise only. It does not appear on other plans. Network18> Controls is also Enterprise only. That19> [network policy](/grok-bot/security#network-policy) is a separate layer that20> still applies; private network reach does not replace your destination21> allowlist.2223## What you can do2425* Route one member's traffic through their desktop, so Bots can reach services26 available from that device and destinations see its IP address.27* Install your networking client on every team computer automatically, from one28 admin-managed manifest, with no per-computer setup.29* Let Bots reach services on your private network without exposing those30 services to the internet or adding shared egress IPs to your allowlists.31* Keep control on your side: your network, your access rules, and your identity32 provider. You can revoke a computer from your own admin console at any time.3334## Choose a connection method3536| Method | Use it when |37| --- | --- |38| Route egress through a desktop | One member needs access through a network already available from their device |39| Install a networking client with Team Setup | Your Enterprise team needs a consistent connection on every hosted computer |4041### Route through a member's desktop4243In the Grok Bot desktop app, open **Settings → Computer** and turn on **Route44egress through this desktop**. The route uses the current device's network and45IP address. It stops when the setting is turned off or an Enterprise admin46disables **Allow Local Egress**.4748Each member controls their own desktop route. Enterprise admins can remove this49option for the whole team from50[Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot). See51[Route traffic through your desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop).5253### Install a networking client with Team Setup5455This is a pattern you run, not a Cursor-managed network mode. Cursor provides56the hook: Team Setup runs your install scripts on every team computer. You own57the rest: installing the client, configuring it, authenticating computers,58maintaining access rules, and keeping up with your vendor's changes. Cursor59installs nothing by default, does not operate or monitor your network client, and60the dashboard shows no client status. Your vendor's documentation is the source61of truth for installing and configuring their software; this page covers the62Cursor side.6364## Before you start6566* You are a team admin on the Enterprise plan. Team Setup does not appear on other67 plans.68* Your networking client runs on Debian-based Linux and can be installed and69 started from a shell script. Team computers run Linux, and scripts run as the70 computer user with `sudo` available.71* Your network has a way in for that client: a gateway, exit node, or tunnel72 connector inside the VPC or intranet you want to reach, per your vendor's73 architecture.74* You have decided how computers will authenticate to your network. Keep75 credentials out of setup scripts.7677## How Team Setup runs your scripts7879Team Setup lives on the **Grok Bot** page of the80[Cursor dashboard](https://cursor.com/dashboard/bot): manifests of install81scripts that run on every team computer. Each manifest holds one or more script82entries, and each entry has an **ID**, a **Setup Script**, and an optional83**Check Script**.8485* Scripts run as the computer user on every team computer; use `sudo` for86 privileged installs.87* They run when a computer starts, and on a periodic refresh, roughly daily,88 while it runs.89* If a Check Script is present and exits 0, the Setup Script is skipped; use it90 to avoid reinstalling on every pass. After a setup runs, the check runs again91 to verify it succeeded.92* Entries run one at a time, in order. Each script has a 30-minute timeout. A93 failed script does not block the computer; it is retried on a later refresh.9495## Create the manifest96971. Go to [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot)98 and open **Team Setup**.992. Next to **Manifests**, select **+** to create a **New Manifest**, then enter100 a **Manifest ID**, for example `private-network`.1013. In the script entry, set the **ID** (for example `install-network-client`)102 and write the **Setup Script**: install your client following your103 provider's Linux install documentation, then start it and connect it to your104 network the way your configuration prescribes.1054. Optionally add a **Check Script** (for example `command -v <your-client>`),106 so computers that already have the client skip the install.1075. Select **Save**.108109If you prefer editing JSON, toggle from **Form** to **JSON** at the top of the110editor. The manifest has this structure:111112```json113{114 "manifestId": "private-network",115 "entries": [116 {117 "id": "install-network-client",118 "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",119 "check": "command -v <your-client>"120 }121 ]122}123```124125> Do not include secrets. Setup scripts run as the computer user on every team126> computer, and manifests are plain text applied to your whole fleet. Do not127> embed auth keys, tokens, or other credentials. Have members authenticate128> interactively in the computer's browser, where your identity provider's129> policies apply, or use a mechanism from your vendor's documentation that keeps130> long-lived credentials out of the script.131132## Set up your networking client133134Whatever tool you use, the last mile is the same: each computer authenticates to135your network, you confirm the connection in your vendor's console, and you136verify by asking a Bot to reach an internal hostname it could not reach before.137Interactive login happens in the computer's browser, the same way members138already [sign in to company tools there](/grok-bot/identity-and-access). Start139with one or two pilot computers before rolling out team-wide.140141### Tailscale142143Run Tailscale on each computer and route through an144[exit node](https://tailscale.com/docs/features/exit-nodes) inside your network.145This is the configuration the pattern has been exercised with. Tailscale also146offers [subnet routers](https://tailscale.com/docs/features/subnet-routers) for147exposing specific private ranges; validate that arrangement on a pilot computer148before relying on it.149150**Before you start:** you operate a tailnet with an exit node inside the VPC or151intranet you want to reach.152153**Team Setup manifest:**154155* **Setup Script:** install Tailscale for Linux following156 [Tailscale's install documentation](https://tailscale.com/docs/install/linux),157 then bring the computer onto your tailnet per your configuration.158* **Check Script:** `command -v tailscale`.159160**Connect and verify:**1611621. Authenticate each computer. Tailscale prints a login URL that opens in the163 computer's browser, where your identity provider's policies apply. Keep auth164 keys out of the script.1652. Confirm the computer appears in your Tailscale admin console and is allowed166 to use the exit node.1673. Ask a Bot to reach an internal hostname.168169**If it does not work:**170171* The client installed but nobody authenticated. The login step is deliberately172 manual, since scripts cannot hold secrets. Check the machine list in your173 Tailscale admin console.174* Your team's network policy is allowlist-only and blocks Tailscale's175 coordination servers or relays. Allow the endpoints from Tailscale's docs.176 Running computers apply the change within about a minute. Sleeping computers177 apply it when they next wake.178* The exit node is not advertised or approved in your tailnet. Check route179 settings in the admin console.180* The computer was recreated, for example after an image update or reset, and181 the session did not survive. Authenticate again.182183### Cloudflare Tunnel184185The same Team Setup mechanics work for186[Cloudflare Tunnel](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/):187a `cloudflared` connector inside your network publishes private services through188Cloudflare's edge, protected by Cloudflare Access, and the computer reaches them189by hostname. This arrangement has not been exercised on team computers the way190the Tailscale one has, so validate it on a pilot computer before rolling out.191192**Before you start:** you run a Cloudflare Tunnel connector inside your private193network, with the services you need routed through it, and you have chosen your194Cloudflare Access policy. Identity-based policies fit this pattern well, since195members sign in through the browser. Access service tokens are secrets; keep196them out of setup scripts.197198**Team Setup manifest:**199200* **Setup Script:** install `cloudflared` following201 [Cloudflare's downloads documentation](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/).202 Only the client goes on the computer; the connector stays in your network.203* **Check Script:** `command -v cloudflared`.204205**Connect and verify:**2062071. Private HTTP services: reach them at the hostname you routed through the208 tunnel. Cloudflare Access enforces your policy; with identity-based policies,209 the member signs in through the computer's browser.2102. Private TCP services, such as databases or SSH: run `cloudflared access tcp`211 on the computer to open a local listener and point the tool at it.212 Cloudflare's docs cover the flow. A Bot can start the listener in its shell213 when it needs the service.2143. Ask a Bot to reach the private hostname or service.215216**If it does not work:**217218* The connector inside your network is down. Check tunnel health in your219 Cloudflare dashboard; this fails on your side, not the computer's.220* Cloudflare Access denies the request. Check your Access logs and confirm the221 member has authenticated.222* Your team's network policy is allowlist-only and blocks the tunnel hostname or223 Cloudflare's endpoints. Allow them. Running computers apply the change within224 about a minute. Sleeping computers apply it when they next wake.225* A service token was embedded in the setup script. Do not do this; manifests are226 plain text. Use identity-based Access, or supply tokens at use time.227* A `cloudflared access tcp` listener is not running when the Bot needs it.228 Listeners do not persist across sessions; start one when needed.229230To choose between them: Tailscale gives the computer network-level reach and,231with an exit node, egress from your network. Cloudflare Tunnel publishes232specific services through Cloudflare's edge behind Access: per-service rather233than whole-network, and the egress addresses that other services see do not234change.235236Other clients that install and run on Debian-based Linux follow the same Team237Setup steps; validate yours on a pilot computer before rolling out.238239## Roll out to existing computers240241* New computers apply manifests when they start.242* Running computers pick up manifest changes on a periodic refresh, roughly243 daily.244* To apply a manifest change immediately, recreate the computer or have the245 member reset it from the desktop app. Organization admins can recreate or246 terminate a member's computer from the dashboard. The durable disk is kept,247 and the next computer applies current manifests when it starts.248* Image updates recreate computers automatically, and your scripts re-apply.249 Sign-in sessions, including your network client's login, may need to be250 re-established after a computer is recreated.251252## Work with the network policy253254The Grok Bot [network policy](/grok-bot/security#network-policy) is a separate255layer that controls which destinations team computers may reach.256If your team uses **Team allowlist only**, add the destinations your networking257client needs, such as coordination servers, relays, and gateways, from your258vendor's documentation. Running computers apply policy changes within about a259minute. Sleeping computers apply them when they next wake. You do not need to260recreate the computer.261262## Limitations263264* This is a pattern you operate, not a Cursor-managed network mode. Cursor265 does not install, operate, or monitor your networking client, and support for266 the client itself comes from your vendor.267* Regular internet traffic still egresses through Cursor's shared static IP268 ranges unless you route it through your own network. Dedicated per-customer269 egress IPs are not available.270* There is no fleet view of script results today. Verify a pilot computer before271 rolling out team-wide.272* This is not the Cloud Agents setup. The Cloud Agents docs have their own273 [Tailscale](https://cursor.com/docs/cloud-agent/setup#running-tailscale) and274 [Cloudflare Tunnel](https://cursor.com/docs/cloud-agent/setup#running-cloudflare-tunnel)275 recipes for a different product surface; Grok Bot computers are configured276 through Team Setup as described here. If Grok Bot delegates work to Cloud277 Agents, those agents run under Cloud Agent network settings, not your278 computer's network client.279280## FAQ281282### Can I put an auth key or credential in the setup script?283284No. Setup scripts are not a secret store, and the dashboard warns against285including secrets. Authenticate computers interactively, or use a mechanism from286your vendor's docs that does not require embedding a long-lived credential in the287script.288289### Which networking tools can I use?290291Any client your team can install and run on Debian-based Linux from a shell292script. Tailscale and Cloudflare Tunnel are the worked examples on this page.293Validate your client on a pilot computer first.294295### Do existing computers get a new manifest?296297Yes. Running computers refresh manifests periodically, roughly daily. To apply298a manifest change immediately, recreate the computer or have the member reset299it from the desktop app.300301### Does this change the IP addresses my services see?302303For traffic routed through your network, yes. Traffic to your private network304arrives from inside your network, via your exit node, gateway, or tunnel305connector. Everything else continues to egress from Cursor's shared static306ranges.307308### We use a strict network allowlist. Will our client work?309310Only if you allow its endpoints. Add the destinations your client requires to311your team allowlist. Running computers apply the change within about a minute.312Sleeping computers apply it when they next wake.313314### Is this the same as the Tailscale and Cloudflare Tunnel sections in the Cloud Agents docs?315316No. Those recipes are specific to Cloud Agent VMs; Tailscale there requires317userspace networking and proxy variables. Grok Bot computers use Team Setup and318your own gateway or connector, as described on this page.319320### Which plans include Team Setup?321322Team Setup is Enterprise only. Team admins manage manifests. If you do not see323it on the Grok Bot page of the dashboard, you are not on Enterprise, or you324need your account team to enable Grok Bot for the organization.325326### What happens if the setup script fails on some computers?327328The computer still starts. Failed entries are retried on a later refresh. Keep329scripts re-runnable and use a Check Script so healthy computers skip the330install.331332## Related pages333334* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)335* [Grok Bot security](/grok-bot/security)336* [Configure identity and access](/grok-bot/identity-and-access)337* [Configure TLS-inspecting proxies](/grok-bot/proxies), for the path from338 member devices to Cursor339* [Cloud Agents: Running Tailscale](https://cursor.com/docs/cloud-agent/setup#running-tailscale)340 and [Running Cloudflare Tunnel](https://cursor.com/docs/cloud-agent/setup#running-cloudflare-tunnel)341