{"version":"2.1.242","anchor":"telemetry-payload-churn-around-analytics-status-and-device-b","canonical_anchor":"telemetry-payload-churn-around-analytics-status-and-device-b","heading":"Telemetry payload churn around analytics status and device bash","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/telemetry-payload-churn-around-analytics-status-and-device-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Telemetry payload churn around analytics status and device bash\n\nEvents now flag when analytics are off, which editor clients use to hide thumbs feedback that would do nothing.\n\n**What**\n\nOne event payload stops carrying a field about withheld device bash, and another gains a flag saying analytics are off, which the schema documents as the signal IDE clients use to hide per-message thumbs feedback when rating would do nothing.\n\n**Details**\n\n- The flag's value reflects the configured privacy level, the `DO_NOT_TRACK` environment variable, or use of a third-party model provider.\n\n**Evidence**\n\n`@internal True when the CLI has analytics\/telemetry disabled (privacy level, DO_NOT_TRACK, or 3P provider).`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}