{"version":"2.1.282","anchor":"upload-checks-tampered-and-legacy-tree-now-classified-a","canonical_anchor":"upload-checks-tampered-and-legacy-tree-now-classified-a","heading":"Files that change during a cloud upload are now reported as unreadable","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/upload-checks-tampered-and-legacy-tree-now-classified-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Files that change during a cloud upload are now reported as unreadable\n\nTwo upload failures, a file that changed mid-check and an old-style tree, now show the unreadable-file message instead of a git error\n\n**Unclear.** It is not clear what produces the `legacy_tree` failure.\n\n**What**\n\nWhen Claude Code checks files before uploading them for a cloud session, two kinds of failure are now reported as \"unreadable\" instead of falling through to the generic git error:\n\n- `tampered`: the file's identity on disk changed between two checks.\n\n- `legacy_tree`: an older kind of file tree.\n\n**Why**\n\nYou now see the unreadable-file message, which points closer to the real problem than a generic git error.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}