You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What
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.
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.
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.
