{"version":"2.1.265","anchor":"consent-tracking-gains-dropconsentdeferral","canonical_anchor":"deferred-consent-payload-tracked-separately-in-session-verif","heading":"Deferred consent payloads are now tracked and clearable","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/consent-tracking-gains-dropconsentdeferral","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Deferred consent payloads are now tracked and clearable\n\nClaude Code now separately tracks a deferred consent payload and can clear it without recording consent\n\n**Unclear.** When or why a deferred consent would need to be dropped rather than recorded is not stated.\n\n**What**\n\n- The session verification cache gains a new `deferredPayload` slot, populated whenever a verified payload arrives with `consentDeferred` set.\n\n- The design\/artifact-consent state object gains a new `dropConsentDeferral()` method that clears this deferred payload directly, without going through the normal consent-recording path.\n\n**Why**\n\nThis lets Claude Code hold onto a consent decision that was deferred (put off) and later discard it cleanly if needed, rather than having to treat it as either recorded consent or nothing at all.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}