Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

OTLP trace exporters get an export-outcome hook, skipped when the traces endpoint is the startup gateway

OpenTelemetry trace exports now report each export's result through a callback, except when traces go to the startup gateway

Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release
What

Claude Code can send traces to a telemetry service you choose, using OpenTelemetry (OTLP). A trace is a timed record of the steps in a piece of work. The service address comes from the environment variable OTEL_EXPORTER_OTLP_TRACES_ENDPOINT.

A new check looks at that address. If it matches an address known when Claude Code started and its path is for traces, it counts as the startup gateway. In every other case, Claude Code now records which protocol is used and whether the export goes through a proxy ({protocol, viaProxy}), and calls a result callback after each export.

The "[3P telemetry] First ... export" debug message is unchanged.

Why

If you send traces to your own telemetry service, Claude Code now tracks how each export went. When traces go to the startup gateway, this extra tracking is skipped.

Read from
What the documentation says
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 doubtThe finding does not say what the per-export callback does with each result.

See this entry in the whole of v2.1.281 →

Feedback