Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Git InternalsArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release
Unclear The finding does not say what capability readsStanding signals to the client or what behavior it unlocks.
What
When Claude Code syncs a git worktree (a checked-out copy of a repository) between a client and its session, the response now builds its history of applied changes (downApplied) differently depending on whether the client has already acknowledged the current worktree commit. If it has, the history folds in downstream applied changes on top of what was already sent; if not, it falls back to just the reversed sent history. The response also now always includes a new readsStanding flag set to true, alongside the existing acceptsHeldParents flag.
Why
This makes worktree sync responses more accurate for clients that haven't yet caught up to the latest commit, avoiding history that assumes acknowledgment that hasn't actually happened.
