{"version":"2.1.251","anchor":"startup-telemetry-reports-remote-control-availability-drops-","canonical_anchor":"startup-telemetry-reports-remote-control-availability-drops-","heading":"Startup telemetry reports Remote Control availability, drops an old experiment","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/startup-telemetry-reports-remote-control-availability-drops-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Startup telemetry reports Remote Control availability, drops an old experiment\n\nStartup telemetry now reports Remote Control availability and an old experiment field was dropped.\n\n**What**\n\nSession telemetry now sends a `remote_control_available` boolean, true unless `disableRemoteControl` is set, the session is an SDK or print session, or the account is not eligible. Nothing in the product keys off it directly. The related `ide_rc_auto_enable_gate` field still comes from `tengu_ide_rc_auto_enable`, which defaults to off. The `tengu_sable_thrush` field was dropped, retiring that experiment.\n\n**Evidence**\n\n`remote_control_available = b_n()`, `tengu_sable_thrush: import.meta`\n\n- Flag `tengu_ide_rc_auto_enable`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.251; this account: on, anonymous baseline: on, compiled default: off)\n- Flag `tengu_sable_thrush`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.251; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Area: Remote Control\n- Names: `disableRemoteControl`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}