Skip to main content
When Cowork on third-party (3P) is configured with Vertex AI or Bedrock, conversation content never reaches Anthropic. The app does, by default, send a small amount of operational telemetry (crash reports and product analytics) that helps Anthropic diagnose issues and improve the product. Each category can be disabled independently via managed configuration. This page covers what each category contains, how to turn it off, and the complete set of outbound hostnames the app uses so you can configure your perimeter firewall.

Telemetry categories

Essential telemetry

Crash reports, error stack traces, and performance timings. Contains diagnostic metadata (app version, OS, error type, redacted stack frames) but never prompt or response content. Attributed to your organization via deploymentOrganizationUuid so Anthropic support can find issues you report.
SettingDefaultEffect when true
disableEssentialTelemetryfalseNo crash or error data leaves the device.
Disabling essential telemetry opts you into a manual support model. Anthropic will have zero remote visibility into failures on your fleet, so to get help with an issue your team will need to collect application logs from affected machines and send them to Anthropic directly. We strongly recommend leaving this enabled during initial rollout.

Non-essential telemetry

Product-usage analytics: feature adoption, session counts, UI interactions. Used to understand how Cowork is used in aggregate. Contains no prompt or response content.
SettingDefaultEffect when true
disableNonessentialTelemetryfalseNo product analytics leave the device.

Non-essential services

Cosmetic third-party fetches: favicons for connectors shown in the UI, and the sandboxed iframe that renders interactive artifact previews. Disabling these degrades the UI slightly (generic icons, static artifact previews) but doesn’t affect functionality.
SettingDefaultEffect when true
disableNonessentialServicesfalseFavicon and artifact-preview fetches are blocked.

Auto-updates

Checks Anthropic’s update feed and downloads new builds.
SettingDefaultEffect when true
disableAutoUpdatesfalseThe app never checks for or downloads updates. Your IT team must redistribute new builds.

Sending telemetry to your own collector

Independently of what’s sent to Anthropic, you can export full session activity (prompts, tool calls, token counts, errors) to your own OpenTelemetry collector by setting otlpEndpoint. This is the recommended way to retain an audit trail in environments that disable Anthropic-bound telemetry. See Monitoring for the event schema and the otlp* keys in the configuration reference.

Required egress paths

Cowork on 3P has two independent network boundaries:
  1. Perimeter firewall — your corporate network controls what the device can reach. The hostnames below are what you allowlist here.
  2. Sandbox egress filter — inside the app, the coworkEgressAllowedHosts key controls what the agent’s web-fetch and shell tools can reach from within the VM. This is independent of, and stricter than, the perimeter.
The Egress Requirements section of the in-app configuration window is the authoritative source for your deployment. It computes the exact allowlist from your current settings, updates as you change them, and can export the list as a text file for your firewall team. Use the tables below as a static reference; defer to the configuration window for the precise set your build requires.
All traffic is HTTPS on port 443. Allowlist by hostname (SNI); path-level rules aren’t required.

Always required

HostPurpose
downloads.claude.aiVM workspace bundle and Claude CLI binary, fetched at session start. Without this, Cowork sessions cannot start.

Inference provider

The host(s) for your configured provider. These carry conversation content.
HostPurpose
<region>-aiplatform.googleapis.comModel inference (or aiplatform.googleapis.com for the global region). Replaced by the host of inferenceVertexBaseUrl if set.
oauth2.googleapis.comGoogle auth token exchange
sts.googleapis.comGoogle auth token exchange
accounts.google.comGoogle auth token exchange
iamcredentials.googleapis.comGoogle auth token exchange

Auto-updates (disableAutoUpdates: false)

HostPurpose
api.anthropic.comUpdate feed
downloads.claude.aiUpdate binaries (already required above)

Essential telemetry (disableEssentialTelemetry: false)

HostPurpose
*.sentry.ioCrash and error reporting
*.ingest.us.sentry.ioCrash and error reporting (listed separately for firewalls that match wildcards one label deep)
browser-intake-us5-datadoghq.comPerformance timing

Non-essential telemetry (disableNonessentialTelemetry: false)

HostPurpose
a-cdn.anthropic.comAnalytics SDK
a-api.anthropic.comAnalytics events
claude.aiAnalytics events

Non-essential services (disableNonessentialServices: false)

HostPurpose
api.anthropic.comArtifact preview
www.claudeusercontent.comArtifact preview iframe
cdnjs.cloudflare.com, cdn.jsdelivr.net, fonts.googleapis.comArtifact preview asset CDNs
www.google.com, *.gstatic.comConnector favicons

Optional features

HostRequired when
Host of otlpEndpointOpenTelemetry export is configured
github.com, objects.githubusercontent.com, pypi.org, files.pythonhosted.orgPython-based desktop extensions are enabled
Hosts of each entry in managedMcpServersManaged MCP servers are configured
Hosts in coworkEgressAllowedHostsSandbox web access is configured

Disabling all Anthropic-bound connections

With disableEssentialTelemetry, disableNonessentialTelemetry, disableNonessentialServices, and disableAutoUpdates all set to true, the desktop application makes no outbound connections to Anthropic-operated hosts at runtime. The only required egress is downloads.claude.ai (for the VM bundle at session start) and your inference provider. This describes the application’s own connections; the guarantee that conversation content does not reach Anthropic via the inference path applies only when using Vertex AI or Bedrock. See the Locked down profile for a complete configuration.

Proxy support

The Cowork sandbox honors the host operating system’s proxy configuration, including PAC (proxy auto-configuration) files. If the device routes HTTPS through a corporate proxy, the sandbox will too, with no additional configuration required.