{"version":"2.1.289","anchor":"permission-rule-suggestions-now-also-apply-to-commands-with","canonical_anchor":"permission-rule-suggestions-now-also-apply-to-commands-with","heading":"Permission suggestions now cover commands that start with environment variables","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/permission-rule-suggestions-now-also-apply-to-commands-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Permission suggestions now cover commands that start with environment variables\n\nCommands like `FOO=1 cmd` now get a suggested permission rule even when the command itself matches the original\n\n**What**\n\nWhen Claude Code asks to run a shell command, it can suggest a permission rule, a saved rule that lets similar commands run without asking. A command can start with environment variables, which are settings given to the command, as in `FOO=1 cmd`. Claude Code now suggests a rule for such commands even when the command name matches the original. Previously it only suggested one when the command name differed.\n\n**Why**\n\nThis changes the rules Claude Code offers for commands that begin with environment variables. You now get a suggested rule for them instead of none.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}