You'll notice
Useful3 Signal3
New cloud sessions now tell the cloud which permission mode they started in, falling back if refused.
What's wrong with this entry?
Anonymous. No account, no email.
What
A freshly created cloud session now records the permission mode it started in and pushes it to the cloud side once, retrying on failure. Previously only sessions attaching to an existing conversation pushed a mode, and only plan mode. If the cloud side refuses, the local mode falls back to default with a notification; if the retries give up, a warning notification appears.
Details
- Applies only when creating a session rather than attaching, and not for viewer-only sessions. It is additionally behind a feature check whose in-source default is not stated, so whether it runs is decided by server configuration.
- The retry helper tracks which mode was last observed on the wire and whether the launch mode was already reported; a repeat attempt logs
[useRemoteSession] Create permission mode already pushed for this session. - The give-up warning is keyed
remote-create-mode-unrecorded.
Evidence
remote-create-mode-unrecorded
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.