{"version":"2.1.280","anchor":"working-tree-upload-refusal-gains-three-new-integrity-checks","canonical_anchor":"working-tree-upload-refusal-gains-three-new-integrity-checks","heading":"Working-tree upload refusal gains three new integrity checks","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/working-tree-upload-refusal-gains-three-new-integrity-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Working-tree upload refusal gains three new integrity checks\n\nGit upload safety scanner adds checks for same-bytes, hardlinked, and unexamined files\n\n**What**\n\nThe safety scanner that Claude Code runs before uploading a working tree already refused uploads containing 'forged' paths or 'alias' (8.3 short-name) paths. It now also refuses uploads in three more cases:\n\n- a 'same-bytes' entry: a file in the index that is byte-for-byte identical to a file meant to stay local, placed there by something other than the upload process itself\n\n- a 'hardlinked' changed file: a file that is a second hard link to something outside the tracked tree\n\n- an 'unexamined' file: a path that could not be safely inspected\n\n**Why**\n\nThese checks close off ways a local-only file's contents could end up uploaded indirectly, either by being duplicated under a different name, linked from outside the tree, or slipping past inspection.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}