{"version":"2.1.281","anchor":"worktree-refusal-message-explains-the-configworktree-file","canonical_anchor":"worktree-refusal-message-explains-the-configworktree-file","heading":"Worktree-refusal message explains the config.worktree file","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/worktree-refusal-message-explains-the-configworktree-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Worktree-refusal message explains the config.worktree file\n\nThe worktree refusal message now shows how to find the config.worktree file and warns sparse-checkout needs it\n\n**What**\n\nClaude Code can refuse to use a git worktree, which is an extra working folder attached to the same repository, when it has its own per-worktree config file. The refusal message now gives the command that shows where that file is: `git rev-parse --git-path config.worktree`. It also warns that sparse-checkout needs that file. Sparse-checkout is a git feature that fills a folder with only part of a repository.\n\n**Why**\n\nYou can locate the file that caused the refusal. You are also warned before deleting it if you rely on sparse-checkout."}