Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
IDE IntegrationArea: what it touches
In DevelopmentKind: in v2.1.232,
In DevelopmentSection of the release
What
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.
Details
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.
Evidence
@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.