{"version":"2.1.319","anchor":"worktree-settingslocaljson-copy-uses-a-stricter-write-dest","canonical_anchor":"worktree-settingslocaljson-copy-uses-a-stricter-write-dest","heading":"Copying local settings into a worktree uses a broader safety check","tier":"notice","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/worktree-settingslocaljson-copy-uses-a-stricter-write-dest","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Copying local settings into a worktree uses a broader safety check\n\nBefore copying settings.local.json into a new worktree, Claude Code now runs a general write-destination safety check rather than only a symlink check\n\n**What**\n\nA worktree is a separate working copy of a git repository that Claude Code can create to work in. When it creates one, Claude Code copies your `settings.local.json` file into it. Before doing that copy, it now runs a general safety check on where the file would be written.\n\nWhen the copy is skipped, the message is now:\n\n- `Skipping settings.local.json copy: destination fails the write-destination safety check`\n\nIt used to say the destination escaped the worktree through a committed symlink (a file that points somewhere else on disk).\n\n**Why**\n\nThe check makes worktree creation harder to trick into writing your local settings to an unexpected place. If you see the new skip message, your local settings were not copied into that worktree.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}