Editors are told when auto mode came only from the default and what you'd be offered instead.
What's wrong with this entry?
The payload sent to IDE and editor integrations at connect time gained two optional fields: one flagging that the session is in auto permission mode only because no settings source picked a mode and the gated auto default kicked in, and one carrying the user-settings default mode a one-time notice would offer instead. Both are populated only on the IDE-host branch. The notice itself already shipped in 2.1.231; what is new is exposing the state to hosts.
- The flag is computed as
permission_mode_from_default_fallback: hat() && u === "auto", so it is true only when the auto default gate is on and the session actually ended up in auto. - Guarded by
wNe() && ..., meaning non-IDE clients never see either field.
@internal True when current_permission_mode is auto because no settings source configured a mode and the gated auto default applied. IDE hosts only; drives the one-time "auto mode is now the default" disclosure.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Stale editor bridge connections are dropped instead of read
Both mention integration
-
v2.1.234
Git remote URLs can no longer smuggle a different host
Both mention integration
-
v2.1.236
Change detection ignores custom diff drivers and submodules
Both mention integration