{"version":"2.1.290","anchor":"bash-parser-command-v-flag-check-fixed","canonical_anchor":"bash-parser-command-v-flag-check-fixed","heading":"Fixed how shell permission checks read flags after command","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bash-parser-command-v-flag-check-fixed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Fixed how shell permission checks read flags after `command`\n\nClaude Code now checks each flag after the shell command `command` correctly when deciding whether a command such as command -v is safe\n\n**Unclear.** The exact flags the new check accepts are not clear.\n\n**What**\n\nBefore a shell command runs, Claude Code reads it to decide whether it needs your permission. For commands starting with `command`, as in `command -v`, the old check looked at the wrong part of the line when testing for flags. It now checks each flag that follows `command` in turn.\n\n**Why**\n\nThis changes how forms such as `command -v` are treated when Claude Code decides whether a shell command can run without asking.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}