{"version":"2.1.238","anchor":"cloud-session-changes-are-not-pulled-back-unless-this-machin","canonical_anchor":"cloud-session-changes-are-not-pulled-back-unless-this-machin","heading":"Cloud session changes are not pulled back unless this machine is confirmed bound","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/cloud-session-changes-are-not-pulled-back-unless-this-machin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Cloud session changes are not pulled back unless this machine is confirmed bound\n\nIf this machine is not confirmed bound, cloud changes stop coming down; your edits still go up.\n\n**What**\n\nIf 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`.\n\n**Details**\n\n- The sync session now takes the binding result as an input, and only a positive result enables pull.\n- 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`.\n\n**Evidence**\n\n`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`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}