{"version":"2.1.323","anchor":"the-bash-tool-description-was-rewritten","canonical_anchor":"the-bash-tool-description-was-rewritten","heading":"Claude is told not to commit your local Claude Code settings file","tier":"notice","area":"Git","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/the-bash-tool-description-was-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude is told not to commit your local Claude Code settings file\n\nClaude's shell instructions now list .claude\/settings.local.json among files likely to hold secrets that it should not commit\n\n**What**\n\nThe Bash tool lets Claude run shell commands on your machine. Its description, which is the set of instructions Claude reads about how to use the tool, warns Claude not to commit files that likely contain secrets, such as `.env` or `credentials.json`. In this release that list also names `.claude\/settings.local.json`, your personal Claude Code settings file for a project.\n\nAs before, Claude should warn you if you specifically ask it to commit one of these files.\n\n**Why**\n\nChanging Claude's instructions changes how it behaves. Claude should now treat your local settings file like other secret-bearing files when making git commits, and warn you instead of committing it without comment.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}