Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.309 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

Telemetry export to your own collector uses separate certificate and proxy settings

When sending OpenTelemetry data, Claude Code now builds its connection from your own certificate and proxy settings, not the shared setup

You'll notice Improvements
JSON All of v2.1.310
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release

Unclear It is not clear which of your certificate and proxy settings now apply to the telemetry connection, or when the strict connection is chosen.

What

Claude Code can send usage data to a collector you run, using OpenTelemetry (a common standard for sending this kind of data, also called OTLP). Before, every connection Claude Code made used the same rules for which certificates to trust and which proxy to go through. A proxy is a server that relays network traffic. Connections for this telemetry export now take a separate path. Claude Code checks your own certificate authority and proxy settings and builds either a "customer" or a "strict" connection from them.

Why

This changes which certificates and proxy are used when Claude Code reaches your collector. If you send telemetry through a corporate proxy or a custom certificate, check that it still arrives.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which of your certificate and proxy settings now apply to the telemetry connection, or when the strict connection is chosen.

See this entry in the whole of v2.1.310 →

Feedback