{"version":"2.1.268","anchor":"cloudremote-commands-now-share-a-common-policy-gate-object","canonical_anchor":"cloudremote-commands-now-share-a-common-policy-gate-object","heading":"Cloud\/remote commands now share a common policy gate object and 'claude-ai' availability tag","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/cloudremote-commands-now-share-a-common-policy-gate-object","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Cloud\/remote commands now share a common policy gate object and 'claude-ai' availability tag\n\nCloud-related commands now share one policy gate requiring an 'allow_remote_sessions' organization policy\n\n**What**\n\nThe `remote-control`, `teleport`, `autofix-pr`, plan-in-web (\"Draft an editable plan...\"), and `remote-env` commands now all declare the same availability tag, `claude-ai`, and the same shared policy gate, which checks for an `allow_remote_sessions` organization policy under the feature label \"Cloud sessions.\"\n\n**Why**\n\nThis consolidates how these cloud-dependent commands check organization permissions, so an organization can now allow or block all of these cloud session features together through one consistent policy rather than separate checks per command.\n\n- Area: Cloud Sessions\n- Names: `allow_remote_sessions`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}