{"version":"2.1.273","anchor":"session-inbox-wake-messages-get-a-dedicated-render-compone","canonical_anchor":"session-inbox-wake-messages-get-a-dedicated-render-compone","heading":"Session-inbox 'wake' messages now get their own parsing and rendering","tier":"notice","area":"Inbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/session-inbox-wake-messages-get-a-dedicated-render-compone","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Session-inbox 'wake' messages now get their own parsing and rendering\n\nMessages that wake a session due to an external event are now parsed and shown with a dedicated chat display instead of a generic one\n\n**What**\n\nMessages that begin with `<wake reason=\"external-event\"` \u2014 sent when an external event wakes up a session \u2014 are now specifically recognized instead of being shown as a generic system message.\n\n- A new function parses and detects these messages using `parseExternalEventWake` and `isSessionInboxWake`.\n\n- When a message passes the `isSessionInboxWake` check, the transcript renderer displays it with a dedicated `UserSessionInboxWakeMessage` component instead of the generic system-message renderer.\n\n**Why**\n\nThis gives session-inbox wake events (where something outside the conversation triggers the session to resume) a clearer, purpose-built appearance in the transcript instead of blending in with ordinary system messages.\n\n- Area: Inbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}