{"version":"2.1.319","anchor":"bash-parser-recognises-an-opt-out-word-after-a-command","canonical_anchor":"bash-parser-recognises-an-opt-out-word-after-a-command","heading":"Shell command analysis can detect an opt-out word","tier":"internal","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bash-parser-recognises-an-opt-out-word-after-a-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Shell command analysis can detect an opt-out word\n\nClaude Code's analysis of shell commands now looks for an opt-out word after the command and records a match\n\n**Unclear.** What the opt-out word is and what it changes about how a command is handled are not stated.\n\n**What**\n\nBefore running a shell command, Claude Code reads the start of it to decide things such as whether you need to approve it. That analysis now checks the words that follow the command for an opt-out and reports when it finds one.\n\n**Why**\n\nThis may change how permission checks read some shell commands.\n\n- Area: Bash Safety\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}