{"version":"2.1.282","anchor":"claude-cloud-refuses-repositories-with-a-git-symlink-or-g","canonical_anchor":"claude-cloud-refuses-repositories-with-a-git-symlink-or-g","heading":"claude --cloud refuses repositories that could steer file sync's git","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/claude-cloud-refuses-repositories-with-a-git-symlink-or-g","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### `claude --cloud` refuses repositories that could steer file sync's git\n\nCloud file sync now refuses repos with a symbolic link inside `.git`, or git settings forced by a settings file in the repo\n\n**What**\n\nWhen you start a cloud session with `claude --cloud` and file sync is involved, Claude Code now refuses two kinds of repository:\n\n- One with a symbolic link (a file that points elsewhere) inside the `.git` directory behind the working folder, where git never creates one\n\n- One where a settings file inside the repository imposes a git setting that file sync's git would have to obey\n\nEach refusal says what to do: remove the link, or remove the setting or move it to your user settings if you set it yourself, then run `claude --cloud` again.\n\n**Why**\n\nA repository crafted to be hostile can no longer steer the git that file sync runs.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}