{"version":"2.1.284","anchor":"teleport-directory-sync-upload-only-no-longer-suppresses-de","canonical_anchor":"teleport-directory-sync-upload-only-no-longer-suppresses-de","heading":"Cloud sessions from a local folder are archived if they cannot bind to this machine","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/teleport-directory-sync-upload-only-no-longer-suppresses-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud sessions from a local folder are archived if they cannot bind to this machine\n\nUpload-only folder sync can now bind to your machine, and a folder cloud session that cannot bind is archived instead of created\n\n**Unclear.** It is not established what controls whether this folder sync feature is available at all.\n\n**What**\n\nClaude Code can start a cloud session from a folder on your computer and keep that folder in sync. A cloud session is one that runs on remote servers rather than locally. Two things differ in how these sessions attach to your machine:\n\n- `upload_only` sync consent no longer stops the session from being bound to this machine.\n\n- Binding refused for a folder cloud session means the session is archived and creation fails with a `device_unbound` error.\n\nThe sync process now also receives the ID of the machine the session is bound to.\n\n**Why**\n\nThis changes what you see when a cloud session made from a local folder cannot attach to your computer: the session is archived and not created, instead of continuing unbound.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}