{"version":"2.1.323","anchor":"local-settings-lookup-in-git-worktrees-reworked","canonical_anchor":"local-settings-lookup-in-git-worktrees-reworked","heading":"Claude Code finds local settings files in git worktrees a different way","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/local-settings-lookup-in-git-worktrees-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude Code finds local settings files in git worktrees a different way\n\nClaude Code has reworked how it works out which extra local settings files to read when you are inside a git worktree\n\n**Unclear.** Whether this changes which local settings file Claude Code reads in a worktree is not stated.\n\n**What**\n\nClaude Code can read a local settings file (`localSettings`), which holds settings for your copy of a project only. A git worktree is a second working folder linked to the same repository as your main one.\n\nWhen you work in a worktree, Claude Code looks for extra local settings files to read. The way it decides where to look has been reworked. It now uses a shared routine instead of comparing the current folder with the repository's root folder directly.\n\n**Why**\n\nWhich local settings apply inside a worktree could be different from before. If your worktree settings behave unexpectedly, check which local settings file is being picked up.\n\n- Area: Settings\n- Names: `localSettings`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}