{"version":"2.1.269","anchor":"bypasspermissions-availability-in-plan-mode-now-requires-an","canonical_anchor":"bypasspermissions-availability-in-plan-mode-now-requires-an","heading":"bypassPermissions availability in plan mode now requires an interactive session","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/bypasspermissions-availability-in-plan-mode-now-requires-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### bypassPermissions availability in plan mode now requires an interactive session\n\nUsing bypass-permissions mode while in plan mode now requires an interactive session\n\n**Unclear.** The finding does not specify what the added condition checks beyond requiring an interactive session, so the exact requirement is not confirmed.\n\n**What**\n\nThe check for whether 'bypass permissions' mode (which skips permission prompts) can be used while Claude Code is in plan mode now requires an additional condition on top of the existing availability flag.\n\n**Why**\n\nThis narrows when bypass-permissions can be combined with plan mode, requiring an interactive session rather than allowing it in any context where the mode is generally available.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}