{"version":"2.1.281","anchor":"clearer-refusal-for-linked-worktrees-with-worktree-config","canonical_anchor":"clearer-refusal-for-linked-worktrees-with-worktree-config","heading":"Clearer refusal for linked worktrees with worktree_config","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/clearer-refusal-for-linked-worktrees-with-worktree-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Clearer refusal for linked worktrees with worktree_config\n\nRefusals for a linked worktree with a `worktree_config` problem now warn that new worktrees made from it will be refused too\n\n**Unclear.** The finding does not say what is being uploaded or where it goes.\n\n**What**\n\nA git worktree is an extra working folder attached to the same git project. Claude Code refuses to upload from a linked worktree in some cases. When the reason is `worktree_config`, the refusal now also warns that a new worktree made from this one would be refused too, because current versions of git copy that configuration file into it.\n\n**Why**\n\nYou will not waste time making a fresh worktree from the same one, expecting it to get around the refusal."}