Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

OpenTelemetry export now gives a clear error when protocol and endpoint are missing

If no OTLP protocol is set and the endpoint is missing or invalid, Claude Code's telemetry export now stops with a clear error

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

Unclear It is not clear whether a default protocol is used when the endpoint is valid but no protocol is set.

What

Claude Code can send its metrics and logs to your own monitoring system using OpenTelemetry (OTLP, a standard format for this data). It now works out which transport protocol to use in one place.

  • If no protocol is set and OTEL_EXPORTER_OTLP_ENDPOINT is missing or not a valid address, Claude Code stops with an error that says so. Before, it only gave a generic "unknown protocol" error. Protocols are set with the OTEL_EXPORTER_OTLP_*_PROTOCOL variables.
  • The endpoint address written to logs is cleaned of sensitive parts.
  • Reports about failed exports now say whether a network connection was reused, how long it had been idle, and how long Claude Code waited, and repeated errors are counted.
Why

A broken monitoring setup now tells you what to fix. If you use an HTTP exporter without setting a protocol, check that exports still arrive, since that case may behave differently now.

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 whether a default protocol is used when the endpoint is valid but no protocol is set.

See this entry in the whole of v2.1.323 →

Feedback