{"version":"2.1.280","anchor":"telemetry-added-as-a-lazily-loaded-plugin-runtime-module","canonical_anchor":"telemetry-added-as-a-lazily-loaded-plugin-runtime-module","heading":"First-party telemetry rebuilt as an internal plugin module","tier":"use","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/telemetry-added-as-a-lazily-loaded-plugin-runtime-module","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### First-party telemetry rebuilt as an internal plugin module\n\nClaude Code's own analytics pipeline now runs as a plugin module that other builtin plugins call into\n\n**What**\n\n- Claude Code's own telemetry\/analytics pipeline has been rebuilt as a plugin-style module named `telemetry`, added to the same lazily-loaded plugin registry as `agents-md`.\n\n- Other builtin plugins now emit first-party analytics events through `$.telemetry.log` \/ `$.telemetry.mark` rather than through a directly-wired-in pipeline.\n\n- It scans a large number of environment variables (CI, IDE, cloud\/deploy platform, terminal, WSL, GitHub Actions, and more) to build an environment fingerprint that's sent with each event to Anthropic's event-logging endpoint.\n\n**Why** Turning telemetry into a plugin module makes it consistent with how other builtin functionality is loaded, and lets other plugins report analytics through the same shared interface.\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}