{"version":"2.1.274","anchor":"new-per-person-ask-class-consent-tracking","canonical_anchor":"new-per-person-ask-class-consent-tracking","heading":"New per-person ask-class consent tracking","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-per-person-ask-class-consent-tracking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New per-person ask-class consent tracking\n\nClaude Code now tracks tool-permission consent separately for each collaborator in a session\n\n**What**\n\nSession state now includes several new tracking maps for permission-classifier decisions ('ask class', the system that decides whether a tool use needs to ask for permission) broken down per person or collaborator, rather than only tracking consent for the whole session:\n\n- `askClassPersonConsent` \u2014 tracks each person's consent decisions\n\n- `askClassPersonAsked` \u2014 tracks whether a person has already been asked\n\n- `askClassNoClassifier` \u2014 tracks cases with no classifier available\n\n- `askClassTakenByPerson` \u2014 tracks which person made a given decision\n\n- `notedUnreadRefusals` \u2014 reuses a cached deny message for a given tool use\n\n**Why**\n\nThis lets Claude Code manage tool-permission consent individually for each collaborator in a shared session, rather than treating consent as a single session-wide setting.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}