{"version":"2.1.248","anchor":"large-directory-sync-downloads-survive-an-expired-token-mid-","canonical_anchor":"large-directory-sync-downloads-survive-an-expired-token-mid-","heading":"Large directory-sync downloads survive an expired token mid-transfer","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/large-directory-sync-downloads-survive-an-expired-token-mid-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Large directory-sync downloads survive an expired token mid-transfer\n\nBig sync downloads now resume after a token expires mid-transfer instead of restarting.\n\n**What**\n\nWhen Claude Code downloads a file directly during a directory sync, a token expiring partway through no longer restarts or corrupts the transfer. Bytes already received are kept, a fresh read token is fetched, and the download resumes from where it stopped.\n\n**Details**\n\n- New read tokens are only issued while the transfer is actually making progress, so a stuck download cannot loop forever.\n- The file's etag is checked to be unchanged between attempts; if the file changed on the server the download does not silently splice two versions.\n- A stall timeout parameter was added.\n- Giving up produces a warning naming exactly how many bytes of the file had arrived.\n\n**Evidence**\n\n`dir-sync: direct download gave up after ${A} read tokens at ${O.received} of ${r.size} bytes`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}