{"version":"2.1.305","anchor":"queued-remote-notifications-notify-a-listener","canonical_anchor":"queued-remote-notifications-notify-a-listener","heading":"Queued notifications in remote sessions can now trigger a notice","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/queued-remote-notifications-notify-a-listener","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Queued notifications in remote sessions can now trigger a notice\n\nIn remote sessions, notifications that were waiting in a queue now pass their IDs on when they are delivered, not only to the log\n\n**What**\n\nIn a remote session, which is a Claude Code session running on another machine, notifications can wait in a queue before they are delivered. When that queue is emptied, Claude Code now passes the IDs of those notifications to another part of the program. Before, it only wrote them to its log. If that step fails, the failure is logged.\n\n**Why**\n\nThis lets a remote session show a notice that queued messages have started.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}