{"version":"2.1.293","anchor":"permission-events-carry-decision-reason-type-and-decision-re","canonical_anchor":"permission-events-carry-decision-reason-type-and-decision-re","heading":"Permission messages can now say why a permission was asked or decided","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/permission-events-carry-decision-reason-type-and-decision-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Permission messages can now say why a permission was asked or decided\n\nMessages about permission prompts now pass on a decision reason type and code when Claude Code has them\n\n**What**\n\nA permission prompt is where Claude Code asks you before it does something, such as running a command. The messages Claude Code sends about these prompts now include a reason type and a reason code for the decision, when those are known. Before, only the identifier of a suppressed request was passed along.\n\n**Why**\n\nRemote clients, such as an app watching a session from elsewhere, can now see why a permission was asked for or how it was decided.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}