{"version":"2.1.280","anchor":"new-asktoannounce-device-hook-request-method","canonical_anchor":"new-asktoannounce-device-hook-request-method","heading":"New 'announce' permission hook via askToAnnounce","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-asktoannounce-device-hook-request-method","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New 'announce' permission hook via askToAnnounce\n\nRemote sessions gained an askToAnnounce request used to ask permission for an 'announce' device hook once tools are admitted\n\n**Unclear.** What askToAnnounce is used for and what triggers it isn't specified.\n\n**What**\n\nA remote session gained a new `askToAnnounce` method that sends a request over the control channel (marked as a device hook) and quietly swallows errors if it fails. Once a session's remote tools are admitted (`remoteToolsAdmission?.admitted === true`), the session now registers this `askToAnnounce` as its announce-permission provider on the control channel, replacing an older inline cancel-handling block that previously always ran.\n\n**Why**\n\nThis gives remote sessions a proper permission-asking path for the 'announce' hook, tied to whether the session's tools have actually been admitted, instead of an older always-on fallback.\n\n- Area: Sessions\n- Names: `askToAnnounce`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}