{"version":"2.1.224","anchor":"startup-remote-control-setting-now-tracks-where-its-value-ca","canonical_anchor":"startup-remote-control-setting-now-tracks-where-its-value-ca","heading":"Startup remote-control setting now tracks where its value came from","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/startup-remote-control-setting-now-tracks-where-its-value-ca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Startup remote-control setting now tracks where its value came from\n\nRemote control startup now records where its on\/off value came from, but nothing reads that yet.\n\n**What**\n\nResolving whether remote control is on at startup now returns the origin of the value as well: managed policy, a command-line flag, user settings, an older global config value, a project or local setting turning it off, or nothing set. The warning that repo-scoped settings are ignored is unchanged. Nothing in the build was found reading the origin.\n\n**Evidence**\n\n`legacy_global_config`\n\n- Area: Remote Control\n- Names: `remoteControlAtStartup`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}