Under the hood
Useful2 Signal2
"Don't ask again" buttons now carry a pre-checked rule, so what you approve is what gets saved.
What's wrong with this entry?
Anonymous. No account, no email.
What
Chrome/domain, Skill, Bash-prefix, plan-mode and MCP permission dialogs no longer assemble a permission rule when you click the button. Each option is created up front as a row holding both its label and the exact rule it would write, and that rule is frozen and checked for being plain data before anything is saved.
Details
- The check rejects functions, accessors, symbol keys and non-plain prototypes in the rule payload.
- If the row is missing or fails its check at answer time, the dialog falls back to a plain one-time allow or a deny, and writes no rule.
- The always-allow row is withheld entirely when the request came from a safety check that a classifier cannot approve, when org policy caps it, or when the host contains a wildcard.
Evidence
deepFreezePlainData: accessor property in mint input
Strings lifted out of the shipped bundle, so the claim above can be checked against them.