{"version":"2.1.293","anchor":"bypass-permissions-consent-no-longer-inherited-blindly-writ","canonical_anchor":"bypass-permissions-consent-no-longer-inherited-blindly-writ","heading":"Bypass permissions mode is passed on only when your settings show you agreed","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/bypass-permissions-consent-no-longer-inherited-blindly-writ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Bypass permissions mode is passed on only when your settings show you agreed\n\nClaude Code now passes bypass permissions mode on to other sessions only if your user settings actually show you agreed to it\n\n**What**\n\nBypass permissions mode lets Claude use tools without asking you each time, and you have to agree to it first. Claude Code now handles that agreement more strictly when bypass mode is carried into another session that Claude Code starts:\n\n- The agreement dialog is skipped only when the agreement is carried over and your user settings already record it.\n\n- After the dialog, Claude Code reads your user settings again. If they do not show the agreement, for example because saving it failed or the file holds an invalid value, it logs a warning and does not pass bypass mode on.\n\nBefore, Claude Code checked once and always carried on.\n\n**Why**\n\nBypass mode no longer spreads to spawned or remote sessions unless your agreement was actually saved.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}