{"version":"2.1.225","anchor":"the-bypasspermissions-consent-flag-reaches-startup-mode-reso","canonical_anchor":"the-bypasspermissions-consent-flag-reaches-startup-mode-reso","heading":"The bypassPermissions consent flag reaches startup mode resolution","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/the-bypasspermissions-consent-flag-reaches-startup-mode-reso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### The bypassPermissions consent flag reaches startup mode resolution\n\nSetting defaultMode to bypassPermissions now works in VS Code when you have enabled the consent setting.\n\n**What**\n\nA settings `defaultMode: \"bypassPermissions\"` is now honoured in a VS Code-owned session when the corresponding VS Code consent setting is enabled.\n\n**Details**\n\n- `allowDangerouslySkipPermissions` is now a parameter of the startup permission-mode resolver and is forwarded into the resolver's cli block\n- previously the resolver was called without it, so the mode was rejected with 'Permission mode bypassPermissions from settings was ignored \u2014 enable the \"Claude Code: Allow Dangerously Skip Permissions\" setting in VS Code to consent to it' even when the setting was on\n\n**Evidence**\n\n`allowDangerouslySkipPermissions`\n\n- Area: Permissions\n- Names: `defaultMode`, `bypassPermissions`, `Claude Code: Allow Dangerously Skip Permissions`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}