Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.235,
ImprovementsSection of the release
Chrome/domain, Skill, Bash-prefix, plan-mode, and MCP permission dialogs no longer build permission updates on the fly when you answer. Each option is minted ahead of time into a displayed row, pairing its label with the exact update it applies, through a shared helper that deep-freezes the update payload and rejects anything that isn't plain data: functions, accessors, symbol keys, or prototype keys. If a row is missing or fails verification at answer time, the dialog falls back to a plain allow or deny rather than applying an unverified rule. The always-allow row is also withheld when the prompt came from a non-classifier-approvable safety check, when capped by org policy, or when the host contains a wildcard.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeImproved permission dialogs: display text and "don't ask again" options now always match what a grant would cover, and "don't ask again" is…