What probably matters to youSection of the release
What
A settings defaultMode: "bypassPermissions" is now honoured in a VS Code-owned session when the corresponding VS Code consent setting is enabled.
Details
allowDangerouslySkipPermissions is now a parameter of the startup permission-mode resolver and is forwarded into the resolver's cli block
previously the resolver was called without it, so the mode was rejected with 'Permission mode bypassPermissions from settings was ignored — enable the "Claude Code: Allow Dangerously Skip Permissions" setting in VS Code to consent to it' even when the setting was on
Evidence
allowDangerouslySkipPermissions
Strings lifted out of the shipped bundle, so the claim above can be checked against them.