{"version":"2.1.242","anchor":"notification-dispatch-accepts-a-caller-supplied-storage-hand","canonical_anchor":"notification-dispatch-accepts-a-caller-supplied-storage-hand","heading":"Notification dispatch accepts a caller-supplied storage handle","tier":"internal","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/notification-dispatch-accepts-a-caller-supplied-storage-hand","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Notification dispatch accepts a caller-supplied storage handle\n\nNotification sending can be given a storage handle, defaulting to none, so nothing changes today.\n\n**What**\n\nThe notification entry point takes an optional third argument holding a storage handle and credentials, forwarded to the session-record write it does before sending on the configured channel. It defaults to empty, so behaviour is unchanged for existing callers.\n\n**Evidence**\n\n`preferredNotifChannel`\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}