{"version":"2.1.284","anchor":"file-sync-off-explanation-for-linked-worktrees-and-separate","canonical_anchor":"file-sync-off-explanation-for-linked-worktrees-and-separate","heading":"Cloud sessions explain why file sync is off in git worktrees","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/file-sync-off-explanation-for-linked-worktrees-and-separate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud sessions explain why file sync is off in git worktrees\n\nIn a linked git worktree, or a checkout whose git folder lives elsewhere, Claude Code says file sync is off and the session starts from GitHub\n\n**Unclear.** It is not clear which command shows these messages, or whether a server-side setting controls them.\n\n**What**\n\nClaude Code can copy your local files into a cloud session. The messages Claude Code shows when it cannot do that have changed. In these two kinds of checkout, it now says file sync is off for the session:\n\n- a linked working tree, made with `git worktree add`\n\n- a checkout that keeps its git directory outside the working tree, either through a `.git` file or a git directory somewhere else\n\nThe message also says the session starts from the tip of the branch on GitHub.\n\n**Why**\n\nIf you work in git worktrees, you get a clear reason why your local changes did not reach the cloud session. Push the branch first if you want the cloud session to have your latest work.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}