{"version":"2.1.283","anchor":"file-sync-treats-incoming-makefile-packagejson-lockfiles","canonical_anchor":"file-sync-treats-incoming-makefile-packagejson-lockfiles","heading":"File sync no longer applies incoming changes to build and instruction files","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/file-sync-treats-incoming-makefile-packagejson-lockfiles","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### File sync no longer applies incoming changes to build and instruction files\n\nFile sync now records a conflict instead of applying incoming changes to Makefiles, package files, lockfiles, CLAUDE.md and AGENTS.md\n\n**Unclear.** How a recorded conflict is shown to you is not clear.\n\n**What**\n\nFile sync copies changes between a cloud session and your machine. It now treats these files as protected names:\n\n- build scripts: Makefile, GNUmakefile, justfile\n\n- package files: package.json, package-lock.json, npm-shrinkwrap.json\n\n- lockfiles: yarn.lock, pnpm-lock.yaml, bun.lock, bun.lockb\n\n- instruction files for Claude and other agents: CLAUDE.md, CLAUDE.local.md, AGENTS.md\n\nMatching also covers the short Windows forms of these names, such as `PACKAG~1.JSO`. When sync would apply an incoming change to one of these files, it records a conflict instead and does not write the file. There is also a new skip reason, `protected_name`, for files that have names this machine protects and were not written.\n\n**Why**\n\nA cloud session can no longer quietly rewrite your build scripts, package files or instruction files on your machine. These files can run code or steer Claude, so you now get to decide whether the change goes in.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}