{"version":"2.1.310","anchor":"bash-permission-check-for-colon-separated-prefixes-changed","canonical_anchor":"bash-permission-check-for-colon-separated-prefixes-changed","heading":"Bash permission check for commands with a colon-separated prefix changed","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/bash-permission-check-for-colon-separated-prefixes-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Bash permission check for commands with a colon-separated prefix changed\n\nClaude Code changed how it checks a Bash command that starts with a colon-separated prefix when deciding whether to allow it\n\n**Unclear.** It is not clear whether any command is now allowed or refused differently than before.\n\n**What**\n\nBefore Claude Code runs a shell command, it checks the command against its permission rules to decide whether the command can run without asking you. For commands that begin with a prefix separated by a colon, that check now looks at the prefix and at the rest of the command after the colon. Previously it looked only at one piece of the command.\n\n**Why**\n\nThis can change which of these commands Claude Code allows automatically and which it stops to ask you about.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}