{"version":"2.1.281","anchor":"new-exit-notice-when-cloud-session-changes-had-not-finished","canonical_anchor":"new-exit-notice-when-cloud-session-changes-had-not-finished","heading":"New exit notice when cloud-session changes had not finished syncing locally","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-exit-notice-when-cloud-session-changes-had-not-finished","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New exit notice when cloud-session changes had not finished syncing locally\n\nExiting while cloud-session changes are still syncing now shows a notice that they stay in the cloud and sync next time\n\n**What**\n\nA cloud session is a Claude Code session that runs on a remote machine. Its changes can be pulled into a folder on your computer. If Claude Code exits while those changes are still being fetched or installed into your folder, it now shows a notice.\n\nThe notice says the changes remain in the cloud session. They will sync the next time you open that session from the same folder.\n\n**Why**\n\nBefore this, quitting partway through a sync gave no sign that your local folder was missing Claude's latest work. Now you are told, and you know that reopening the session from that folder will finish the sync.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}