{"version":"2.1.301","anchor":"file-transfer-uploads-written-under-a-lock-and-a-per-session","canonical_anchor":"file-transfer-uploads-written-under-a-lock-and-a-per-session","heading":"Received transfer files are saved to the uploads folder in a safer way","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/file-transfer-uploads-written-under-a-lock-and-a-per-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Received transfer files are saved to the uploads folder in a safer way\n\nFiles received through file transfer are now written by first taking hold of the uploads folder and releasing it afterward\n\n**What**\n\nWhen Claude Code receives a file through file transfer, it saves the file in an uploads folder. It used to create that folder and then write the file straight into it. Now it first takes hold of the folder, writes the file through it, and releases the folder when done. If saving fails, the error still says the file could not be written to the uploads directory.\n\n**Why**\n\nThis makes the handling of uploaded files more robust.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}