{"name":"tengu_settings_bypass_unconsented_noninteractive_ignored","slug":"tengu-settings-bypass-unconsented-noninteractive-ignored","family":"flag","title":"Feature flags","noun":"feature flag","description":"In VS Code sessions, unsafe default permission modes from settings are refused and fall back to normal.","description_source":"entry","described_by":{"version":"2.1.225","anchor":"vs-code-owned-sessions-get-their-own-settings-defaultmode-ha"},"presence":{"first_seen":null,"removed_in":null,"in_current_build":false,"newest_mined":"2.1.308","builds":0,"mined_builds":149,"first_cited":{"version":"2.1.225","released_at":"2026-08-07 23:08:56","spans":1}},"aliases":[],"entries":[{"version":"2.1.225","anchor":"vs-code-owned-sessions-get-their-own-settings-defaultmode-ha","heading":"VS Code-owned sessions get their own settings defaultMode handling","line":"In VS Code sessions, unsafe default permission modes from settings are refused and fall back to normal.","released_at":"2026-08-07 23:08:56","reason":"gate cited by this entry, found in this entry's text"}],"entries_total":1,"docs":[],"docs_total":0,"gates":[],"related":[{"name":"tengu_settings_change_staged","slug":"tengu-settings-change-staged","description":"New settings-review system can stage settings file changes for owner approval instead of applying them immediately, though it isn't active in this build"},{"name":"tengu_settings_mode_widening_carry_ignored","slug":"tengu-settings-mode-widening-carry-ignored","description":"Project or local settings can no longer widen the effective permission mode via defaultMode."}],"url":"https:\/\/changelogs.core-directive.com\/reference\/flag\/tengu-settings-bypass-unconsented-noninteractive-ignored","family_url":"https:\/\/changelogs.core-directive.com\/reference\/flag.json"}