{"version":"2.1.282","anchor":"directory-sync-exiting-mid-upload-now-only-warns-and-no-lon","canonical_anchor":"directory-sync-exiting-mid-upload-now-only-warns-and-no-lon","heading":"Leaving a cloud session mid-upload now warns instead of trying one last upload","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/directory-sync-exiting-mid-upload-now-only-warns-and-no-lon","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Leaving a cloud session mid-upload now warns instead of trying one last upload\n\nIf file sync is still uploading when you exit, Claude Code now only warns you; the rest goes up with your first message next time\n\n**Unclear.** It is not known what causes a sync to end with the \"detached\" reason.\n\n**What**\n\nIf you exit Claude Code while file sync is still uploading changes to a cloud session, Claude Code now prints a warning and stops. It no longer tries a final upload on the way out. The warning says that anything that did not go up will be sent with your first message next time.\n\nThe record of an ended sync can also now carry a new \"detached\" reason.\n\n**Why**\n\nExiting a cloud session no longer waits on a last upload. Unfinished changes wait for your next session instead.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}