{"version":"2.1.277","anchor":"file-sync-staging-now-uses-an-ownershippermission-checked-p","canonical_anchor":"file-sync-staging-now-uses-an-ownershippermission-checked-p","heading":"File-sync staging now uses an ownership\/permission-checked private folder, with the old auto-cleanup keyed differently","tier":"notice","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/file-sync-staging-now-uses-an-ownershippermission-checked-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### File-sync staging now uses an ownership\/permission-checked private folder, with the old auto-cleanup keyed differently\n\nFile sync now stages files in a private, permission-checked folder and skips it during cleanup\n\n**What**\n\nWhen Claude Code syncs files, it now moves them through a dedicated staging folder that is locked down to the current user only (permission mode 0700, meaning only the owner can read, write or enter it). Before using this folder, Claude Code checks that it and its parent folder are genuinely owned by the current user with no group or other access. If the check fails, it deletes the folder and refuses to use it, reporting one of several specific reasons: it could not be created, it is not owned solely by the current user (which can happen on drives that don't preserve file permissions), or it turned out to be a symbolic link or another user's folder.\n\nThe existing cleanup routine that removes old staging folders has also been updated to skip the one that is currently in active use.\n\n**Why**\n\nThis prevents another user on a shared machine from tampering with or reading files while they're being staged for sync, and stops the cleanup process from accidentally deleting a staging folder that a sync is actively using.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}