{"version":"2.1.232","anchor":"ide-handshake-can-tell-hosts-that-auto-mode-came-from-the-de","canonical_anchor":"ide-handshake-can-tell-hosts-that-auto-mode-came-from-the-de","heading":"IDE handshake can tell hosts that auto mode came from the default","tier":"internal","area":"IDE Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/ide-handshake-can-tell-hosts-that-auto-mode-came-from-the-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### IDE handshake can tell hosts that auto mode came from the default\n\nEditors are told when auto mode came only from the default and what you'd be offered instead.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- 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.\n- Guarded by `wNe() && ...`, meaning non-IDE clients never see either field.\n\n**Evidence**\n\n`@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.`\n\n- Area: IDE Integration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}