You'll notice
Useful4 Signal2
Permission-mode changes in cloud sessions retry, warn if they drift, and roll back if refused.
What's wrong with this entry?
Anonymous. No account, no email.
What
Changing 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.
Details
- The two notifications are keyed
remote-permission-mode-unsyncedandremote-permission-mode-rejected. - Active only for a cloud session that has a control channel and is not viewer-only. No feature flag guards it.
- 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.
Evidence
'!' commands aren't available in cloud sessions yet
Strings lifted out of the shipped bundle, so the claim above can be checked against them.