{"version":"2.1.280","anchor":"new-telemetry-remote-control-entry-feature-logging","canonical_anchor":"new-telemetry-remote-control-entry-feature-logging","heading":"New telemetry: remote_control_entry feature logging","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-telemetry-remote-control-entry-feature-logging","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New telemetry: remote_control_entry feature logging\n\nClaude Code now logs telemetry around remote-control session entry and exit\n\n**What**\n\nClaude Code now calls a new logging helper, `logFeatureBadAsync`, with the feature name `remote_control_entry` and an outcome string such as `registration_failed` or `trusted_device_unenrolled`, around the points where a remote-control session begins and ends. This runs alongside the existing `flushAnalyticsBeforeExit` call.\n\n**Why**\n\nThis gives visibility into how remote-control sessions start and fail, which can help diagnose issues like a device losing its trusted status or failing to register.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}