[DOCS] Data usage docs omit host-managed analytics behavior for Bedrock, Vertex, and Foundry

Resolved 💬 2 comments Opened May 1, 2026 by coygeek Closed May 10, 2026

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/data-usage

Section/Topic

"Default behaviors by API provider" under "Telemetry services"

Current Documentation

The docs currently state that telemetry-related services are disabled by default for third-party providers:

By default, error reporting, telemetry, and bug reporting are disabled when using Bedrock, Vertex, or Foundry.

The provider table also says:

| Statsig (Metrics) | Default on.<br />DISABLE_TELEMETRY=1 to disable. | Default off.<br />CLAUDE_CODE_USE_VERTEX must be 1. | Default off.<br />CLAUDE_CODE_USE_BEDROCK must be 1. | Default off.<br />CLAUDE_CODE_USE_FOUNDRY must be 1. |

What's Wrong or Missing?

The v2.1.126 release entry says host-managed deployments using CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST no longer auto-disable analytics on Bedrock, Vertex, or Foundry.

The current data-usage page still presents the third-party provider rule as unconditional: Bedrock, Vertex, and Foundry default to off for error reporting, telemetry, and bug reporting. It does not mention the host-managed deployment exception or explain how CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST changes the analytics default.

This leaves administrators with outdated guidance for managed third-party-provider deployments and can cause them to assume analytics is off when v2.1.126 behavior may leave it enabled unless they set the explicit opt-out variables.

Suggested Improvement

Update the "Default behaviors by API provider" section to distinguish ordinary third-party-provider use from host-managed deployments.

For example, add a note near the table:

In host-managed deployments where CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST is set, Bedrock, Vertex, and Foundry no longer auto-disable analytics as of v2.1.126. To disable non-essential traffic in these deployments, set CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, or set the service-specific variables such as DISABLE_TELEMETRY, DISABLE_ERROR_REPORTING, and DISABLE_FEEDBACK_COMMAND.

If the table remains the primary reference, add a footnote to the Bedrock, Vertex, and Foundry columns so the "Default off" rows do not appear unconditional.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/data-usage | "Default behaviors by API provider" | States that telemetry, error reporting, and bug reporting are disabled by default for Bedrock, Vertex, and Foundry, without mentioning CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST. |

Total scope: 1 page affected.

The behavior change comes from the v2.1.126 release entry: "Host-managed deployments (CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST) no longer auto-disable analytics on Bedrock/Vertex/Foundry."

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗