Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.274 ·

Managed settings can now be reported to telemetry

A new OTEL_LOG_MANAGED_SETTINGS env var adds managed/policy settings details to telemetry, with sensitive values redacted

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaManaged Settingswhat it touches
KindInternal Changesin v2.1.274,
Group of 2 Under the hood

A new OTEL_LOG_MANAGED_SETTINGS env var adds managed/policy settings details to telemetry, with sensitive values redacted

What

  • A new environment variable, OTEL_LOG_MANAGED_SETTINGS, is now recognized as an OpenTelemetry-related setting.
  • A new telemetry event, managed_settings_resolved, reports metadata about how managed (policy-controlled) settings were resolved: their source, behavior, helper state, whether a helper was applied, and the entry's key, path, and script hash.
  • If OTEL_LOG_MANAGED_SETTINGS is set, this event also includes the actual resolved settings content. Values are redacted to [REDACTED] unless they match the expected tool/permission-rule/value schema, are known tool names, or match an mcp__ tool naming pattern.

Why

This gives administrators visibility into how managed/policy settings are being resolved across an organization's machines, useful for auditing and debugging configuration issues, while redaction keeps unexpected or sensitive values from leaking into telemetry unless explicitly opted in.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded claude_code.managed_settings_resolved OTel event: managed-settings sources and policy helper state; redacted settings and digests with…

See this entry in the whole of v2.1.274 →

Feedback