{"version":"2.1.229","anchor":"sdk-clients-are-told-the-cli-accepts-queued-notifications","canonical_anchor":"sdk-clients-are-told-the-cli-accepts-queued-notifications","heading":"SDK clients are told the CLI accepts queued notifications","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/sdk-clients-are-told-the-cli-accepts-queued-notifications","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### SDK clients are told the CLI accepts queued notifications\n\nSDK clients now learn during handshake that the CLI can accept queued notifications.\n\n**What**\n\nThe init handshake a client gets over the SDK control protocol now advertises a third capability value, `queued_notifications`, meaning the CLI accepts inbound queued notification stream messages and drains them on request.\n\n**Details**\n\n- Documented as read by the backend from the persisted init event to decide whether it may send such messages.\n\n**Evidence**\n\n`'queued_notifications' = the CLI accepts inbound queued_notification stream messages and drains them via ReadNotifications`\n\n- Area: SDK\n- Names: `queued_notifications`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}