Under the hood
No documentation found
Permission requests now carry defaultToNo and suppressAlwaysAllowRule fields from the server
What
Permission requests (the prompts Claude Code shows before running a risky action) can now include two new pieces of information sent from the server: defaultToNo, and suppressAlwaysAllowRule. The second one is passed on internally as askSuppressesAlwaysAllowRule so that other parts of the code can check whether a given permission ask should skip offering an "always allow" rule.
Why
This lets the server mark certain permission prompts as ones where you shouldn't be offered a blanket "always allow" option, presumably for actions considered too sensitive to auto-approve going forward.
Names in the bundledefaultToNosuppressAlwaysAllowRule
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What specifically triggers suppressAlwaysAllowRule to be set is not stated.