Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Cloud session changes are not pulled back unless this machine is confirmed bound

You'll notice
Useful3 Signal4
Cloud Sessions

If this machine is not confirmed bound, cloud changes stop coming down; your edits still go up.

What

If the device-binding check for this machine does not come back confirmed, directory sync permanently turns off the pull direction for the session and tells you so. Your local edits still go up to the cloud session; nothing comes back down. Skipped pulls are reported with the reason skipped_unbound.

Details
  • The sync session now takes the binding result as an input, and only a positive result enables pull.
  • New peer-liveness notices: after two turns with no confirmation from the other side, the session warns that sync may not be reaching it, and pull events carry peer_stopped and peer_resumed.
Evidence

Files Claude changes in the cloud session won't be copied back to this directory in this session; your other changes here still sync to it

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.238 →