{"version":"2.1.246","anchor":"cloud-sessions-retry-permission-mode-changes-and-tell-you-wh","canonical_anchor":"cloud-sessions-retry-permission-mode-changes-and-tell-you-wh","heading":"Cloud sessions retry permission-mode changes and tell you when they drift","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-sessions-retry-permission-mode-changes-and-tell-you-wh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud sessions retry permission-mode changes and tell you when they drift\n\nPermission-mode changes in cloud sessions retry, warn if they drift, and roll back if refused.\n\n**What**\n\nChanging permission mode in a cloud session now sends the change to the session and retries on a 1000\/3000\/9000 ms backoff if it is not delivered. If it never lands you get a notification saying the mode may be out of sync and to press shift+tab to retry; if the session rejects it outright, your local mode rolls back to the last mode the session confirmed.\n\n**Details**\n\n- The two notifications are keyed `remote-permission-mode-unsynced` and `remote-permission-mode-rejected`.\n- Active only for a cloud session that has a control channel and is not viewer-only. No feature flag guards it.\n- The cloud-session handling was reorganised into a single object owning the active remote, message submission, slash-command availability and mode sync. Existing refusals moved onto it with unchanged wording, including the one for `!` bash commands.\n\n**Evidence**\n\n`'!' commands aren't available in cloud sessions yet`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}