{"version":"2.1.269","anchor":"permission-mode-bypass-check-consolidated-into-a-shared-help","canonical_anchor":"permission-mode-bypass-check-consolidated-into-a-shared-help","heading":"Permission-mode bypass check consolidated into a shared helper","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/permission-mode-bypass-check-consolidated-into-a-shared-help","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Permission-mode bypass check consolidated into a shared helper\n\nPermission bypass-mode check consolidated into one shared helper across three call sites\n\n**Unclear.** The finding does not say what effect the moved isNonInteractiveSession check has in practice at either call site.\n\n**What**\n\nThree places in the code separately checked whether the current permission mode is `bypassPermissions`, or is `plan` mode with bypass permissions available. That duplicated logic has been consolidated into a single shared helper. As part of the change, one of the call sites dropped a check for whether the session is non-interactive, while a different call site gained that same check.\n\n**Why**\n\nConsolidating the check into one place reduces the risk of the three call sites drifting out of sync, though the shift of the non-interactive check between call sites means the conditions under which bypass mode applies changed slightly at those two spots.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}