{"version":"2.1.281","anchor":"bash-command-set-check-uses-raw-command-name","canonical_anchor":"bash-command-set-check-uses-raw-command-name","heading":"Bash command-set check uses raw command name","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bash-command-set-check-uses-raw-command-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bash command-set check uses raw command name\n\nWhen the shell is bash, Claude Code now checks some command lists against the command name exactly as typed\n\n**Unclear.** The finding does not say which command groups changed or what the classification is used for.\n\n**What**\n\nClaude Code sorts shell commands into groups before running them, for example to decide how to treat them. When the shell is bash, this check now compares some groups against the command name exactly as written, not a cleaned-up form of it. The set of groups it looks at has also changed.\n\n**Why**\n\nIn bash, how a command is classified can now depend on its exact spelling.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}