{"version":"2.1.246","anchor":"folder-sync-now-says-out-loud-when-it-has-stopped","canonical_anchor":"folder-sync-now-says-out-loud-when-it-has-stopped","heading":"Folder sync now says out loud when it has stopped","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/folder-sync-now-says-out-loud-when-it-has-stopped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Folder sync now says out loud when it has stopped\n\nWhen folder sync stops, you're told the reason and to start a new cloud session.\n\n**What**\n\nWhen a cloud session tied to a local folder stops syncing, Claude Code now prints the reason instead of going quiet: the cloud session never picked up anything sent from the folder, the local sync store is missing or unreadable, or the folder's files could not be recorded when the session opened. Each message tells you to start a new cloud session from that folder.\n\n**Details**\n\n- The local sync store is the on-disk record of what has been sent; if it cannot be read, that session cannot resume syncing at all.\n- A separate notice explains that files replaced or deleted by sync are moved to a trash directory on your machine rather than thrown away.\n- Only appears for folder-backed cloud sessions.\n\n**Evidence**\n\n`This folder is not syncing: this session's local sync store is missing or unreadable on this machine. Start a new cloud session from this folder to sync again.`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}