{"version":"2.1.275","anchor":"bridge-repl-can-relay-a-queued-notification-from-another-ses","canonical_anchor":"bridge-repl-can-relay-a-queued-notification-from-another-ses","heading":"Bridge REPL can relay a queued notification from another session as a user frame","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/bridge-repl-can-relay-a-queued-notification-from-another-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Bridge REPL can relay a queued notification from another session as a user frame\n\nThe bridge REPL can now relay a queued notification from another session as if it were that session's own message\n\n**Unclear.** The finding does not say what produces a `queued_notification` message or what user-visible effect the relayed message has.\n\n**What**\n\nThe bridge (a communication channel used by the REPL, or interactive command loop) now recognizes a new incoming message type called `queued_notification`. When one arrives, it is re-delivered as if it were a regular user message belonging to the other session it references. If no notification buffer is configured to hold it, the message is instead logged and dropped.\n\n**Why**\n\nThis allows notifications generated in one session to be surfaced inside another session's conversation flow, rather than being lost when there's nowhere to route them.\n\n- Area: Remote Control\n- Names: `queued_notification`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}