What it is
Project or local settings can no longer widen the effective permission mode via defaultMode.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.257.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
First cited
1The earliest release whose published evidence quoted tengu_settings_mode_widening_carry_ignored was v2.1.257, 1 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table above.
Gate readings
0No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
Names beside it
Every feature flag in the inventory starting tengu_settings, up to twelve of them.
tengu_settings_bypass_unconsented_noninteractive_ignoredIn VS Code sessions, unsafe default permission modes from settings are refused and fall back to normal. never mined
tengu_settings_change_stagedNew settings-review system can stage settings file changes for owner approval instead of applying them immediately, though it isn't active in this build never mined
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.