Sign in
← AI PulseSep 7, 2026

Policy · news · Single-source brief

Grok Bot Computers Can Connect to Private Networks via Team Setup

xAI's Grok Bot computers can access internal services on private networks by installing networking clients through the Team Setup feature, available on the Enterprise plan.

By Illumora Editorial

Source · Sep 7, 2026, 10:28 PM · On Illumora · Sep 7, 2026, 10:58 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →xAI Docs — Connect to private networks | SpaceXAI Docs
Save

xAI's documentation outlines a method for Grok Bot computers to connect to private networks. This capability allows Grok Bot computers, which run in Cursor's cloud and use shared static egress IP addresses, to reach internal services such as APIs, source control, databases, or staging environments.

The connection is established by installing an organization's networking client on each team computer via Team Setup. This feature is part of the Enterprise plan and supports common choices like Tailscale and Cloudflare Tunnel, with worked examples provided for both. Other VPN, zero-trust, or mesh clients compatible with Linux can follow a similar pattern.

Key Points

  • Grok Bot computers can access private networks by installing a networking client through Team Setup.
  • Team Setup is a feature available on the Enterprise plan.
  • Common networking clients like Tailscale and Cloudflare Tunnel are supported, with examples provided.
  • The approach involves running install scripts on every team computer, with the organization managing the client installation, configuration, and authentication.
  • Team Setup manifests are plain text and run as the computer user; secrets should not be embedded in setup scripts.
  • The Grok Bot network policy, including the destination allowlist, remains a separate and active layer.
  • Changes to Team Setup manifests are applied to running computers periodically, typically within about a day, or immediately upon computer recreation.

Context

According to xAI's documentation, Team Setup provides a hook for organizations to run install scripts on every team computer. This allows for the deployment of networking clients that enable Grok Bot computers to reach internal services that are not exposed to the public internet. The organization is responsible for the client's installation, configuration, authentication, and maintenance, while Cursor provides the mechanism for script deployment.

Why It Matters

This capability provides Grok Bot users with a method to integrate their AI agents more deeply into existing internal infrastructure, enhancing the utility of Grok Bot for tasks requiring access to private corporate resources. It shifts the responsibility for network client management and security to the user, requiring careful implementation of access controls and authentication.

What To Do

  • Review the xAI Docs on connecting to private networks to understand the full implementation details.
  • If on the Enterprise plan, explore the Team Setup section within the Grok Bot page of the Cursor dashboard.
  • Test the integration with a pilot computer using Tailscale or Cloudflare Tunnel before a team-wide rollout.
  • Ensure that no secrets, such as authentication keys or tokens, are embedded directly into Team Setup scripts.
  • Note that the Grok Bot network policy and destination allowlist still apply, and necessary client coordination servers should be added to the allowlist.