{"version":"2.1.307","anchor":"permission-decision-records-person-decider-is-mapped-to-a-p","canonical_anchor":"permission-decision-records-person-decider-is-mapped-to-a-p","heading":"Permission decision records drop the decider field","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/permission-decision-records-person-decider-is-mapped-to-a-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Permission decision records drop the decider field\n\nRecords of permission decisions no longer include a decider field, and a decision made by a person now sets a plugin field instead\n\n**What**\n\nWhen Claude asks for permission to do something and that request is answered, Claude Code writes a record of the decision. These records no longer have a `decider` field. They now have a `plugin` field, which is set to a fixed value when the decision was made by a person.\n\n**Why**\n\nAnything that reads these records and looks for `decider` will no longer find it.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}