{"version":"2.1.225","anchor":"vs-code-owned-sessions-get-their-own-settings-defaultmode-ha","canonical_anchor":"vs-code-owned-sessions-get-their-own-settings-defaultmode-ha","heading":"VS Code-owned sessions get their own settings defaultMode handling","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/vs-code-owned-sessions-get-their-own-settings-defaultmode-ha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### VS Code-owned sessions get their own settings defaultMode handling\n\nIn VS Code sessions, unsafe default permission modes from settings are refused and fall back to normal.\n\n**What**\n\nFor sessions owned by the VS Code extension, `permissions.defaultMode` is read only from policy, flag and user settings, and unsafe values from settings are refused.\n\n**Details**\n\n- `bypassPermissions` from settings is ignored unless the user has consented; a warning is printed to stderr and the mode falls back to default.\n- `auto` is ignored while the auto-mode circuit breaker is active.\n- The `auto` read additionally requires `tengu_harbor_willow` (fallback `!1`) or a `meadow_lantern` config value.\n\n**Evidence**\n\n`tengu_settings_bypass_unconsented_noninteractive_ignored`\n\n- Flag `tengu_harbor_willow`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.225; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Names: `permissions.defaultMode`, `bypassPermissions`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}