{"version":"2.1.269","anchor":"autobypass-permissions-plan-mode-gating-gains-an-extra-cond","canonical_anchor":"autobypass-permissions-plan-mode-gating-gains-an-extra-cond","heading":"Auto\/bypass-permissions plan-mode gating gains an extra condition","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/autobypass-permissions-plan-mode-gating-gains-an-extra-cond","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Auto\/bypass-permissions plan-mode gating gains an extra condition\n\nPlan-mode bypass-permissions gating now checks one more condition before treating bypass mode as active\n\n**Unclear.** What the added condition (referred to only as a function call) actually checks is not identified.\n\n**What**\n\nClaude Code has a \"plan mode\" for reviewing an approach before it runs, and a \"bypass permissions\" mode that skips normal approval prompts. The internal check that decides whether bypass-permissions mode is effectively active while in plan mode now requires an additional condition to be false, on top of the existing checks that plan mode is on and bypass permissions is available.\n\n**Why**\n\nThe extra condition narrows exactly when Claude Code treats bypass-permissions as active during plan mode, though what the added condition itself checks isn't identified.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}