{"version":"2.1.223","anchor":"circuit-breaker-permission-reasons-moved-to-a-registry-isola","canonical_anchor":"circuit-breaker-permission-reasons-moved-to-a-registry-isola","heading":"Circuit-breaker permission reasons moved to a registry; isolatePeerMachines is now bypass-immune","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/circuit-breaker-permission-reasons-moved-to-a-registry-isola","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Circuit-breaker permission reasons moved to a registry; isolatePeerMachines is now bypass-immune\n\nCross-machine file transfer denials can no longer be bypassed once you enable peer isolation.\n\n**What**\n\nPermission code no longer hardcodes a single circuit-breaker name when deciding what cannot be bypassed, and cross-machine isolation denials now survive the bypass path.\n\n**Details**\n\n- A table marks each circuit breaker as `bypassImmune` \/ `classifierRouted`: dangerousRemoval, backgroundOperator, suspiciousWindowsPath, isolatePeerMachines. Previously only `dangerousRemoval` was checked directly.\n- The isolatePeerMachines file-transfer denial now stamps `circuitBreaker: \"isolatePeerMachines\"` on its decision reason, which makes it bypass-immune in the multi-`cd` ask path.\n- The isolatePeerMachines setting still has to be enabled for that breaker to fire at all.\n\n**Evidence**\n\n`isBypassImmuneCircuitBreaker`\n\n- Area: Permissions\n- Names: `isolatePeerMachines`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}