{"version":"2.1.232","anchor":"telemetry-only-managed-settings-get-their-own-approval-promp","canonical_anchor":"telemetry-only-managed-settings-get-their-own-approval-promp","heading":"Telemetry-only managed settings get their own approval prompt","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/telemetry-only-managed-settings-get-their-own-approval-promp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Telemetry-only managed settings get their own approval prompt\n\nA managed telemetry-only setting now prompts by naming the collector, not warning about code execution.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- Matches environment variable names against `\/^OTEL_EXPORTER_OTLP_(?:LOGS_|METRICS_|TRACES_)?ENDPOINT$\/`.\n- Shows a \"Telemetry destination:\" list and advises accepting only if you recognise the collector.\n- The buttons are unchanged: \"Yes, I trust these settings\" and \"No, exit Claude Code\".\n\n**Evidence**\n\n`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.`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}