{"version":"2.1.282","anchor":"directory-sync-linked-worktrees-are-no-longer-deferred-exce","canonical_anchor":"directory-sync-linked-worktrees-are-no-longer-deferred-exce","heading":"Cloud file sync's skip message now names linked worktrees only on Windows and WSL","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/directory-sync-linked-worktrees-are-no-longer-deferred-exce","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud file sync's skip message now names linked worktrees only on Windows and WSL\n\nThe message for checkouts that cloud file sync skips now lists linked worktrees only on Windows or WSL, alongside submodules and separate git folders\n\n**Unclear.** Only the message changed visibly, so it is not confirmed that linked worktrees outside Windows and WSL are now actually synced.\n\n**What**\n\nCloud file sync copies your local files to a cloud session. For some kinds of checkout it defers syncing and says why. Before, that message listed any linked working tree (made with `git worktree add`) and any checkout that keeps its git folder elsewhere.\n\nThe message now names only checkouts that keep their git folder elsewhere:\n\n- a submodule\n\n- a separate git folder\n\n- a linked working tree on Windows or WSL\n\n**Why**\n\nPeople who use `claude --cloud` from an ordinary linked worktree on other systems may now get file sync.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}