{"version":"2.1.280","anchor":"policy-classification-changed-event-subscription-is-wired","canonical_anchor":"policy-classification-changed-event-subscription-is-wired","heading":"Policy-classification 'changed' event subscription is wired but hard-disabled","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/policy-classification-changed-event-subscription-is-wired","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Policy-classification 'changed' event subscription is wired but hard-disabled\n\nA new internal listener for skipped or refused safety checks exists in the code but is forced off and never runs\n\n**What**\n\nClaude Code's internals now include a wrapper (`NZn`) that would let the app listen for 'changed' events tracking policy classifications that were skipped or refused, covering categories like bio, cyber, aup (acceptable use policy), agentic, and control. But a guard function (`ILn`) that decides whether this listener is allowed to run is hardcoded to always return false. As a result, `NZn` never actually subscribes to anything: it just hands back a do-nothing cleanup function, and the underlying event stream never fires.\n\n**Why**\n\nThis is inactive scaffolding: the plumbing for tracking skipped or refused policy checks is present in the code but is completely disabled, so it has no effect on how Claude Code behaves right now. It's worth knowing about only because it hints at monitoring capability that may be switched on in a future release.\n\n- Area: Permissions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}