{"version":"2.1.310","anchor":"telemetry-init-now-conditionally-runs-an-extra-step-under-te","canonical_anchor":"telemetry-init-now-conditionally-runs-an-extra-step-under-te","heading":"Usage reporting can run an extra setup step under a remote switch","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/telemetry-init-now-conditionally-runs-an-extra-step-under-te","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Usage reporting can run an extra setup step under a remote switch\n\nWhen a remote switch is on, Claude Code now runs an extra step before starting its usage reporting\n\n**Unclear.** It is not stated what the extra step does.\n\n**What**\n\nClaude Code sends usage reports (telemetry, meaning automatic background data about how the program is running). When it starts that reporting, it now runs an extra step first if a remote switch is on. Previously it only started the reporting.\n\n**Why**\n\nThis adds a step to usage reporting that only runs where the switch is turned on.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}