{"version":"2.1.223","anchor":"remote-notifications-from-the-session-stream-are-routed-into","canonical_anchor":"remote-notifications-from-the-session-stream-are-routed-into","heading":"Remote notifications from the session stream are routed into the local notification queue","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/remote-notifications-from-the-session-stream-are-routed-into","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Remote notifications from the session stream are routed into the local notification queue\n\nNotifications sent from a remote session now actually reach you instead of being silently discarded.\n\n**What**\n\n`notification` frames arriving on the remote and thin-client streams used to be dropped on the floor; they now reach the local notification queue.\n\n**Details**\n\n- frames are validated for a string key, string text and a known priority; malformed frames are dropped with a debug line\n- normalisation prefixes the key with `remote:`, collapses text to a single line, downgrades `immediate` priority to `high` and clamps the timeout\n- an older remote notification is evicted when the remote quota is full\n- telemetry records the routing path taken\n\n**Evidence**\n\n`tengu_remote_notification_routed`\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}