{"version":"2.1.323","anchor":"write-tool-validation-unchanged-but-settingslocaljson-now","canonical_anchor":"write-tool-validation-unchanged-but-settingslocaljson-now","heading":"settings.local.json is now always added to your global gitignore","tier":"notice","area":"Git","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/write-tool-validation-unchanged-but-settingslocaljson-now","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### settings.local.json is now always added to your global gitignore\n\nClaude Code now writes a rule for settings.local.json to your global gitignore even when git cannot confirm it, and warns Claude not to commit it\n\n**What**\n\n`.claude\/settings.local.json` holds your personal Claude Code settings for a project. Claude Code adds a rule to your global gitignore, the file that tells git which files never to track. Before, it skipped that rule unless a git check confirmed it would work. It now writes the rule even when that check cannot confirm it.\n\nThe guidance Claude follows when making commits also now lists `.claude\/settings.local.json` among the files not to commit because they may contain secrets, alongside `.env` and `credentials.json`.\n\n**Why**\n\nYour local settings are less likely to be committed and shared by accident.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}