{"version":"2.1.283","anchor":"remote-session-attach-stops-early-with-arm-failed-when-the-s","canonical_anchor":"remote-session-attach-stops-early-with-arm-failed-when-the-s","heading":"Attaching a synced cloud session now stops early when its anchor is missing","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/remote-session-attach-stops-early-with-arm-failed-when-the-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Attaching a synced cloud session now stops early when its anchor is missing\n\nAttaching a cloud session with folder sync now stops at once with an explanation when the git anchor for syncing is unavailable\n\n**Unclear.** The condition under which this check runs is not stated.\n\n**What**\n\nSome cloud sessions keep a folder on your machine in sync with the session. The sync uses the folder's git root, the top of the repository, as its anchor.\n\nWhen you attach such a session, Claude Code now checks that anchor first. If the check reports that the anchor is unavailable, the session stops at once, marked as failing to arm, and shows a line saying it is not bound to this machine.\n\n**Why**\n\nAttaching now fails straight away with a reason. Before, it might have set up and then broken later.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}