{"version":"2.1.282","anchor":"remote-file-sync-first-upload-now-supports-linked-git-workt","canonical_anchor":"remote-file-sync-first-upload-now-supports-linked-git-workt","heading":"Cloud file sync handles linked git worktrees on first upload","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/remote-file-sync-first-upload-now-supports-linked-git-workt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud file sync handles linked git worktrees on first upload\n\nThe first file upload to a cloud session now handles linked git worktrees, and refuses with a reason when the setup looks unsafe\n\n**Unclear.** It is not clear whether linked worktrees were already turned away elsewhere before, so this may be new support or only added safety checks.\n\n**What**\n\nA linked git worktree is an extra working folder attached to a git repository that lives somewhere else. When the first upload of files to a cloud session starts from such a folder, Claude Code now handles it. It refuses the upload when:\n\n- the repository's own settings would change how git behaves\n\n- it cannot set up a private git folder to check the current commit\n\n- a link has been planted in the repository behind the worktree\n\n- the folder layout no longer matches what was checked earlier\n\nThere is a new failure cause, `admin_dir`.\n\n**Why**\n\nIf you start cloud sessions from a git worktree, file sync can now work, or fail with a clearer reason, rather than trusting a repository set up in a risky way.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}