{"version":"2.1.229","anchor":"queued-notification-added-to-the-stdout-message-protocol","canonical_anchor":"queued-notification-added-to-the-stdout-message-protocol","heading":"queued_notification added to the stdout message protocol","tier":"internal","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/queued-notification-added-to-the-stdout-message-protocol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### `queued_notification` added to the stdout message protocol\n\nClaude Code can now buffer notifications and redeliver undrained ones when you resume a session.\n\n**What**\n\nThe message types Claude Code emits on stdout gained a `queued_notification` entry carrying an id, origin, content, a priority of \"now\", \"next\" or \"later\", and a queue timestamp. It is the wire format behind the ReadNotifications tool: the CLI buffers the event, nudges the model to drain it, and only acknowledges it once drained, so an undrained event is redelivered when the session resumes.\n\n**Evidence**\n\n`The CLI buffers it, nudges the model to call the ReadNotifications tool, and acks the event processed only when drained \u2014 an undrained event redelivers on resume.`\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}