{"version":"2.1.323","anchor":"shell-command-safety-check-tightened-for-env-vars-and-globf","canonical_anchor":"shell-command-safety-check-tightened-for-env-vars-and-globf","heading":"Shell command safety check looks at more parts of a command","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/shell-command-safety-check-tightened-for-env-vars-and-globf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Shell command safety check looks at more parts of a command\n\nClaude Code's check on shell commands now looks at environment variable values, and can also flag wildcards and some short flags\n\n**Unclear.** It is not clear when the extra checks apply or which commands they cover.\n\n**What**\n\nBefore running a shell command, Claude Code checks it to decide whether it is safe to run without asking you. That check used to look only at the names of environment variables (named settings passed to a program) and arguments. It now also looks at environment variable values, and in some cases flags:\n\n- environment variables set just before certain commands\n\n- arguments containing the wildcard characters `*`, `?` or `[`\n\n- short flags containing the letter `n`, for some commands\n\n**Why**\n\nMore commands may now stop and ask for your permission before they run.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}