{"version":"2.1.317","anchor":"bare-allow-rules-like-tool-are-normalized-to-rulecontent","canonical_anchor":"bare-allow-rules-like-tool-are-normalized-to-rulecontent","heading":"Allow rules like Tool(*) now count as allowing any input for some tools","tier":"use","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/bare-allow-rules-like-tool-are-normalized-to-rulecontent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Allow rules like Tool(*) now count as allowing any input for some tools\n\nFor some tools, an allow rule ending in (*) or () now means any input, behind a remote switch that is on unless turned off\n\n**Unclear.** Which tools this applies to, and how the old reading differs in practice, is not stated.\n\n**What**\n\nA permission rule tells Claude Code what it may do without asking you. For tools in a certain set, an allow rule that ends in `(*)` or `()` now means \"any input\" for that tool. Removing and saving rules also follow this reading.\n\nThe change is controlled by a remote switch that is on unless it is turned off remotely. A warning explains that older versions of Claude Code treat such a rule as the bare tool name, and that this version will too if Anthropic turns the change off.\n\n**Why**\n\nThis changes what some of your allow rules permit. A rule like `Tool(*)` may be read differently depending on your Claude Code version.\n\n- Area: Permissions\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}