{"version":"2.1.284","anchor":"new-device-unbound-reason-why-a-project-directorys-files","canonical_anchor":"new-device-unbound-reason-why-a-project-directorys-files","heading":"Cloud file sync can now stop because this computer can't sign its uploads","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/new-device-unbound-reason-why-a-project-directorys-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud file sync can now stop because this computer can't sign its uploads\n\nSyncing a folder's files to a cloud session now stops, with a message, when this computer can't sign uploads as the device tied to the session\n\n**Unclear.** Whether this path is behind a switch, and what that switch defaults to, is not stated.\n\n**What**\n\nClaude Code can send a folder's files to a cloud session. That sync now stops when this computer has no key to sign the files with. You see: \"This computer could not be set up to sign synced files (the cloud did not bind it to the session as a device, or its device key could not be read), so this directory's files were not sent.\"\n\nA related reason explains that the computer could not sign uploads as the device the session is bound to, which the cloud requires.\n\n**Why**\n\nCloud sync now appears to require uploads to be signed by a device tied to the session. If your files were not sent, this message says why.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}