{"version":"2.1.223","anchor":"permission-circuit-breakers-now-have-a-capability-table","canonical_anchor":"permission-circuit-breakers-now-have-a-capability-table","heading":"Permission circuit breakers now have a capability table","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/permission-circuit-breakers-now-have-a-capability-table","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Permission circuit breakers now have a capability table\n\nPeer-machine isolation prompts now still appear even when you're running in bypass-permissions mode.\n\n**What**\n\nThe four circuit-breaker kinds are described by a table of two booleans consumed by new predicates, replacing hard-coded special cases. isolatePeerMachines prompts now survive bypassPermissions mode, and they no longer route through classifier approval.\n\n**Details**\n\n- kinds covered: dangerousRemoval, backgroundOperator, suspiciousWindowsPath, isolatePeerMachines\n- the table holds `bypassImmune` and `classifierRouted` per kind\n- previously bypass-permissions immunity was hard-coded to dangerousRemoval, and classifier routing applied to every circuit breaker\n- backgroundOperator and suspiciousWindowsPath keep classifier-approval routing\n\n**Evidence**\n\n`bypassImmune`\n\n- Area: Permissions\n- Names: `bypassPermissions`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}