{"version":"2.1.318","anchor":"shell-line-settings-identity-check-now-fails-closed-in-more","canonical_anchor":"shell-line-settings-identity-check-now-fails-closed-in-more","heading":"More shell commands are treated as possibly touching a settings file","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/shell-line-settings-identity-check-now-fails-closed-in-more","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### More shell commands are treated as possibly touching a settings file\n\nWhen Claude Code cannot tell whether a shell command names a settings file, it now treats it as naming one in more cases\n\n**Unclear.** It is not clear which commands fall into the new cases.\n\n**What**\n\nClaude Code checks shell commands to see whether they name one of its settings files. In more cases now, when that check cannot reach a clear answer, the command is marked unresolved and counted as naming a settings file, instead of being let through as clean. Before, those cases passed unchanged.\n\n**Why**\n\nThis is more cautious: a command that might write to your settings is less likely to slip through unchecked. It may also mean more commands get stopped or questioned as possible settings changes.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}