You'll notice
Useful3 Signal2
Claude is told when a mid-merge or conflicted checkout meant your file changes never got sent.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a cloud session's checkout is mid-merge, rebase or cherry-pick, holds unresolved conflicts, has an unborn branch, or cannot be read, Claude is now told this turn's file changes were not sent and instructed not to claim the files arrived.
Evidence
a merge, rebase or cherry-pick is under way in it
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory