{"version":"2.1.286","anchor":"remote-control-cloud-policy-check-helper","canonical_anchor":"remote-control-cloud-policy-check-helper","heading":"Organization policy blocks on remote features now come with a specific reason","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/remote-control-cloud-policy-check-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Organization policy blocks on remote features now come with a specific reason\n\nA single check now matches Remote Control and cloud sessions to their organization policies and returns a clear message when one is turned off\n\n**Unclear.** It is not clear which parts of Claude Code call this check.\n\n**What**\n\nClaude Code now has one check that takes a remote feature (Remote Control, a cloud session, or one it does not recognize) and looks up the organization policy that governs it: `allow_remote_control` or `allow_remote_sessions`. When access is refused, the check says whether data residency (where your organization's data must be kept) or a policy caused it, and gives a message such as:\n\n- Remote Control was turned off by your organization's policy.\n\n- Session mirroring was turned off by your organization's policy (allow_remote_sessions).\n\n**Why**\n\nIf your organization has turned a remote feature off, you can be told which policy did it instead of just seeing it fail.\n\n- Area: Remote Control\n- Names: `allow_remote_control`, `allow_remote_sessions`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}