{"version":"2.1.274","anchor":"new-git-worktree-create-refusal-for-unsafe-lfs-config-keys","canonical_anchor":"new-git-worktree-create-refusal-for-unsafe-lfs-config-keys","heading":"New git worktree-create refusal for unsafe LFS config keys","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-git-worktree-create-refusal-for-unsafe-lfs-config-keys","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New git worktree-create refusal for unsafe LFS config keys\n\nCreating a git worktree can now be refused if the repo's git config sets an unsafe Git LFS-related key\n\n**What**\n\nClaude Code can now refuse to create a git worktree or checkout with a new reason, `unsafe_key`, when the repository's own git config sets an LFS (Git Large File Storage)-related config key that names a program git-lfs would run during checkout or status.\n\n**Why**\n\nA repository's git config can be crafted to make git-lfs automatically run an arbitrary program. Refusing the worktree creation in that case stops Claude Code from triggering that program without the user knowing.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}