{"version":"2.1.281","anchor":"cloud-session-better-recovery-when-a-launch-or-create-permi","canonical_anchor":"cloud-session-better-recovery-when-a-launch-or-create-permi","heading":"Cloud session: better recovery when a launch or create permission mode is refused","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-session-better-recovery-when-a-launch-or-create-permi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud session: better recovery when a launch or create permission mode is refused\n\nCloud sessions recover more reliably when the permission mode you asked for is refused, with retries and a notice if they fail\n\n**Unclear.** The finding does not say what the notice shown after the retry helper gives up says.\n\n**What**\n\nA permission mode is the setting that controls how freely Claude may act before asking you. When a cloud session (one running on a remote machine rather than your own) refuses the mode you asked for, Claude Code now handles it more carefully:\n\n- Refused at creation: the client records a converge entry and releases it once the follow-up is accepted.\n\n- Refused at launch: the fallback `default` mode it then sends goes through a retry helper instead of a single unchecked request, and if the helper gives up, a notice is shown.\n\n- Connection down: a new `linkDown` check tells the creation step that the connection is not available.\n\n- Mode warning: the message \"This cloud session is in ${xd} mode; your ${da} setting wasn't applied.\" is now decided once per session, and is not shown when the session's label shows you set that mode yourself.\n\n**Why**\n\nA refused mode is less likely to leave the session in an unexpected mode without you knowing, and the mismatch warning no longer appears for a mode you chose."}