{"version":"2.1.235","anchor":"permission-prompt-dont-ask-again-rows-are-now-minted-fro","canonical_anchor":"permission-prompt-dont-ask-again-rows-are-now-minted-fro","heading":"Permission-prompt \"don't ask again\" rows are now minted, frozen and verified","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/permission-prompt-dont-ask-again-rows-are-now-minted-fro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Permission-prompt \"don't ask again\" rows are now minted, frozen and verified\n\n\"Don't ask again\" permission rows are now pre-minted, frozen, and verified before being applied\n\nChrome\/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.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 2\/5"}