{"version":"2.1.300","anchor":"permission-always-allow-suppression-now-takes-a-second-arg","canonical_anchor":"permission-always-allow-suppression-now-takes-a-second-arg","heading":"'Always allow' in ask mode can now depend on a server-controlled switch","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/permission-always-allow-suppression-now-takes-a-second-arg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### 'Always allow' in ask mode can now depend on a server-controlled switch\n\nPermission prompts in ask mode no longer always hide 'always allow'; that now depends on the `tengu_valiant_crayon` switch\n\n**Unclear.** It is not clear which condition decides whether ask mode still hides the option.\n\n**What**\n\nWhen Claude Code asks permission to use a tool, it can offer an 'always allow' option so you are not asked again. Some tools decide, through a check called `suppressesAlwaysAllowRule`, whether that option should be hidden.\n\n- `suppressesAlwaysAllowRule` now receives a second piece of information from the permission prompt: `!k(\"tengu_valiant_crayon\", !1)`, which depends on a server-controlled switch named `tengu_valiant_crayon`.\n\n- In ask mode, the 'always allow' option used to be hidden every time. Now ask mode hides it only when that second value is false, which happens when `tengu_valiant_crayon` is on.\n\nNothing has been read about the state of `tengu_valiant_crayon`.\n\n**Why**\n\nIn ask mode you may start seeing an 'always allow' choice where it was always hidden before, depending on how that switch is set for you.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}