You'll notice
Useful3 Signal3
When file sync stops, Claude is told the remote copy is stale or emptied and works locally.
What's wrong with this entry?
Anonymous. No account, no email.
What
The notice that tells the model which directory to work in now covers sessions where file sync stopped: the remote copy is marked EMPTIED if it was cleared, STALE if it was not, or left described as untouched. When the copy was cleared, the recommended place to work flips to the local machine.
Evidence
EMPTIED when file sync stopped for this session
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