{"version":"2.1.319","anchor":"worktree-symlink-safety-message-and-check-changed","canonical_anchor":"worktree-symlink-safety-message-and-check-changed","heading":".worktreeinclude entries are now skipped by 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-symlink-safety-message-and-check-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### .worktreeinclude entries are now skipped by a broader safety check\n\nClaude Code now skips a .worktreeinclude entry when its destination fails a general safety check, not only when it escapes through a committed symlink\n\n**What**\n\nA worktree is an extra working copy of a git repository. A `.worktreeinclude` file lists files to copy into a new worktree. Claude Code used to skip an entry only when its destination escaped the worktree through a symlink saved in the repository. A symlink is a file that points to another place. It now skips an entry when the destination fails a general check that it is safe to write there.\n\n- The warning now reads \"Skipping .worktreeinclude entry: destination fails the write-destination safety check\".\n\n- For a check that is switched off, the text now reads \"The check comes back on its own.\" instead of \"It comes back on its own.\"\n\n**Why**\n\nMore kinds of unsafe destinations may now cause an entry to be skipped. If a file you expected is missing from a new worktree, this warning explains why.\n\n- Area: Worktrees\n- Names: `.worktreeinclude`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}