{"version":"2.1.282","anchor":"remote-file-sync-capture-points-no-longer-snapshot-synchron","canonical_anchor":"remote-file-sync-capture-points-no-longer-snapshot-synchron","heading":"Cloud file sync now queues save points instead of waiting for them","tier":"internal","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/remote-file-sync-capture-points-no-longer-snapshot-synchron","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud file sync now queues save points instead of waiting for them\n\nIn cloud sessions with file sync, saving a capture point now queues an upload and reports it as queued instead of waiting for a snapshot\n\n**Unclear.** It is not known which sessions have file sync turned on.\n\n**What**\n\nFile sync keeps a folder's files in step with a cloud session, a Claude Code session that runs on Anthropic's servers. At certain moments it records a capture point, a snapshot of the files to send.\n\nBefore, Claude Code waited for a snapshot check at each capture point and reported whether files were being sent, were unchanged, or could not be snapshotted. It now queues the upload and reports it as queued, unless the files are being kept locally or sync has already failed. The telemetry for capture points no longer records how long the check and snapshot took.\n\n**Why**\n\nCapture points should return faster. The trade-off is that the step recording them no longer learns straight away whether anything changed.\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}