{"version":"2.1.285","anchor":"remote-home-settings-toggle-can-be-blocked-with-a-reason","canonical_anchor":"remote-home-settings-toggle-can-be-blocked-with-a-reason","heading":"Turning on this machine's settings for cloud sessions can now be blocked with a reason","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/remote-home-settings-toggle-can-be-blocked-with-a-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Turning on this machine's settings for cloud sessions can now be blocked with a reason\n\nThe 'Use this machine's settings in cloud sessions' toggle now checks first and can say why it cannot turn on; in this build it reports unsupported\n\n**Unclear.** Which situations can block the change is not known.\n\n**What**\n\nClaude Code can run sessions in the cloud and forward your local settings to them, controlled by the `remoteHomeSettings` toggle, shown as 'Use this machine's settings in cloud sessions'. Before, changing this toggle always went ahead.\n\n- The toggle and the home-settings prompt now run a check before making the change.\n\n- If the check fails, the change is stopped with a reason, starting \"Could not turn this on\". There are two reasons: 'unsupported' and 'flag_off'. For example: \"Could not turn this on: forwarding settings to cloud sessions is not available in this version\".\n\n- In this build, the check always reports 'unsupported'.\n\n**Why**\n\nIf you try to forward your settings to cloud sessions and it does not work, you now see a message saying why, instead of the toggle appearing to succeed.\n\n- Area: Managed Settings\n- Names: `remoteHomeSettings`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}