{"version":"2.1.280","anchor":"cloud-commits-not-yet-fast-forwarded-into-linked-worktrees","canonical_anchor":"cloud-commits-not-yet-fast-forwarded-into-linked-worktrees","heading":"Cloud commits no longer silently fail to sync into linked git worktrees","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cloud-commits-not-yet-fast-forwarded-into-linked-worktrees","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cloud commits no longer silently fail to sync into linked git worktrees\n\nClaude Code now explicitly tells you when its cloud commits can't be fast-forwarded into a linked git worktree\n\n**What**\n\n- The directory-sync fast-forward path now explicitly detects when the checkout is a linked git working tree and returns a \"waiting\" result with reason `linked_worktree`, instead of falling through to generic git-error handling.\n\n- The user now sees an explicit message explaining that Claude's cloud commits are not fast-forwarded into a linked working tree, though file contents still stay up to date.\n\n**Why** Previously this situation could look like a generic, unexplained sync failure. Now it's called out specifically so someone working from a linked worktree understands why commits aren't showing up there, even though their files stay current.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}