{"version":"2.1.248","anchor":"cloud-agents-and-cloud-sessions-are-refused-in-restricted-se","canonical_anchor":"cloud-agents-and-cloud-sessions-are-refused-in-restricted-se","heading":"Cloud agents and cloud sessions are refused in restricted sessions","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cloud-agents-and-cloud-sessions-are-refused-in-restricted-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cloud agents and cloud sessions are refused in restricted sessions\n\nRestricted sessions fall back to local runs instead of cloud agents or cloud sessions.\n\n**What**\n\nAsking a Task to run with cloud isolation now falls back to a local or worktree run when the session is restricted, in addition to the existing fallbacks for no claude.ai login and the feature being off, and the log line names which reason applied. Creating a cloud session likewise bails out early with a restricted-session reason.\n\n**Details**\n\n- Cloud session creation already refused under a managed policy that disallows remote sessions, and requires the first-party Anthropic API provider; the restricted check joins those.\n\n**Evidence**\n\n`(no claude.ai login or feature gate off)`, `Cloud sessions are only available on the first-party Anthropic API provider.`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}