{"version":"2.1.285","anchor":"remote-machine-project-sync-coerced-off-without-an-engine","canonical_anchor":"remote-machine-project-sync-coerced-off-without-an-engine","heading":"Remote project sync is treated as off when no sync engine is available","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/remote-machine-project-sync-coerced-off-without-an-engine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Remote project sync is treated as off when no sync engine is available\n\nWith no sync engine, a remote machine set to two_way or upload_only project sync is treated as off, and the separate-copy hint is always shown\n\n**Unclear.** How Claude Code decides that no sync engine is available is not stated.\n\n**What**\n\nA remote machine can be set to sync your project files with `two_way` or `upload_only`. Claude Code now treats both settings as `off` when no sync engine is available. The sync engine is the part that does the copying.\n\nThe hint saying the remote machine works on a separate copy of your files is now always shown. Before, `two_way` and `upload_only` showed a different hint about leaving out files git ignores.\n\n**Why**\n\nWhen reading files on a remote machine, you may now see the separate-copy hint where you used to see the git-ignore hint.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}