{"version":"2.1.284","anchor":"cloud-directory-file-sync-gains-device-bound-signing-and-a","canonical_anchor":"cloud-directory-file-sync-gains-device-bound-signing-and-a","heading":"Cloud file sync signs files per device and explains when that fails","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/cloud-directory-file-sync-gains-device-bound-signing-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud file sync signs files per device and explains when that fails\n\nCloud file sync now signs synced files with a key for this computer, and stops with a clear message if that cannot be set up\n\n**Unclear.** Whether this is controlled by the remote switch it appears to be is not confirmed.\n\n**What**\n\nCloud file sync copies your project files into a cloud session started with `--cloud`. Sync now signs the synced files with a key tied to your computer. If that cannot be set up, sync stops with a message explaining why. This happens when the cloud did not register your computer as a device for the session, or its device key could not be read. The message suggests running without sync: `CLAUDE_CODE_DIR_SYNC_ENGINE=none claude --cloud`.\n\nThis part of file sync is off unless it is switched on remotely.\n\n**Why**\n\nWhen device registration fails, sync now stops rather than sending unsigned files. The message gives you a way to keep working without sync.\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.284; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_DIR_SYNC_ENGINE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}