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.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Telemetry-only managed settings get their own approval prompt

You'll notice
Useful2 Signal2
Managed Settings

A managed telemetry-only setting now prompts by naming the collector, not warning about code execution.

What

If the only setting your organization pushed that needs approval is an OpenTelemetry endpoint variable, and there are no shell settings, hooks or CLAUDE.md, the startup prompt now names the collector instead of warning about arbitrary code execution.

Details
  • Matches environment variable names against /^OTEL_EXPORTER_OTLP_(?:LOGS_|METRICS_|TRACES_)?ENDPOINT$/.
  • Shows a "Telemetry destination:" list and advises accepting only if you recognise the collector.
  • The buttons are unchanged: "Yes, I trust these settings" and "No, exit Claude Code".
Evidence

Your organization has configured Claude Code to send telemetry to the destination below., Only accept if you recognize this as your organization's telemetry collector.

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.232 →