{"version":"2.1.287","anchor":"cloud-session-default-respects-org-policy","canonical_anchor":"cloud-session-default-respects-org-policy","heading":"Organization policy can now block cloud sessions","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-session-default-respects-org-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Organization policy can now block cloud sessions\n\nCloud sessions, including launching in the cloud by default, now respect an organization policy that can deny them\n\n**Unclear.** It is not clear what the default-to-cloud setting is or how it is turned on.\n\n**What**\n\nA cloud session is one that runs on remote servers instead of your own machine. Claude Code now checks whether your organization's policy denies cloud sessions (`cloudSessionsDeniedByOrgPolicy`).\n\n- A launch that would go to the cloud by default now waits for the policy first. When the policy denies it, Claude Code records organization policy as the reason.\n\n- The result of applying cloud-session settings can now be `not_allowed`. Before, it could only be none, declined or applied.\n\n- A check for whether the launch folder is a monorepo (one repository holding several projects) was also added, with a `noMonorepo` option.\n\n**Why**\n\nOrganizations can stop their members' sessions from going to the cloud, including by default. If your sessions stay local unexpectedly, your organization's policy may be the reason.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}