{"version":"2.1.222","anchor":"remotecontrolatstartup-can-no-longer-be-turned-on-by-repo-sc","canonical_anchor":"remotecontrolatstartup-can-no-longer-be-turned-on-by-repo-sc","heading":"remoteControlAtStartup can no longer be turned on by repo-scoped settings","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/remotecontrolatstartup-can-no-longer-be-turned-on-by-repo-sc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### remoteControlAtStartup can no longer be turned on by repo-scoped settings\n\nA cloned repo's settings can no longer switch on Remote Control at startup; only your own settings can.\n\n**What**\n\nA checked-in project or local settings file can no longer enable Remote Control at startup, closing off a path where cloning a repo changed your startup behaviour.\n\n**Details**\n\n- The setting is read through the security-sensitive settings path, so only user, policy or flag scope can enable it.\n- Project and local settings can still disable it: a false value wins.\n- A true value at repo scope is ignored and logged.\n- `projectSettings` is ignored entirely when it aliases user settings.\n\n**Evidence**\n\n`repo-scoped settings cannot enable Remote Control; set it at user scope (\/config)`\n\n- Area: Permissions\n- Names: `remoteControlAtStartup`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}