{"version":"2.1.323","anchor":"bash-guidance-now-warns-against-committing-claudesettings","canonical_anchor":"bash-guidance-now-warns-against-committing-claudesettings","heading":"Claude now keeps .claude\/settings.local.json out of commits by default","tier":"notice","area":"Git","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-guidance-now-warns-against-committing-claudesettings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude now keeps `.claude\/settings.local.json` out of commits by default\n\nClaude's commit instructions now list `.claude\/settings.local.json` with .env and credentials files as files likely to hold secrets\n\n**What**\n\nClaude Code gives the model built-in instructions for making git commits. They are part of the description of the Bash tool, the tool Claude uses to run shell commands. The list of files that likely contain secrets and should not be committed now also names `.claude\/settings.local.json`, next to `.env` and `credentials.json`. If you specifically ask Claude to commit one of these files, it is told to warn you first.\n\nThis wording changed in the Bash tool description captured under this release.\n\n**Why**\n\nClaude will leave `.claude\/settings.local.json` out of commits unless you insist, so whatever is in that file is less likely to end up in a shared repository.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}