{"version":"2.1.269","anchor":"new-remote-control-config-field-remote-control-auto-connect","canonical_anchor":"new-remote-control-config-field-remote-control-auto-connect","heading":"New remote-control config field: remote_control_auto_connect_default","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-remote-control-config-field-remote-control-auto-connect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New remote-control config field: remote_control_auto_connect_default\n\nIDEs can now see the org-level default for Remote Control auto-connect separately from the user's own setting\n\n**What**\n\nA new field, `remote_control_auto_connect_default`, is now sent to IDE hosts. It reports the organization or Growth Book (feature-flagging) default for whether Remote Control should auto-connect, separately from the explicit `remoteControlAtStartup` setting a user may have configured.\n\n**Why**\n\nThis lets an IDE correctly show the state of the auto-connect toggle even after the older `remoteControlAtStartup` setting key gets cleared mid-session, since it no longer has to infer the default from that legacy value alone.\n\n- Area: Remote Control\n- Names: `remote_control_auto_connect_default`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}