Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.229 Home All releases ←olderv2.1.228 v2.1.231newer→
Claude Code v2.1.229

OpenTelemetry can be sent through Anthropic's first-party gateway

Use it now
Useful2 Signal4
Telemetry Notable

Telemetry can route through Anthropic's own gateway, but only under a narrow set of conditions.

ANTHROPIC_BASE_URLANTHROPIC_AUTH_TOKENCLAUDE_CODE_PROVIDER_MANAGED_BY_HOST
What

Telemetry export now decides per signal (metrics, logs, traces) whether to send OTLP data to a gateway endpoint derived from ANTHROPIC_BASE_URL, authenticated with a Bearer header from ANTHROPIC_AUTH_TOKEN. It only does this when CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST is set, the auth mode is first-party/gateway, the token is scoped to the gateway audience, you have set no OTLP headers of your own, and your OTLP endpoint already matches the derived URL. Any other combination sends nothing.

Details
  • The check runs separately for each signal, so metrics can qualify while traces do not.
  • User-set OTEL_EXPORTER_OTLP_* headers disqualify the signal outright, so your own collector configuration is never overridden.
  • Falls back to returning "do not send" rather than erroring.
Evidence

claude-gateway

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.229 →