{"version":"2.1.280","anchor":"git-worktree-config-detection-now-distinguishes-file-vs-e","canonical_anchor":"git-worktree-config-detection-now-distinguishes-file-vs-e","heading":"Git worktree config detection now distinguishes 'file' vs 'extension' vs 'absent' states","tier":"internal","area":"Git Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-worktree-config-detection-now-distinguishes-file-vs-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git worktree config detection now distinguishes 'file' vs 'extension' vs 'absent' states\n\nGit worktree config detection now reports 'file', 'extension', or 'absent' instead of the old three states\n\n**Unclear.** The finding does not say what different behavior each of the three states now triggers.\n\n**What**\n\nClaude Code checks how a git repository's worktree configuration is set up, since this affects how it handles multiple working copies of a repo. The internal check now reports one of three outcomes: `file` (a real `config.worktree` file exists), `extension` (git reports the worktree extension is turned on but no backing file exists), or `absent` (neither is set).\n\n**Why**\n\nThis is an internal reclassification of an existing check, giving Claude Code a more precise read on how a repo's worktree setup is configured, which can affect how it interacts with git worktrees.\n\n- Area: Git Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}